When new or updated incident in ilert, sync it to Facebook Lead Ads.
When an incident occurs in ilert, sync event parameters to Facebook Lead Ads.
See all ilert + Facebook Lead Ads integrations or talk to a human
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.
ilert Explore ilert →
TriggersFires when a monitor or check in ilert raises an alert.
Fires when an incident is opened or updated in ilert.
Fires when a monitored site, service or alarm in ilert changes state.
Opens a new incident or alert in ilert.
Acknowledges an open incident in ilert.
Resolves an incident in ilert.
Facebook Lead Ads Explore Facebook Lead Ads →
TriggersFires when a new lead comes in from an ad campaign in Facebook Lead Ads.
Fires when Facebook Lead Ads records a conversion or offline event.
Fires when a new ad or campaign goes live in Facebook Lead Ads.
Sends an offline or server-side conversion event to Facebook Lead Ads.
Adds a contact to a custom audience or customer list in Facebook Lead Ads.
Removes a contact from a custom audience in Facebook Lead Ads.
Common questions
Can Knit build “When new or updated incident in ilert, sync it to Facebook Lead Ads.” between ilert and Facebook Lead Ads?
Yes — describe it in the box above and Knit's Integrations Agent researches ilert and Facebook Lead Ads'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.