Agent + StackGo

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

Agent publishes 1 trigger event and 1 action on its public Zapier listing. That is what a StackGo connector would be built on.

CRM System of record Not connected yet

Request this integration Book a demo

What Agent is

Agent 3000 provides a Website, IDX, CRM and all the necessary marketing tools a REALTOR needs.

Description supplied by Agent.

The trigger

What starts a check

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

New Contact

The write-back

What StackGo puts back on the record

A Agent connector would write the outcome, the status and a link to the result onto the record by default. These are the fields StackGo can write on the systems it connects to today.

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 Agent

Create Contact

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

Questions

Common questions about Agent

What is an agent API?

There is no StackGo connector for Agent yet. Agent publishes 1 trigger events and 1 actions through Zapier, including “New Contact”, so building one is realistic. Requests decide the build order.

How would a check result show up in Agent?

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