Verify clients when they accept your Ignition proposal

Start compliance from Ignition. A new record starts the check, and StackGo holds the result.

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

Accounting System of record Via ZapierIgnition integration currently powered by Zapier BetaThe Ignition integration works today and is still being refined. Talk to us before you roll it out.

Also listed under Client onboarding

How the StackGo and Ignition integration works · Watch the video: client ID checks for accounting practices using Ignition
What Ignition is

Ignition makes it simple to engage clients, get paid and run your business on autopilot. From impressive online proposals to automated engagement letters and payments, we free you up to focus on what matters most.

Description supplied by Ignition.

The trigger

What starts a check from Ignition

You do not open StackGo. A change in the system starts the work, and the system stays your source of truth.

  • Proposal Accepted

Ignition’s other proposal triggers, such as Proposal Completed, can start a check instead. Service Accepted by Client fires once for each service in a proposal, so it would send the client more than one check link. Talk to us if a different moment suits your process better.

The result

Where the result goes

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

Everything else Ignition publishes

Ignition’s public integration surface

The rest of what Ignition 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.

8 more events
  • Proposal Archived
  • Proposal Completed
  • Proposal Marked as Lost
  • Proposal Moved to Awaiting Acceptance
  • Proposal Revoked
  • Proposal Saved as Draft
  • Classic Proposal State Changed
  • Service Accepted by Client
3 actions
  • Create Client
  • Create Deal
  • Update Client

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

Setting it up

Connected through Zapier

Verify the client the proposal was accepted by.

How it runs

From an accepted proposal in Ignition to a verified client

Your team does nothing extra. The client accepting your proposal in Ignition starts the check through Zapier, the client verifies on their phone, and StackGo returns the result.

How it runs, in five steps: the client signs the proposal in Ignition; Proposal Accepted fires in Zapier; StackGo Create Verification emails the check link; the client verifies on their phone; the result is in StackGo.
  1. The client signs. They accept your proposal in Ignition, or you accept it on their behalf.
  2. Proposal Accepted. Once every signatory has signed, Ignition fires Zapier’s Proposal Accepted trigger.
  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. The Zap gets the check link back.
Step 1 · Start in Ignition

The client accepts your proposal in Ignition

Send proposals the way you do today. When the client signs, the check starts. If they agree another way, Accept on client’s behalf counts too.

The Ignition Proposals tab filtered to Accepted, with pins on the client name and the Accepted status, and the proposal’s activity showing who signed, when and where.
  1. A signed proposal moves to Accepted. That is the moment Proposal Accepted fires.
  2. The client’s name and email carry through to StackGo, so nobody types them twice.
  3. Every signatory signs first. With several signatories, the trigger waits until all of them have signed.
Step 2 · Connect through Zapier

One Zap: Proposal Accepted starts Create Verification

You build the Zap once. From then on, every accepted proposal passes the client’s name and email to StackGo, which emails them the check link.

The Zap. Trigger: Ignition, Proposal Accepted. Action: IdentityCheck by StackGo, Create Verification, with first name, last name and email taken from the client on the proposal.
  • Built once, runs for every client. Use the API key from StackGo, under Integrations, Zapier.
  • The trigger names are Ignition’s own, exactly as they appear in Zapier.
Step 3 · 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 4 · Your team is told

StackGo emails your team when the check is complete

Point the Notification Email at a shared inbox so the whole team sees each result.

The result email from IdentityCheck: subject Identity Verification Decision for priya.nair@example.com: positive, showing the name and a Positive result, 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 5 · The result

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 Ignition

Does ignition have an API?

StackGo connects to Ignition through Zapier, and a check can start from an event like “Proposal Accepted”. StackGo emails your team the result, and the full report is held in StackGo.

Does StackGo write the result back to Ignition?

Not automatically. Through Zapier, nothing is written onto the Ignition 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 “Proposal Accepted” start a check?

Ignition’s other proposal triggers, such as Proposal Completed, can start a check instead. Service Accepted by Client fires once for each service in a proposal, so it would send the client more than one check link. Talk to us if a different moment suits your process better.

Where this sits

Ignition is the record. StackGo runs the steps around it.

Ignition is where a check starts. StackGo runs the steps and keeps the record of each one.

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.

Cookie settings

Choose which optional cookies we can use. You can change this at any time from Cookie settings at the bottom of every page.