When new deal in Gust, sync it to Pipefy.
When a new deal is created in Gust, create a card in Pipefy to track evaluation tasks.
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.
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.
Pipefy Explore Pipefy →
TriggersFires when a new task, job or item is created in Pipefy.
Fires when a task in Pipefy is marked complete.
Fires when a task's due date in Pipefy is coming up.
Fires when a task, job or project changes status in Pipefy.
Creates a new task, job or item in Pipefy.
Updates a task's status or assignee in Pipefy.
Posts a comment on a task in Pipefy.
Assigns a task in Pipefy to a team member.
Common questions
Can Knit build “When new deal in Gust, sync it to Pipefy.” between Gust and Pipefy?
Yes — describe it in the box above and Knit's Integrations Agent researches Gust and Pipefy'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.