Send identity checks from a Slack channel

Slack and the compliance workflow around it.

Slack publishes 13 trigger events and 25 actions on its public Zapier listing. A trigger that carries the person’s name and email can start a StackGo check.

Communication Across the workflow Via ZapierSlack integration currently powered by Zapier LiveThe Slack integration is live and in use.

Also listed under Project management

How the StackGo and Slack integration works
What Slack is

Slack is a platform for team communication: everything in one place, instantly searchable, available wherever you go. Offering instant messaging, document sharing and knowledge search for modern teams.

Description supplied by Slack.

Where it fits

Across the workflow, not at a step

A chat or support tool does not sit at one step of a compliance workflow. It carries the workflow to the people who have to act on it — which is why it belongs here, and why pinning it to Intake or Monitor would be wrong.

A check can start from
  • New Message Posted to Channel
What StackGo sends to Slack

An outcome, not a record. Slack is not your system of record, so it is told what happened — never the client's identity data. The verification detail stays where it belongs.

FieldWhat it holds
What happened Outcome
A check cleared, referred or failed
Who it was for Outcome
The client name already in your system — no identity data
When Outcome
The time it completed, so the notification is actionable
Where the record is Outcome
A link back to the full record, behind your login
  • Outcome Carries no identity data. Safe anywhere your team already works.
Run it one-way if that suits you better

The two directions are independent. You can have Slack start a check and write nothing back — the result stays in StackGo, behind your login, and Slack is never touched. Or write back without a trigger, and start checks by hand. Firms whose system of record is visible to support staff, contractors or an outsourced team often choose trigger-only for exactly that reason.

Everything else Slack publishes

Slack’s public integration surface

The rest of what Slack exposes on Zapier, beyond the ones above. A trigger that carries a person’s name and email can start a check. StackGo has no Zapier trigger of its own, so these actions are not run from a StackGo result.

12 more events
  • New Public Message Posted Anywhere
  • New Channel
  • New Team Custom Emoji
  • New File
  • New Mention
  • New Message From Query
  • New Channel Member
  • New Reaction Added in a Channel
  • New Message Posted to Private Channel
  • New Pushed Message
  • New Saved Message
  • New User
16 actions
  • Add Reaction
  • Add Reminder
  • Archive Conversation
  • Cancel Scheduled Message
  • Invite User to Channel
  • Send Channel Message
  • Create Canvas
  • Delete Message
  • Send Direct Message
  • Edit Canvas
  • Edit Message
  • Create Channel
  • Send Private Channel Message
  • Request Approval
  • Set Channel Topic
  • Update Profile

Names are Slack’s own, read from its public Zapier listing on 23 October 2026.

Setting it up

Connected through Zapier

Post a name and email in your checks channel to send the identity check; the result is in StackGo.

Set up once · Before your first check

One Zap: New Message Posted to Channel starts Create Verification

A one-off set-up before your first check: one Zap, built once, watches your checks channel. A step in the Zap splits the message into name and email. Use the API key from StackGo, under Integrations, Zapier.

The Zap: Slack’s New Message Posted to Channel trigger starts IdentityCheck’s Create Verification action, with the name and email from the message mapped across.
  • Built once, runs for every client. Use the API key from StackGo, under Integrations, Zapier.
  • The trigger names are Slack’s own, exactly as they appear in Zapier.
How it runs

From a message in Slack to a verified client

Someone on your team posts a name and email in your checks channel. The Zap emails that person a check link, they verify on their phone, and StackGo emails your team the result.

How it runs, in five steps: post the name and email in the Slack channel; Zapier’s New Message Posted to Channel trigger fires; Create Verification emails the check link; the client verifies on their phone; the result and full report are in StackGo.
  1. Post their name and email. In your team’s checks channel, post the client’s name and email as a message.
  2. New Message Posted to Channel. The message fires Zapier’s trigger for that one channel. The Zap splits it into name and email.
  3. Create Verification. The Zap passes the client’s name and email to StackGo, which emails the check link.
  4. The client verifies. A short form if you ask for one, then ID photo and selfie on their phone.
  5. Result in StackGo. Result and full report in StackGo, and your team gets an email. Nothing is posted back to Slack.
Step 1 · Start in Slack

Post the client’s name and email in your Slack checks channel

Post the client’s name and email as one message in your checks channel.

A Slack channel called id-checks with a message holding the client’s name and email, ready to send, and the posted message.
  1. Open your team’s checks channel. One channel set aside for checks. Ours is called #id-checks; you name your own.
  2. Type the client’s name and email as one message. The Zap splits it into name and email for StackGo. The check link goes to this email.
  3. Send it. A new message in that channel is what fires New Message Posted to Channel.
Step 2 · The client verifies

On the client’s phone, a few minutes, nothing to type

Everything happens on the client’s own phone, from the email StackGo sends.

Four phone screens: the IdentityCheck email, an optional short form, photographing the ID, and taking a selfie.
  1. Open the link. An email from IdentityCheck, sent on behalf of your business.
  2. A few questions (optional). Only if you have set up a form: details, consent or a few questions.
  3. Photograph the ID. Passport, driver licence or national ID card.
  4. Take a selfie. A quick photo to match their face to the ID.
Step 3 · Your team is told

StackGo emails your team when the check is complete

StackGo emails your team the result as soon as the check is complete.

The email StackGo sends your team: the result in the subject line, a View details button, and the PDF report when attachments are turned on.
  1. The result is in the subject line. It goes to the Notification Email set in StackGo, under Account, Notifications.
  2. View details opens the full report in StackGo.
  3. The PDF report can be attached too. Ask us to turn it on.
Step 4 · The full report

The result and the full report in StackGo

The report records the document, date of birth, ID and selfie images, and a timeline of the check. Download it as a PDF for your records.

The verification report in StackGo: result Positive, document type, country, number, date of birth, expiry, the ID and selfie images, and a Download PDF button.
Questions

Common questions about Slack

What is Slack integration?

StackGo connects to Slack through Zapier, and a check can start from an event like “New Message Posted to Channel”. Slack is then told the outcome — cleared, referred or failed — while the verification record itself stays in your system of record.

Does StackGo write the result back to Slack?

Not automatically. Through Zapier, nothing is written onto the Slack record: IdentityCheck sends results by webhook, not as a Zapier trigger. StackGo emails your team when the check is complete, and the result and full report are in StackGo. If you need the result on the record, it can be set up from that webhook.

What does the client have to do?

Open the email from IdentityCheck on their phone, answer a short form if you have set one up, photograph their ID and take a selfie.

How does my team find out the result?

StackGo emails the Notification Email set under Account, Notifications, with the result in the subject line and a link to the full report. The PDF report can be attached if you ask us to turn it on.

Can something other than “New Message Posted to Channel” start a check?

Keep one channel just for checks: every message posted in it starts a check, and each check is charged. A filter step in the Zap can skip messages without an email address. Talk to us if a different moment suits your process better.

Where this sits

Slack sits beside the work, not inside it.

The compliance work happens in the five workflows below. Slack is where a check can start, or where the result lands.

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.