Accounting

Ignition + StackGo

Run compliance from inside Ignition. Checks start from a record and the result lands back on the client.

Ignition publishes 11 trigger events and 5 actions on its public Zapier listing. StackGo uses them today.

Accounting System of record Via ZapierIgnition integration currently powered by Zapier

Also listed under Client onboarding

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.

  • Service Accepted by Client
The write-back

What StackGo puts back on the record

Named fields on the Ignition record, not a link to a portal someone has to log into. Every field is optional — you choose which ones get written, and the ones carrying client information are marked so that choice is an informed one.

FieldWhat it holds
Verification status Outcome
Verified, Refer, Failed or Pending
Risk rating Outcome
The assessed rating and the date it was set
Last checked Outcome
The date the check completed, so monitoring has a baseline
Report link Outcome
A link to the full record, behind your StackGo login. The link travels; the data does not.
Verified name Personal data
Full legal name as it appears on the document
Date of birth Personal data
As verified against the document
Document checked Personal data
Type, issuing country and expiry
Screening result Personal data
Clear, or a potential match with the list that matched
Beneficial owners Personal data
The individuals behind an entity, each with their own status
Form responses Personal data
Whatever the intake form collected
Verification report (PDF) Personal data
The whole session: every field collected, the document images, the timestamps. Attach it where your retention obligation is to hold the evidence, not a link to it.
  • Outcome Carries no identity data. Safe anywhere your team already works.
  • Personal data Client information. Turn it on where the record has the right access controls, and leave it off where it does not.
Run it one-way if that suits you better

The two directions are independent. You can have Ignition start a check and write nothing back — the result stays in StackGo, behind your login, and Ignition 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.

How it lands in Ignition
  • Create Client
  • Create Deal

Ignition's own write operations. The result goes onto the record you already work in.

Everything else Ignition publishes

Ignition’s public integration surface

The rest of what Ignition exposes on Zapier, beyond the ones above. Any of these can be wired into a StackGo workflow.

10 more events
  • Contract Accepted (Legacy)
  • Ping
  • Proposal Accepted
  • Proposal Archived
  • Proposal Completed
  • Proposal Marked as Lost
  • Proposal Moved to Awaiting Acceptance
  • Proposal Revoked
  • Proposal Saved as Draft
  • Classic Proposal State Changed
3 more actions
  • Update Client
  • Find Client
  • Search Clients

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

Setting it up

Connected through Zapier

Verify the client the proposal was accepted by.

  1. Connect StackGo to Ignition through Zapier.
  2. Map the fields above to where you want them on the record.
  3. Choose the trigger — the event that should start a check.
  4. Run a test on yourself before you point it at a client.
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 “Service Accepted by Client”. The result comes back on the record you already work in.

How would a check result show up in Ignition?

Through Ignition’s own write operations: “Create Client”, “Create Deal”. You choose which fields are written, and you can also run it one-way, with nothing written back to Ignition at all.

Questions taken from what people actually search in Australia. We answer only the ones our own data answers.

Where this sits

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

Every step writes back to Ignition, so the client record stays the source of truth.

If you use Ignition, you probably also use

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.