Store ad campaign leads in a central database
When a potential customer submits a form through an ad in Hyros, automatically write their contact details to a table in Ninox.
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.
Hyros Explore Hyros →
TriggersFires when a new lead comes in from an ad campaign in Hyros.
Fires when Hyros records a conversion or offline event.
Fires when a new ad or campaign goes live in Hyros.
Sends an offline or server-side conversion event to Hyros.
Adds a contact to a custom audience or customer list in Hyros.
Removes a contact from a custom audience in Hyros.
Ninox Explore Ninox →
TriggersFires when a new row is added to a table in Ninox.
Fires when an existing row changes in Ninox.
Fires when a scheduled query in Ninox finishes running.
Runs a SQL query against Ninox and returns the result.
Writes a new or updated row to Ninox.
Syncs a table in Ninox with data from another source.
More Hyros + Ninox workflows
See all Hyros + Ninox integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Store ad campaign leads in a central database” between Hyros and Ninox?
Yes — describe it in the box above and Knit's Integrations Agent researches Hyros and Ninox'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.
How do offline conversions in Ninox get sent back to Hyros?
When data in Ninox updates to show a successful purchase or offline conversion, an event can be sent directly to Hyros to measure campaign impact.
Can I build ad target audiences from database records in Ninox?
Yes, inserting or updating customer records in Ninox can automatically add or remove those users from custom targeting segments in Hyros.