Send exit surveys when subscriptions are canceled
When a subscription is canceled in SubscriptionFlow, automatically add the customer as a respondent in Tally to collect exit feedback.
See all SubscriptionFlow + Tally integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
SubscriptionFlow Explore SubscriptionFlow →
TriggersFires when a new customer is created in SubscriptionFlow.
Fires when a subscription is canceled in SubscriptionFlow.
Fires when a new invoice is generated in SubscriptionFlow.
Fires when a payment attempt fails in SubscriptionFlow.
Creates a new customer in SubscriptionFlow.
Creates a new subscription in SubscriptionFlow.
Cancels an existing subscription in SubscriptionFlow.
Updates a customer's billing details in SubscriptionFlow.
Tally Explore Tally →
TriggersFires when a form is submitted in Tally.
Fires when a respondent finishes a survey in Tally.
Fires when an existing response is edited in Tally.
Creates or updates a form or survey in Tally.
Looks up a specific form response in Tally.
Adds a respondent or contact to a form in Tally.
More SubscriptionFlow + Tally workflows
Create subscribers from sign-up form responses
When a customer submits a registration form in Tally, automatically create a new customer and subscription profile in SubscriptionFlow.
See details
Update customer records based on updated form details
When a form response is updated in Tally, automatically update the matching customer details in SubscriptionFlow to keep billing information accurate.
See details
See all SubscriptionFlow + Tally integrations → · Browse the full workflow library →
Common questions
Can Knit build “Send exit surveys when subscriptions are canceled” between SubscriptionFlow and Tally?
Yes — describe it in the box above and Knit's Integrations Agent researches SubscriptionFlow and Tally's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
How does connecting Tally and SubscriptionFlow streamline subscription workflows?
Form entries in Tally can automatically create subscribers in SubscriptionFlow, while subscription changes in SubscriptionFlow can initiate automated survey outreach.
Can survey responses update existing subscriber records?
Yes, when a customer submits or updates information in Tally, their contact and billing profile in SubscriptionFlow can update automatically.