← Docs

Docs · Connector reference

Gusto connector reference

Operations, inputs, troubleshooting, and questions for the Gusto connection.

Set up and verify the Gusto connection

  1. Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
  2. Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
  3. Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
  4. Review the retrieved information, retain its identifiers, and keep any later change in a separate, explicitly authorized step.

Information your agent can use

ResourceRecord identityStart withPage coverage
EmployeesuuidTop levelPage number
Record identity
Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with
Resolve the parent identifier first.
Page number
Page-number pagination. Keep filters and ordering consistent while checking successive pages.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Read
Retrieves information; check the returned scope and identifiers before use.
OperationEffectApprovalProvider permissionsInputs
Employees ListReadBy policyNone named4
Terminations ListReadBy policyNone named1

Inputs by operation

Employees List Read
Inputs for Gusto Employees List
InputRequirementAccepted value
company_idRequiredstringMinimum characters: 1Maximum characters: 64
pageOptionalintegerMinimum: 1Maximum: 100000
perOptionalintegerMinimum: 1Maximum: 100
terminatedOptionalboolean
Terminations List Read
Inputs for Gusto Terminations List
InputRequirementAccepted value
employee_idRequiredstringMinimum characters: 1Maximum characters: 64

When the Gusto task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the bearer token connection and its access to the specific resource; a successful connection does not establish access to every object.

Compare the lookup against one known record first, and keep an empty response separate from a permissions error.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

Questions about the Gusto connector

Can I use my existing agent with Gusto?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Gusto?

This connector supports reads. Use a configured connection to retrieve information and prepare a recommendation; it provides no action for changing provider data, even if the provider’s API offers writes.

What do I need to connect Gusto?

Prepare Gusto company UUID, Gusto company access token; the connection uses Bearer token, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Gusto keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.