Docs · Connector reference

Factory Droid connector reference

Operations, inputs, troubleshooting, and questions for the Factory Droid connection.

Set up and verify the Factory Droid connection

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

Information your agent can use

Resource	Record identity	Start with	Page coverage
Sessions	`sessionId`	Top level	Cursor
Session messages	`id`	Sessions	Cursor
Computers	`id`	Top level	None configured
Computer metrics	`timestamp`	Computers	None configured
Organization users	`id`	Top level	Cursor
Global user credits limit	Not specified	Top level	None configured
User credits limits	`email`	Top level	None configured
Enterprise control changes	`revision`	Top level	Cursor
CI automation jobs	`repoFullName` + `filePath`	Top level	None configured
CI eligible repositories	`fullName`	Top level	None configured
CI repository owners	`login`	Top level	None configured
CI workflow scan	`repoFullName` + `filePath`	Top level	None configured
Wiki runs	`wikiRunId`	Top level	None configured

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.
Cursor: Cursor pagination. Continue from the returned cursor; an initial page is not a complete inventory.
None configured: No page continuation is configured for this resource. Check the response and any provider limits before treating it as a complete inventory.

When the Factory Droid 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.

Resolve parent resources first: Sessions, Computers. A matching display name is not enough for a child lookup.

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.

The next step needs a write

Use a separate authorized action or a person to make the change; broader credentials do not add a write operation to this connection.

See how an action proceeds and how to review an approval.

Questions about the Factory Droid connector

Can I use my existing agent with Factory Droid?

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 Factory Droid?

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 Factory Droid?

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

Does connecting Factory Droid 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.

Factory Droid connector overview Docs All connectors