IdentityCheck
Identity & SecurityConnect AI agents to IdentityCheck by StackGo, a KYC identity verification service. Agents create verification requests that invite a contact into a hosted capture session and read the media it captured, while the decision itself arrives at a webhook endpoint you configure in the vendor dashboard.
What This Integration Enables
This is a small connector on purpose, and reading it honestly is the fastest way to use it well. IdentityCheck by StackGo has exactly one write: Create Verification, which creates a KYC session for a contact and returns the verification ID plus a unique verification link. The Send Email toggle maps to the platform's emailUser field, so with it enabled IdentityCheck emails the link to the contact, and with it disabled the link comes back in the response for you to deliver through your own channel. The service always sends the required constants for a direct KYC verification. If the email address already belongs to an in progress verification, the API returns a 409 rather than creating a second session. The other three actions are reads over media: Get Verification Media Info lists the images captured during a session with their IDs, sizes, and names such as face, document-front, and document-back, Get Verification Image returns one of those as a base64 string with its dimensions, and Save Verification Image to File decodes it and writes it into FlowRunner file storage, returning a URL. The image count varies per session because applicants retake photos for lighting, shadows, or blur.
What the connector deliberately does not do is worth stating plainly, because building around a capability that is not there is the common failure here. There are no triggers, and there is no polling path either. The documented API surface is those four operations: there is no list verifications endpoint and no get verification status endpoint, so a flow cannot ask IdentityCheck whether a session has finished or what the decision was. Verification outcomes are delivered as webhook payloads sent through Svix, and those endpoints are configured by hand in the IdentityCheck dashboard under Account then Webhooks, which subscribes an endpoint of your choosing and does not create a FlowRunner trigger. The practical shape is therefore request and collect: your flow creates the verification, holds the verification ID against the case, and resumes on the signal that arrives at whatever endpoint you configured. Document capture, liveness, and the AML and sanctions screening around it all happen inside the IdentityCheck platform. What FlowRunner owns is who gets asked, when, and where the captured images end up.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Identity Step in an Application Pipeline
An application reaches the point where identity has to be established. The agent assembles the applicant's first name, last name, and email from the record, confirms with the onboarding owner that this is the right person and address, and runs Create Verification with Send Email enabled. IdentityCheck sends the applicant a link to capture their government issued ID and a selfie. The agent stores the returned verification ID on the case so that when the outcome arrives at the configured webhook endpoint it can be matched back to the right application without anyone searching a dashboard.
Delivering the Link Through Your Own Channel
A brokerage already has an established relationship with the applicant over a portal and does not want a separate email arriving from an unfamiliar sender. The agent runs Create Verification with Send Email disabled, which returns the idUrl without notifying anyone. The flow then delivers that link inside the portal message the applicant is already expecting, in the brand and tone they already recognise. The verification session is identical. The difference is that the applicant receives the request somewhere they have a reason to trust it, which is the single largest factor in whether they complete it at all.
Filing Captured Documents Into the Case Record
A verification session completes. The agent runs Get Verification Media Info to list what was actually captured, which varies because applicants retake photos. For each image it runs Save Verification Image to File, which decodes the base64 payload and writes a PNG or JPEG into FlowRunner file storage, returning a URL. The agent attaches those URLs to the case record alongside the verification ID and the image names, so the file holds the face capture and both document sides in one place. The images stop being an artifact of a session somewhere else and become part of a record with a retention owner.
Human-in-Loop Highlight
Create Verification with Send Email enabled sends a real human being a message asking them to photograph their government issued identity document and take a selfie. That message cannot be recalled, it arrives with all the shape of a phishing attempt, and it is exactly the kind of request a person should be suspicious of. Sending it to a stale address, to the wrong record after a merge, or to somebody who was never supposed to be asked is not a data quality problem, it is a trust problem with a customer and a set of ID images that now exist. So the agent stops before the send. It posts to the onboarding owner: "Ready to send an ID capture request to [name] at [email] for application [reference]. This asks them to photograph a government ID and take a selfie. Send now, send with the link only so we deliver it ourselves, or hold?" The owner confirms the recipient, and only then does the agent call Create Verification. The 409 the API returns when an email is already taken by an in progress verification is treated the same way: not as an error to retry around, but as a signal that someone is already mid session and the flow should ask before creating a second one. Everything after the send, listing captured media and filing the images, runs without a person in the path.
Agent Capabilities
4 actionsVerifications
1- Create Verification Creates a new KYC identity verification for a contact and returns the verification ID together with the unique verification link (idUrl). When Send Email is enabled, IdentityCheck emails the link to the contact so they can capture their government issued ID and a selfie. When it is disabled, the API only returns the link so you can deliver it through your own channel. The API responds with 409 if the email is already taken by an in progress verification. This is the connector's only write, and it is routed for confirmation before it runs.
Media
3- Get Verification Media Info Lists metadata for the images captured during a verification session, including image ID, size in bytes, and name such as face, document-front, or document-back. The number of images varies per session because users may retake photos due to lighting, shadows, or blur. Use the returned image IDs with Get Verification Image.
- Get Verification Image Retrieves a single image captured during a verification session as a base64 encoded string, together with its width and height in pixels. Image IDs come from Get Verification Media Info.
- Save Verification Image to File Retrieves an image captured during a verification session, decodes it from base64, and saves it to FlowRunner file storage, returning the file URL together with the image dimensions. Used to attach captured ID document and selfie images to a case record without handling base64 payloads downstream.
Frequently Asked Questions
What can FlowRunner do with IdentityCheck?
FlowRunner agents can run Create Verification, Get Verification Media Info, and Get Verification Image in IdentityCheck, plus 1 more action.
Does connecting IdentityCheck to FlowRunner require OAuth?
No. IdentityCheck connects to FlowRunner with an API key, no OAuth flow required.
Can IdentityCheck trigger a FlowRunner workflow automatically?
IdentityCheck doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with IdentityCheck
$100 in credits. No card required. Connect in minutes.