SendApp

A support agent finishes a ticket in Zendesk and the flow needs to follow up on WhatsApp two days later. Two days is outside Meta's 24 hour customer service window, so free text will be rejected. The agent reads List WhatsApp Templates, selects the approved follow-up template, fills its variables from the ticket record, and sends it with Send WhatsApp Template Message. It captures the returned Meta message ID and polls Get WhatsApp Message Status to record whether the customer read it, then writes that state back to the ticket. Nothing about the window is guessed, because the connector reads the approval state rather than assuming it.

New customers land in Shopify all day. A flow watches for new orders, normalizes the phone number, and calls Create Contact, which merges into an existing record when the phone or email already exists rather than creating a duplicate. Weekly, a reconciliation flow calls Bulk Create Contacts with the full customer export so late arrivals and corrections catch up in a single call, and reads the contact usage figure the response returns against the plan ceiling. When the plan ceiling is close, the agent stops importing and raises it in Slack instead of silently dropping records.

A distributor keeps its product documentation as PDFs and a public catalog site. A flow calls Create AI Account, submits the PDFs and the sitemap with Upload AI Training Data, then polls Get AI Training Status until the run completes. From then on, inbound product questions arriving through the account are answered with Ask AI Assistant, passing the conversation ID back on each turn so context carries across the exchange. When the assistant returns its configured fallback message, meaning it had no answer, the flow escalates the thread to a human in Microsoft Teams with the customer's question attached. The assistant handles the repeat questions and the unanswered ones become a queue for a person.