Where to find this: Inside the workflow editor — these nodes only appear if the corresponding integration is connected.
Introduction
Partner Nodes hand off the workflow at a specific point to a third-party messaging platform. Two legacy partner nodes remain: Engati (conversational AI) and Kwik Engage (multi-channel messaging).When to use
- You already use Engati or Kwik Engage for non-WhatsApp customer messaging (e.g., Engati conversational bot flows, Kwik Engage SMS).
- You want loyalty events to trigger those legacy partner integrations.
- For WhatsApp messaging through any provider — use the WhatsApp Workflow node instead.
Available partner nodes
Engati Node
- Available when: the Engati integration is connected.
- Action: triggers a specified Engati flow / bot interaction with the customer.
- Configuration: pick the Engati flow, optionally pass workflow context.
- For WhatsApp via Engati: use the WhatsApp node with Engati selected as the provider.
Kwik Engage Node
- Available when: the Kwik Engage integration is connected.
- Action: triggers a Kwik Engage event — SMS, WhatsApp, or another configured channel.
- Configuration: pick the event type, optionally pass workflow context.
- For WhatsApp via Kwik Engage: use the WhatsApp node with Kwik Engage selected as the provider.
WhatsApp Node — the unified successor
For WhatsApp specifically, the WhatsApp Workflow node supersedes these partner nodes. One node, 7 providers (AISensy, Zoko, WATI, DelightChat, Kwik Engage, Engati, QuickReply.ai), shared shortcode catalogue.How partner nodes execute
- The node calls the partner’s API with the customer’s data.
- The partner tool takes over messaging from there.
- The workflow continues to the next node after the call returns (without waiting for the customer’s response).
Decision guidance
- Use Engati Node when you want a conversational bot flow (the customer can reply and continue the conversation through Engati).
- Use Kwik Engage Node when you want one-shot SMS or other-channel messages.
- Use the WhatsApp Node for any WhatsApp template send, regardless of provider — it’s the unified path.
Limitations
- Each partner node only appears if the corresponding integration is connected.
- The workflow doesn’t wait for the customer’s reply in the partner tool.
- Failures in the partner tool are logged but don’t block the workflow.
Best practices
FAQs
Can I add a custom partner node?
Can I add a custom partner node?
Not in v1. Use Webhooks and a custom integration if you have a partner not supported here.
Why don't I see the partner node?
Why don't I see the partner node?
The partner integration must be connected first. See Integrations.
Should I use the Engati Node or the WhatsApp Node with Engati provider?
Should I use the Engati Node or the WhatsApp Node with Engati provider?
For WhatsApp template sends, use the WhatsApp Node — it uses the same Engati credentials but gives you the unified shortcode catalogue and a clearer UI. Use the Engati Node only for non-template conversational flow triggers.
Related
WhatsApp Workflow node
The unified node for WhatsApp across all 7 providers.
WhatsApp overview
Provider-agnostic overview of the WhatsApp integration.
Build your first workflow
A 10-minute walkthrough from blank canvas to a live workflow.
Triggers & Conditions
Events that start a workflow and rules that branch it.
Action Nodes
Send email, credit / debit points, issue a coupon.
Wait & Exit
Pause execution and end a workflow cleanly.
Partner Nodes
Hand off to Engati or KwikEngage.
Analytics
Track entries, completions and step-level drop-off.
Book a Free Setup Call
Talk to our team for personalised setup help.Time: 30 minutes
Contact Support
Visit our support hub for help articles, live chat and ticket submission.
Browse the Guides
Documentation across loyalty, referrals, memberships and more.
Install Yuko
Add Yuko to your Shopify store from the Shopify App Store.