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 Connecteam 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 Connecteam

Create User Note
Create Job
Create Job With Sub-Jobs
Create Task

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

Everything else Connecteam publishes

Connecteam’s public integration surface

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

10 more events

Clock In
Clock Out
Manager Field Updated
New Form Submission
New Shift in Scheduler
Updated Shift in Scheduler
Task Completed
Task Published
User Archived
New User

13 more actions

Archive User
Clock In
Clock Out
Create Job With Sub-Jobs
Create Shift
Create Timesheet Row
Create Time Off Request
Create User
Delete Shift
Send Message in Channel/Team
Send Private Message (DM)
Update Form Submission
Update User Custom Fields

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

Questions

Common questions about Connecteam

Does Connecteam integrate with teams?

There is no StackGo connector for Connecteam yet. Connecteam publishes 11 trigger events and 19 actions through Zapier, including “User Updated”, so building one is realistic. Requests decide the build order.

How would a check result show up in Connecteam?

Through Connecteam’s own write operations: “Create User Note”, “Create Job”, “Create Job With Sub-Jobs”, “Create Task”. You choose which fields are written, and you can also run it one-way, with nothing written back to Connecteam at all.