Skip to main content

​
Devin

Shanone’s Devin integration gives your agent 38 tools for Cognition’s Devin AI software engineer: sessions, playbooks, knowledge notes, schedules, secrets, PR reviews, files, and session insights.

​
Getting Started

1

Get an API Key and Organization ID

In Devin, go to Settings → Service Users to create a service user and get its API Key along with your Organization ID.
2

Add credentials to Shanone

Open Integrations in the Shanone dashboard, select Devin, and enter both the API Key and Organization ID — both are required.
3

Retry your request

Once saved, shanone_execute_tool calls for devin_* tools will succeed.

​
Available Tools

Shanone provides 38 tools for Devin, organized into these categories:
devin_list_sessions, devin_get_session, devin_create_session, devin_send_message, devin_update_session_tags, devin_terminate_session, devin_archive_session, devin_get_session_messages, devin_get_session_tags, devin_append_session_tags, devin_create_session_advanced
devin_list_knowledge_notes, devin_get_knowledge_note, devin_create_knowledge_note, devin_update_knowledge_note, devin_delete_knowledge_note, devin_list_knowledge_folders
devin_list_playbooks, devin_get_playbook, devin_create_playbook, devin_update_playbook, devin_delete_playbook
devin_list_schedules, devin_get_schedule, devin_create_schedule, devin_update_schedule, devin_delete_schedule
devin_upload_file, devin_get_session_files, devin_download_attachment
devin_get_session_insights, devin_generate_session_insights, devin_list_sessions_with_insights
devin_list_secrets, devin_create_secret, devin_delete_secret
devin_trigger_pr_review, devin_get_pr_review_status

​
Common Use Cases

Delegate coding tasks

Create a Devin session with a task description and follow up with clarifications as it works

Reusable playbooks

Codify a recurring workflow as a playbook and reuse it across future sessions

Automated PR reviews

Trigger a Devin PR review on a new pull request and check its status before merging

Scheduled maintenance

Set up a recurring schedule for Devin to run routine maintenance or dependency updates

​
Troubleshooting

Devin’s v3 API requires both the API Key and Organization ID together — check that both fields were saved correctly in the Integrations page, since the API Key alone can’t resolve which organization’s sessions to operate on.
Messages can only be sent to sessions with status_detail of waiting_for_user — check devin_get_session first; if Devin is still working, the message queues but won’t be processed until it’s ready for input.
Check devin_get_session for status: error and inspect devin_get_session_messages — this usually indicates the task description referenced inaccessible resources (e.g. a repo the org’s Devin instance isn’t connected to).