Create identity verifications in IdentityCheck when a proposal is accepted in Ignition.
Create identity verifications in IdentityCheck when a proposal is accepted in Ignition.
See all IdentityCheck + Ignition 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.
IdentityCheck Explore IdentityCheck →
TriggersFires when a new user account is created in IdentityCheck.
Fires when a new security or access event is logged in IdentityCheck.
Fires when a scan, verification or risk check finishes in IdentityCheck.
Creates a new user account in IdentityCheck.
Deactivates a user's access in IdentityCheck.
Runs a verification, fraud or risk check on a record in IdentityCheck.
Ignition Explore Ignition →
TriggersFires when a new invoice is created in Ignition.
Fires when a payment is recorded in Ignition.
Fires when an invoice in Ignition passes its due date unpaid.
Fires when a new expense is recorded in Ignition.
Creates a new invoice in Ignition.
Records a payment against an invoice in Ignition.
Creates a new expense entry in Ignition.
Syncs a customer's billing record in Ignition.
Common questions
Can Knit build “Create identity verifications in IdentityCheck when a proposal is accepted in Ignition.” between IdentityCheck and Ignition?
Yes — describe it in the box above and Knit's Integrations Agent researches IdentityCheck and Ignition'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.