Integration Actions
Call your own API, report conversions to Meta, and route incoming WhatsApp calls from a LeadPattern bot — every setting, limit and skip reason.
Call API (call_api)
Makes an outbound HTTP request to your own system — look up an order, push a lead to a CRM, ping a Zap.
The node itself only has a Select API dropdown. Each API is a reusable definition, so several bots can share it. Use Create New API (or the edit icon on a row) to open the editor; deleting an API asks for confirmation and makes any node still using it show "Selected API was deleted".
| API field | What it does |
|---|---|
| API name (required) | A label, for example "Get User Data". |
| Method and URL (required) | GET, POST, PUT, DELETE, PATCH or HEAD, and the endpoint (https://api.example.com/endpoint). |
| Query params | Key/value pairs added to the URL. Rows with an empty key are ignored. |
| Path params | Replace :paramName in the URL with the value (URL-encoded). |
| Headers | Key/value pairs. There's no separate auth setting — put an Authorization header here. |
| Body type | None, JSON (raw text, validated when you leave the box), Form data (text or file rows) or URL encoded. JSON sets Content-Type: application/json. |
What happens when the bot runs:
- Variables in the URL, path values, query values, header values and body values are filled in
first (
{{field:…}}and{{attr:…}}; Shopify/QuickSell tokens come out empty here). Values are inserted as-is — they aren't JSON-escaped, so a name containing a quote can break a JSON body. - The request times out after 15 seconds (the Test button in the editor waits 30).
- Any HTTP status counts as success — a 404 or 500 doesn't stop or branch the flow. The status code is recorded in the bot log.
- The response is not stored: there's no way to put values from the response into attributes or messages, and no retries.
- Private and internal addresses are blocked, including localhost, 10.x, 172.16–31.x, 192.168.x, link-local and cloud metadata addresses, and on redirects (max 3). A blocked or unreachable call logs a failed step and the flow continues. Saving rejects URLs that already point at a private address.
- If the API definition was deleted, the step is skipped.
Send Meta Conversion (send_meta_conversion)
Tells Meta that a Click-to-WhatsApp chat reached an outcome (qualified lead, purchase…), so Meta can optimise your ads. Read Meta Conversions (CAPI) first — it explains what the add-on does and how to turn it on.
| Field | What it does |
|---|---|
| Meta event | One of: Lead submitted, Qualified lead, Purchase, Checkout started, Added to cart, Viewed content, Order created, Order shipped, Order delivered, Order canceled, Order returned, Cart abandoned, Rating given, Review given. |
| Order value (Purchase only) | Fixed amount (a number) or From a custom field (pick an attribute; non-numeric characters such as "₹" and "," are stripped, so "₹1,499" becomes 1499). |
| Currency (Purchase only) | Three-letter code, for example INR. Defaults to INR. |
The node never stops your flow. If the event can't be sent, the step is logged as skipped with the reason:
| Reason | Meaning |
|---|---|
| Conversions off / not entitled / WhatsApp not connected | Not enabled in Integrations → Meta Ads → Conversions, not in your plan, or WhatsApp disconnected |
| Not from an ad / no click ID | The contact didn't come from a Click-to-WhatsApp ad |
| Click too old | The ad click was more than 7 days ago |
| No value | A Purchase without a numeric value |
| Duplicate | This event was already sent for this contact and ad click |
| Restricted | Workspace is restricted |
Events are queued and sent in the background, once per event, contact and ad click. Activation errors: an unknown event, a Purchase with no value source, or a plan without the feature; a warning if conversions aren't switched on yet.
Incoming Call (ring_call)
Only available when the trigger is Incoming WhatsApp Call. It decides which agents' phones ring and what happens next. See Receive a call.
| Field | What it does | Default |
|---|---|---|
| Assignment method | Ring all simultaneously, Round robin, Route randomly, Assigned agent or Escalate to manager. | Ring all |
| Agents | Who can be rung — only active agents with a calling licence are listed. | — |
| Manager | Who to escalate to (Escalate method). | — |
| Ring for / Wait per agent (seconds) | How long each ring lasts, 5–60. A warning appears when the total ringing time goes over 45 seconds. | 20 |
Outputs: Answered (continues after the call ends) and Not answered. If nobody is available, the flow takes Not answered immediately and the call is rejected.
What's next
Was this article helpful?
Your feedback helps us continuously improve our documentation.
Related Articles
Conditions & Actions
How a LeadPattern bot flow runs: node categories, failure handling, variables and activation checks, with links to every action and condition.
Bot Triggers
Every LeadPattern bot trigger with each setting explained: keywords, attribute and template filters, ad scopes, store events and calls, and when each fires.
Meta Conversions (CAPI)
Report qualified leads, bookings and purchases from WhatsApp chats back to Meta with LeadPattern and the Conversions API, to see which CTWA ads work.
Receive a Call
Answer incoming WhatsApp calls from customers in LeadPattern, and use bots to respond automatically when a call comes in.

