When deal moved to new stage in Gust, sync it to Customers.ai.
When a deal moves to a new stage in Gust, update the contact profile in Customers.ai.
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.
Customers.ai Explore Customers.ai →
TriggersFires when a new lead or contact is captured in Customers.ai.
Fires when a contact enters an automation in Customers.ai.
Fires when a field on a contact changes in Customers.ai.
Fires when a contact unsubscribes in Customers.ai.
Creates or updates a contact in Customers.ai.
Adds a contact to a workflow or campaign in Customers.ai.
Sends an email or message to a contact via Customers.ai.
Changes a contact's tags in Customers.ai.
Gust Explore Gust →
TriggersFires when a new donation, pledge or investment is recorded in Gust.
Fires when a donor sets up a recurring gift in Gust.
Fires when a fundraising campaign or round in Gust hits its goal.
Creates or updates a donor or investor record in Gust.
Sends a donation receipt via Gust.
Starts a new fundraising campaign in Gust.
Common questions
Can Knit build “When deal moved to new stage in Gust, sync it to Customers.ai.” between Customers.ai and Gust?
Yes — describe it in the box above and Knit's Integrations Agent researches Customers.ai and Gust'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.