Decide which Slack channels, Linear or Jira triggers, and GitHub comments can start a Devin session. Have every engineer link their accounts, and name a human owner for each pull request Devin opens.
When you need this
- Engineers want to tag Devin in bug threads and assign it tickets.
- Product or support staff will start sessions without opening the Devin web app.
- Pull requests from Devin arrive with no clear owner.
Evaluation criteria
Slack
Which Slack channels can start a session, and who can see the run?
Look forInvite the app to approved Slack channels, where @Devin starts a session and replies in the thread. Create a Slack channel such as #devin-runs so teams see each other's runs. Have each user link a Slack profile, and choose one Devin organization for the workspace before teams install separately.
Linear
Which tickets start work on their own?
Look forAssigning a ticket to Devin runs its default playbook, which is !plan on new connections. Add a label such as !implement to select another playbook. Filter automation triggers by team, label, and status. A trigger fires only when a ticket changes into a match. On Enterprise, map each Linear team to a Devin organization.
Jira
Does Devin join Jira as a Rovo agent or as a service user?
Look forUse Devin for Jira when Jira Cloud agent features are on. Assigning or @mentioning Devin then starts a session as the matching Devin user, with that person's permissions. When Rovo is off, connect a Jira service account over OAuth. Set automations to trigger on a label or an assignment.
GitHub
Who can start or steer a session from a pull request?
Look forAllow /devin comments on open pull requests from users with write access and a linked Devin account. Devin answers comments on pull requests its sessions are working on until the session is archived, and each reply uses credits. Decide who can trigger that work.
Ownership
Whose name is on the pull request?
Look forSet Open PRs as to User or User only so the requesting engineer owns the change. Automations and service users still open pull requests as Devin, so name an owner for each automation.
Automations
Which recurring work runs with nobody watching?
Look forGive each automation a security profile and a results channel. Triggers include Slack messages, GitHub or Linear events, schedules, and webhooks. Set a budget for each automation on Teams, where runs use shared on-demand credits.
Questions to ask vendors
- Which channels and ticket labels can start a Devin session, and who maintains that list?
- Have all engineers linked their Slack, Linear, and GitHub accounts so sessions and pull requests carry their names?
- Who approves pull requests requested by people outside engineering?
- Which automations run unattended, and which security profile governs each one?
Red flags
- Automation triggers on broad labels that start sessions for tickets nobody scoped.
- Pull requests opened as Devin with no named human owner.
- Review comments restarting sessions while nobody watches usage.
- Two departments trying to connect separate Devin organizations to one Slack workspace.
Products in this piece
Sources
- Official documentation
- 9
- Public source
- 1
- Devin docs: Integrations overview
- Devin docs: Slack
- Devin docs: Linear
- Devin docs: Jira integration
- Devin docs: GitHub integration
- Devin docs: Automations
- Devin docs: Security profiles
- Devin docs: Self-serve plans
- Devin docs: Common issues
- Vikram Sreekanti and Joseph E. Gonzalez (RunLLM), Frontier AI: One month of using Devin (Jan 23, 2025)