Skip to main content
Devin is an AI software engineer that works on tasks autonomously in its own environment. The Cargo integration lets a workflow launch a Devin session and use what it produced — structured output and pull requests — in downstream nodes.

​
Authentication

Connect to Devin with a service user API key. Create a service user under Settings → Service users, give it a role with the ManageOrgSessions and ViewOrgSessions permissions, and generate a key. The key is only shown once.

​
Connection details

Both are on the Settings → Service users page. The organization ID is part of every API path, so a wrong value fails the connection test the same way a wrong key does.

​
Devin actions

​
Launch agent

Create a Devin session and send it a task. Configuration The Playbook dropdown lists the organization and enterprise playbooks your service user can see. Preview Devin modes have to be enabled for your organization; leave the field empty to use the organization default. Output
The node completes as soon as the session is created — it does not wait for Devin to finish. The Devin API has no callback to announce that a session finished, so there is nothing to wait on without polling.
That means the output carries the session’s identity rather than its results: structured output, pull requests and ACUs consumed only exist once Devin has done some work, so they would always be empty here. Follow the session at its url, or read it back from the Devin API with the sessionId.

​
Use cases

Turn a qualified request into a pull request without a human in the loop.
Ask Devin to investigate a repository and return structured findings.
Run a playbook per incoming item so every session follows the same steps.
Launch one session per incoming issue and collect the pull requests they open.

​
Best practices

  1. Give Devin a complete prompt - Nothing downstream is waiting to answer a follow-up question
  2. Use playbooks for repeated work - They keep sessions consistent across records
  3. Set a max ACU limit - It bounds what a single run can cost
  4. Tag sessions launched from Cargo - It makes them easy to find in reporting, and it is how you correlate a workflow run with the sessions it started