By default, the outcome, the status and a link to the result. These are the fields StackGo can write on the systems it connects to today; a Assignar connector would offer the same.

Verification status
Risk rating
Last checked
Report link
Verified name
Date of birth
Document checked
Screening result
Beneficial owners
Form responses
Verification report (PDF)

Personal fields are off by default. What goes back to your CRM explains the default; what each field holds is set out in what “integrates with” actually means.

How it lands in Assignar

Create Client
Create Contact
Create Order Task
Create Relational Contact

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

Everything else Assignar publishes

Assignar’s public integration surface

The rest of what Assignar exposes on Zapier, beyond the ones above. This is the raw material a connector would use.

14 more events

New Task
New Timesheet
New Timesheets Raw
New Activity
New Asset
New Charge Code
New Digital Docket
New Order
New Order Task
New Project
New Site Diary
New Skill
New Supplier
New User

12 more actions

Create Activity
Create Asset
Create Charge Code
Create Competency
Create Induction
Create Journal
Create Order
Create Project
Create Supplier
Create Task
Create Timesheet
Create User

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

Questions

Common questions about Assignar

Which Assignar events can start a compliance check?

“New Client”, “New Contact”. These are Assignar’s own trigger names from its public Zapier listing. StackGo does not connect to Assignar yet, so they show where a connector would start.

How would a check result show up in Assignar?

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