Connectors / Gusto

What Deixic does with Gusto.

Read only

Read employee and termination records to identify departures.

How Deixic helps with Gusto.

Read information
Review employees and terminations from Gusto as evidence and to check state.
Read only
Use the information to prepare a decision. Deixic changes nothing in Gusto through this connection.

Example workflow

Read terminations as the trigger for offboarding

Read the Gusto employees and terminations. List people whose employment has ended and the date, then name the accounts to check in Google Workspace, GitHub, and the identity provider.
  1. Read employee and termination records and match each departed person to the work email used in the other systems. Keep the Gusto identifier with the result.
  2. Check the termination’s effective date before preparing access removal. Keep the date and employee identifier with the access review.
  3. Prepare the supported removals in the connected systems for approval, read each back, and keep the receipts with the Gusto employee identifier in the job.

Check before you continue: This connection reads data from Gusto and does not change it. A contractor and an employee can appear in different record types; confirm the person type before treating a record as a termination.

Provider reference: Gusto API documentation

Use your existing agent with Deixic. Calls you route through Deixic follow your access and approval policy.

Provider access

Supported Gusto reads and actions.

Choose the reads and actions your task needs. Your connection’s permissions and your agent’s access determine what it can use.

Read data

  • Employees Read
  • Terminations Read

Actions

This connection does not expose a write or invoke action.

Permissions

Choose the access for Gusto.

Use a token issued for the account the agent should work in, check its owner, expiry, and resource access, and remember that replacing an expired token does not change the account’s permissions.

Connection
Bearer token
Supported operations
Read only
Reads
2
Actions
0
Provider permissions
Grant only the permissions needed for the task.

What you need to connect

  • Gusto company UUID
  • Gusto company access token

Deixic checks calls routed through its gateway and requests approval when your policy requires it.

Reference and troubleshooting

Gusto operation reference, troubleshooting, and questionsSOC 2 for Gusto

Connectors for related work

Tell us what you need from Gusto.

Bring one task. We’ll show you the access it needs and how Deixic helps.

Request early access

Connector guide by Deixic · Updated