Devin AI Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Devin AI endpoint. Use the Devin AI destination connector to programmatically launch sessions, send instructions to active sessions, manage playbooks and secrets, and maintain your organization's knowledge base — all as part of an automated Nexla data pipeline.

Devin AI

Create a Devin AI Destination

1. Click the + icon on the Nexset that will be sent to the Devin AI destination, and select the Send to Destination option from the menu.

2. Select the Devin AI connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Devin AI organization, and click Next; or, create a new Devin AI credential for use in this flow.

3. In Nexla, Devin AI destinations can be created using pre-built endpoint templates, which expedite destination setup for common Devin AI endpoints. Each template is designed specifically for the corresponding Devin AI endpoint, making destination configuration easy and efficient.
   • To configure this destination using a template, follow the instructions in Configure Using a Template.

   Devin AI destinations can also be configured manually, allowing you to send data to Devin AI endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Devin AI endpoints. Each template is designed specifically for the corresponding Devin AI endpoint, making destination setup easy and efficient.

• To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

  Create Session

  Launches a new Devin AI session with a prompt and optional configuration parameters. Use this endpoint to programmatically kick off Devin engineering tasks from Nexla — for example, triggering a Devin session whenever a new work item arrives in your pipeline, or automating session creation as part of a broader orchestration workflow.

  • The request body is sent as JSON. Ensure your Nexset contains the fields required by the Devin AI Create Session API, including a message field with the prompt text you want Devin to act on.

  • Optional fields supported by the Create Session endpoint include:

    • snapshot_id: A snapshot ID to use as the starting environment for the session.
    • playbook_id: A playbook ID to apply to the session, providing Devin with structured instructions.
    • idempotent_id: A unique identifier to prevent duplicate session creation if the same request is submitted more than once.
    • max_acu_limit: The maximum number of ACUs (AI Compute Units) that this session may consume before being automatically stopped.
  • After a session is successfully created, the Devin AI API returns the new session ID and its initial status. Use the Response Webhook option in the manual configuration section to capture this response automatically in a new Nexla source.

  For complete request and response schema details, see the Devin AI API reference for Create Session.

  Send Session Message

  Sends a follow-up message or instruction to an active Devin AI session, allowing interactive steering of the agent. Use this endpoint to provide Devin with additional context, updated requirements, or corrective feedback mid-session — for example, automatically forwarding new issue comments or CI failure logs to an in-progress Devin session.

  • Enter the unique identifier of the session to which the message will be sent in the Session ID field.

    • The Session ID is a required field. It can be obtained from the response when creating a session, from the List Sessions data source endpoint, or from the Devin AI web app.
    • The session must be active (not terminated or completed) to accept new messages.
  • The message content is sent as a JSON body. Ensure your Nexset contains a message field with the text of the instruction or information you want to send to Devin.

  For complete request and response schema details, see the Devin AI API reference for Send Session Message.

  Terminate Session

  Terminates a running or queued Devin AI session, freeing resources and stopping any work in progress. Use this endpoint to programmatically cancel sessions that are no longer needed — for example, aborting a session when a related work item is closed, a deployment is cancelled, or a time or cost limit is reached.

  • Enter the unique identifier of the session to terminate in the Session ID field.

    • The Session ID is a required field. It can be obtained from the List Sessions data source endpoint or from the Devin AI web app.
  • This operation sends a DELETE request to the Devin AI API. No request body is required.

  :::warning Important Terminating a session is irreversible. Any work Devin has completed but not yet committed or saved may be lost. Confirm that the session is no longer needed before sending a terminate request. :::

  For complete details on the terminate session endpoint, see the Devin AI API reference for Terminate Session.

  Create Playbook

  Creates a new organization-level playbook that defines repeatable Devin workflows. Playbooks provide structured instructions and context to Devin sessions, enabling consistent, reusable engineering processes. Use this endpoint to programmatically provision playbooks from external systems — for example, publishing approved workflow templates from a documentation system into Devin.

  • The request body is sent as JSON. Ensure your Nexset contains the fields required by the Devin AI Create Playbook API, including a name and the playbook's instructions content.
  • After a playbook is created, it becomes available to all sessions in your organization via the playbook_id parameter on the Create Session endpoint.

  For complete request and response schema details, see the Devin AI API reference for Create Playbook.

  Update Playbook

  Updates an existing playbook's instructions, name, or metadata. Use this endpoint to keep playbooks current as organizational processes evolve — for example, automatically updating a playbook whenever a corresponding process document is revised in an external system.

  • Enter the unique identifier of the playbook to update in the Playbook ID field.

    • The Playbook ID is a required field. Playbook IDs can be obtained from the List Playbooks data source endpoint or from the Devin AI web app.
  • The updated playbook content is sent as a JSON body using a PUT request, which replaces the full playbook definition. Ensure your Nexset contains all required playbook fields, not just the fields you wish to change.

  For complete request and response schema details, see the Devin AI API reference for Update Playbook.

  Delete Playbook

  Deletes an existing playbook by its unique ID. Use this endpoint to programmatically remove obsolete or retired playbooks from your Devin AI organization — for example, cleaning up playbooks that correspond to deprecated processes or archived projects.

  • Enter the unique identifier of the playbook to delete in the Playbook ID field.

    • The Playbook ID is a required field. Playbook IDs can be obtained from the List Playbooks data source endpoint or from the Devin AI web app.
  • This operation sends a DELETE request. No request body is required.

  :::warning Important Deleting a playbook is permanent and cannot be undone. Verify that the playbook is no longer in use before proceeding. :::

  For complete details, see the Devin AI API reference for Delete Playbook.

  Create Secret

  Stores a new organization-level secret — such as an API key or credential — that Devin sessions can access at runtime. Use this endpoint to programmatically provision secrets in Devin AI from a secrets management pipeline or onboarding workflow.

  • The request body is sent as JSON. Ensure your Nexset contains the required fields for the Devin AI Create Secret API, including the secret's name and value.
  • Secrets stored in Devin AI are available to all sessions in your organization at runtime. Secret values are write-only — they cannot be retrieved through the API after creation.

  :::warning Important Secret values passed through this destination will be transmitted to the Devin AI API over HTTPS. Ensure that your Nexset does not expose sensitive values in logs or sample payloads. Review your Nexla data flow access controls before sending secrets through this endpoint. :::

  For complete request and response schema details, see the Devin AI API reference for Create Secret.

  Delete Secret

  Deletes an organization-level secret by its unique ID. Use this endpoint to remove secrets that are no longer needed, have been rotated, or correspond to revoked credentials.

  • Enter the unique identifier of the secret to delete in the Secret ID field.

    • The Secret ID is a required field. Secret IDs can be obtained from the List Secrets data source endpoint.
  • This operation sends a DELETE request. No request body is required.

  :::warning Important Deleting a secret is permanent. Any Devin sessions that reference this secret will lose access to it immediately. :::

  For complete details, see the Devin AI API reference for Delete Secret.

  Create Knowledge Note

  Creates a new organization-level knowledge note so Devin can learn organization-specific context. Knowledge notes are tips, instructions, and background information that Devin automatically recalls as relevant when working on tasks. Use this endpoint to programmatically populate Devin's knowledge base from external documentation systems, wikis, or knowledge management platforms.

  • The request body is sent as JSON. Ensure your Nexset contains the required fields for the Devin AI Create Knowledge Note API, including the note's title and body content.
  • Knowledge notes created through this endpoint are immediately available to all sessions in your organization.

  For complete request and response schema details, see the Devin AI API reference for Create Knowledge Note.

  Update Knowledge Note

  Updates an existing knowledge note's title, body, or metadata. Use this endpoint to keep Devin's knowledge base current as organizational processes, codebases, or conventions evolve — for example, automatically updating knowledge notes whenever corresponding documentation is revised in an external system.

  • Enter the unique identifier of the knowledge note to update in the Note ID field.

    • The Note ID is a required field. Note IDs can be obtained from the List Knowledge Notes data source endpoint.
  • The updated note content is sent as a JSON body using a PUT request, which replaces the full note definition. Ensure your Nexset contains all required note fields, not just the fields you wish to change.

  For complete request and response schema details, see the Devin AI API reference for Update Knowledge Note.

  Delete Knowledge Note

  Deletes a stale or incorrect knowledge note by its unique ID. Use this endpoint to remove outdated information from Devin's knowledge base, ensuring that Devin is not influenced by incorrect or obsolete context.

  • Enter the unique identifier of the knowledge note to delete in the Note ID field.

    • The Note ID is a required field. Note IDs can be obtained from the List Knowledge Notes data source endpoint.
  • This operation sends a DELETE request. No request body is required.

  :::warning Important Deleting a knowledge note is permanent. Devin will no longer have access to this knowledge in future sessions. :::

  For complete details, see the Devin AI API reference for Delete Knowledge Note.

Configure Manually

Devin AI destinations can be manually configured to send data to any valid Devin AI v3 API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Devin AI API after each call to a new Nexla webhook data source.

API Method

1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

2. Select the API method that will be used for calls to the Devin AI API from the Method pulldown menu. Common methods for Devin AI destinations include:

   • POST: For creating new sessions, playbooks, secrets, or knowledge notes
   • PUT: For replacing existing playbooks or knowledge notes with updated content
   • DELETE: For removing sessions, playbooks, secrets, or knowledge notes

Data Format

3. Select the format in which the Nexset data will be sent to the Devin AI API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. Devin AI API endpoints accept JSON format — select application/json as the content format.

API Endpoint URL

4. Enter the URL of the Devin AI API endpoint to which you want to send the Nexset data in the URL field. All Devin AI v3 organization-scoped endpoints follow the base URL pattern https://api.devin.ai/v3/organizations/{organization_id}/. For operations on specific resources, append the resource ID to the end of the URL (e.g., https://api.devin.ai/v3/organizations/{organization_id}/sessions/{session_id}).

Request Headers

Optional

• If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

  You do not need to include the Authorization header — it is automatically injected by Nexla using the API key configured in your Devin AI credential.

Exclude Attributes from the Call

Optional

• If any record attributes in the Nexset should be omitted when sending data to this Devin AI destination, select the attributes from the Exclude Attributes pulldown menu.

• Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching

Optional

1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Most Devin AI API endpoints accept a single resource per request. Batching is most appropriate when sending data to custom or bulk endpoints that accept arrays. Review the Devin AI API documentation to confirm whether your target endpoint supports batched requests before enabling this option.

Response Webhook

Optional

Nexla can automatically send the response received from the Devin AI API after each call to a new Nexla webhook data source. This option allows you to capture session IDs returned after creating sessions, track the status of each API call, and chain downstream workflows based on Devin AI API responses.

• To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload

Sample request payloads containing a portion of the Nexset data that will be sent to the Devin AI API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

• Click on a sample request payload to expand it and view the complete payload content.
• Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)

After all endpoint settings have been configured, Nexla can send a test payload to the Devin AI API to ensure that the destination is configured correctly.

1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Devin AI API using the current settings.

Save & Activate the Destination

• Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Devin AI endpoint, open the destination resource menu, and select Activate.

  The Nexset data will not be sent to the Devin AI API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.