When new verification decision in Veriff, sync it to Short.io.
When a verification decision is updated in Veriff, update relevant custom short links in Short.io.
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.
Short.io Explore Short.io →
TriggersFires when a shortened link created in Short.io is clicked.
Fires when a new shortened link is created in Short.io.
Creates a new shortened link in Short.io.
Tags a link's record in Short.io for tracking.
Retrieves click analytics for a link in Short.io.
Veriff Explore Veriff →
TriggersFires when a new user account is created in Veriff.
Fires when a new security or access event is logged in Veriff.
Fires when a scan, verification or risk check finishes in Veriff.
Creates a new user account in Veriff.
Deactivates a user's access in Veriff.
Runs a verification, fraud or risk check on a record in Veriff.
Common questions
Can Knit build “When new verification decision in Veriff, sync it to Short.io.” between Short.io and Veriff?
Yes — describe it in the box above and Knit's Integrations Agent researches Short.io and Veriff'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.