You need to control the API response shape. If you only consume a third-party API, map fields with Response Mapping and show them with
{{custom_fields}} instead.Response envelope
messages— content sent to the contactactions— side effects (tags, fields, send Flow, Inbox transfer)
X-USER-ID header on every External Request so your server can identify the contact.
Response mapping helpers
When you map a normal JSON API (not dynamic content), these special paths are available:
Use
http_status_code with a Condition to branch on success vs client/server errors.
Message examples
Text
Multiple messages
Text with buttons
Up to 3 buttons. Button titles up to 20 characters. Use a Flow or step ID aspayload to continue the conversation.
Quick replies
Attach up to 11 quick replies to text, media, or cards. Payload rules match buttons.Image, video, audio, or file
Changetype to image, video, audio, or file.
Card or gallery
Card title/subtitle up to 80 characters. Up to 3 buttons per card. Galleries up to 10 cards.image_aspect_ratio: horizontal or square.
WhatsApp-only payloads
For lists, catalogs, contacts, or other WhatsApp interactive types, return the WhatsApp Cloud API message object insidemessages. Fliqr AI sets the recipient for you — keep "to": null.
Actions in the response
Run side effects alongside (or instead of) messages.
Example — set a field and send a Flow:
Actions as button payloads
Payloads are strings. JSON-encode the actions object:Limits
- Default External Request rate: 100 requests / 60 seconds per bot account
- Channel button, card, and media limits still apply after conversion
Next
External requests
Add the block, headers, and success/failure paths.
Extract JSON
Pull individual fields from JSON with JSONPath.