With the Drip integration, you can send Returnflows events directly to Drip to trigger your email flows.
Event names and logic match Klaviyo 1:1.
🧭 What the integration does
Sends Returnflows events to Drip so you can build automated emails.
Events appear on the customer’s profile in Drip.
If the customer doesn’t exist in Drip yet, events are still sent, but you’ll only see them once the customer is created in Drip.
🧩 Setup (2 minutes)
Log in to Drip
Go to User settings in Drip → copy your API Token
In Returnflows: Settings → Integrations → Drip → paste the API Token → Save
Tip: Use View Logs to inspect integration logs (errors/success).
🧪 Verify it works
Trigger an action in Returnflows (e.g., create a return).
Look up the customer in Drip.
If the customer isn’t created in Drip: create the customer → events will now be visible on the profile.
🔔 Events sent to Drip
Event | Description |
Return Created | When a customer creates a new return |
Return Received | When we receive the tracking event “package handed in / delivered” |
Return Paused | When an exchange order is put on hold (typically due to missing return) |
Return Closed | When a return is closed and processed |
Return Completed | The moment the customer completes their return |
Return Reset | When a return is reset |
Return Canceled | When a return is canceled |
Return In Transit | When we receive an IN_TRANSIT tracking update from carriers |
❓ FAQ
Does the customer need to exist in Drip to receive events?
Events are sent regardless, but you’ll see them in Drip only after the customer is created.
Where do I paste the API Token?
In Returnflows → Integrations → Drip (the API Token field).
Do events match Klaviyo?
Yes — event names and logic match Klaviyo 1:1.