Overview
Torii integrates with Devin and syncs:
| User Fields | License Types |
|---|---|
| Name, Email, Role | Devin |
- You can constantly stay updated with application information from our Integrations Page >> Integration Capabilities button >> Integration Capabilities table.
Requirements
To connect this integration, we require the following:
Accounts & Permissions
- A Devin Enterprise plan. Torii connects with an enterprise service user, which Teams plans do not have.
- An enterprise service user whose role includes the View Account Membership permission, to sync users.
- To also use Torii actions, give the role the Manage Account Membership permission instead. It includes View Account Membership, so one service user covers both.
Required keys
-
Enterprise service-user API key - starts with
cog_. -
Organization ID - starts with
org-.
How to Generate the Required Values
Follow these steps to generate the required values. For more details, see the Devin documentation: Enterprise quick start and Authentication.
Step 1: Create an enterprise service user and copy its API key
- In Devin, go to Enterprise settings > Devin API and open the Service users tab.
- Click Provision > Enterprise service user.
- Enter a descriptive display name (for example, "Torii").
- Select an enterprise role that includes View Account Membership, or Manage Account Membership if you plan to use actions.
- Copy the API key shown after the service user is provisioned.
Important
The API key is shown only once. Copy it right away and store it securely.
Step 2: Copy your Organization ID
- Open the organization you want to connect, go to Settings > Devin API, and find the Organization ID at the top of the page.
- Copy it. It starts with
org-.
How to Connect the Integration
- Go to the Integrations page in Torii.
- Search for Devin and click Connect.
- Enter the Enterprise service-user API key and the Organization ID.
- Click Connect.
Actions
Torii workflows can perform the following actions in Devin:
- Invite Devin enterprise user - invites a user to your Devin enterprise with the enterprise role you select. The user is not assigned to the connected organization, so they appear in Torii only after being assigned to it in Devin.
- Change Devin organization role - changes a user's role in the connected organization. Members who get access through an identity provider group cannot be changed this way.
- Remove user from Devin organization - removes a user from the connected organization only. Members who get access through an identity provider group cannot be removed this way.
Actions require the service user's role to include the Manage Account Membership permission.
Q&A
Q: What should I enter in the "Account Name" field?
A: The Account Name field lets you connect multiple Devin accounts to Torii. The value can be anything you choose. It is only used to distinguish between your connected accounts. Make sure to use a unique Account Name for each account: connecting a different account with an Account Name that is already in use will overwrite the existing account's data, so choosing distinct names is your responsibility.
For any further questions, please contact Torii Support.