Segment contacts based on campaign activity
When an email campaign is sent in Beambox, automatically place those contacts into a specialized segment in Piggy for follow-up messaging.
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.
Piggy Explore Piggy →
TriggersFires when a new subscriber is added in Piggy.
Fires when a campaign is sent from Piggy.
Fires when a subscriber unsubscribes in Piggy.
Adds or updates a subscriber in Piggy.
Creates or sends a campaign from Piggy.
Adds a subscriber to a segment in Piggy.
Beambox Explore Beambox →
TriggersFires when a new subscriber is added in Beambox.
Fires when a campaign is sent from Beambox.
Fires when a subscriber unsubscribes in Beambox.
Adds or updates a subscriber in Beambox.
Creates or sends a campaign from Beambox.
Adds a subscriber to a segment in Beambox.
More Piggy + Beambox workflows
See all Piggy + Beambox integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Segment contacts based on campaign activity” between Piggy and Beambox?
Yes — describe it in the box above and Knit's Integrations Agent researches Piggy and Beambox'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 marketing tools like Piggy and Beambox?
Integrating Piggy and Beambox helps you maintain synchronized subscriber lists, avoid duplicate outreach, and target specific segments across platforms.
How are unsubscribes handled between Piggy and Beambox?
When a subscriber opts out in Piggy, their status can be instantly updated in Beambox to preserve compliance and deliverability.