Segment contacts based on custom database query results
When a targeted audience query finishes running in Zite, automatically add the identified contacts into a designated segment in Encharge.
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.
Zite Explore Zite →
TriggersFires when a new row is added to a table in Zite.
Fires when an existing row changes in Zite.
Fires when a scheduled query in Zite finishes running.
Runs a SQL query against Zite and returns the result.
Writes a new or updated row to Zite.
Syncs a table in Zite with data from another source.
Encharge Explore Encharge →
TriggersFires when a new subscriber is added in Encharge.
Fires when a campaign is sent from Encharge.
Fires when a subscriber unsubscribes in Encharge.
Adds or updates a subscriber in Encharge.
Creates or sends a campaign from Encharge.
Adds a subscriber to a segment in Encharge.
More Zite + Encharge workflows
See all Zite + Encharge integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Segment contacts based on custom database query results” between Zite and Encharge?
Yes — describe it in the box above and Knit's Integrations Agent researches Zite and Encharge'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.
What's the most common Databases & Warehouses + Marketing automation?
Syncing campaign and contact activity from Encharge into Zite on a schedule, so marketing metrics can be joined against product or sales data.
Does this need a specific reporting format?
No — the Agent maps Encharge's own fields into whatever table structure Zite expects, so it fits your existing schema rather than forcing a new one.