Iterable, ready to run.
The Iterable integration connects each case to your cross-channel messaging. Floowed reads a user's profile, lists and subscriptions, then updates fields, tracks an event or triggers a campaign when the case is decided.
What it does.
What Floowed reads from Iterable
- User profiles and data fields
- List membership
- Subscription preferences per channel
- Events tracked on a user
What it writes back
- User fields updated from the case
- A custom event that starts a journey
- A triggered campaign send
- A subscription change or unsubscribe
Iterable keys come in types, so give Floowed a server-side key. Use custom events to hand off to your journeys, which keeps copy and timing in Iterable where your marketers work. Channel unsubscribes are honored without waiting for a person.
How it connects.
- 1
Connect Iterable
Using an API key. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with Iterable?
Yes. Floowed connects to Iterable with a server-side API key from your project.
What can Floowed do with Iterable?
It updates user fields, tracks events, triggers campaigns and changes subscriptions based on how a case ends.
Is my Iterable data secure?
Floowed only gets the access it needs and never stores a password. The key is per project and can be disabled from Iterable's integrations settings. Every read and write is logged with the reason it happened.
What does the Iterable integration cost?
Nothing extra. Integrations are included in every plan, and you only pay for the work your operations do.
Start with Iterable. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.