Suppress contact in secondary platform upon unsubscribe
If a user unsubscribes in Proof, automatically remove them from active email campaigns in Pardot to maintain compliance.
Google for Startups AcceleratorHow 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.
Proof Explore Proof →
TriggersFires when a new lead or contact is captured in Proof.
Fires when a contact enters an automation in Proof.
Fires when a field on a contact changes in Proof.
Fires when a contact unsubscribes in Proof.
Creates or updates a contact in Proof.
Adds a contact to a workflow or campaign in Proof.
Sends an email or message to a contact via Proof.
Changes a contact's tags in Proof.
Pardot Explore Pardot →
TriggersFires when a new lead or contact is captured in Pardot.
Fires when a contact enters an automation in Pardot.
Fires when a field on a contact changes in Pardot.
Fires when a contact unsubscribes in Pardot.
Creates or updates a contact in Pardot.
Adds a contact to a workflow or campaign in Pardot.
Sends an email or message to a contact via Pardot.
Changes a contact's tags in Pardot.
More Proof + Pardot workflows
See all Proof + Pardot integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Suppress contact in secondary platform upon unsubscribe” between Proof and Pardot?
Yes — describe it in the box above and Knit's Integrations Agent researches Proof and Pardot'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.
Why connect two different marketing automation tools together?
It allows organizations managing separate platforms for different business units or channels to synchronize contact tags, subscriber statuses, and campaign workflows seamlessly between Proof and Pardot.
How are opt-out preferences handled across both systems?
When a contact unsubscribes in Proof, an automated sync can remove tags or apply suppression tags to that same contact in Pardot.