Finding Integration Details for Execution Tools

Created by Matthew Chartier, Modified on Sun, 28 Dec, 2025 at 11:10 AM by Matthew Chartier

Overview


To allow Agiloop INVENT to push features, stories, and tasks into your execution tools, you must provide a small set of integration details in Project Settings → Push To.


Each tool requires different information. This article shows you exactly where to find each required value.


Jira Integration Details


Agiloop requires the following values for Jira:

  • Base URL

  • Username

  • API Token

  • Project Key


1. Base URL


Your Jira Base URL is the URL of your Jira Cloud instance.


Example:

https://yourcompany.atlassian.net

You can copy this directly from your browser while logged into Jira.


2. Username


Your Jira username is the email address associated with your Atlassian account.


This must match the account that owns the API token.


3. API Token


Jira requires an API token (not your password).


How to create an API token:

  1. Go to Atlassian API Tokens:

    https://id.atlassian.com/manage-profile/security/api-tokens

  2. Click Create API token

  3. Give it a label (e.g., “Agiloop INVENT”)

  4. Copy the generated token


⚠️ Store this token securely. It will not be shown again.


4. Project Key


The Project Key identifies which Jira project items should be created in.


How to find it:

  • Open your Jira project

  • Look for the short key shown next to issues (e.g., AID-123)

  • The prefix (AID) is your Project Key


Azure DevOps (ADO) Integration Details


Agiloop requires the following values for Azure DevOps:

  • Base URL

  • API Token

  • Project Key


1. Base URL


Your Azure DevOps Base URL usually follows this format:

https://dev.azure.com/yourorganization

Or, for older organizations:

https://yourorganization.visualstudio.com

You can copy this from your browser while logged into Azure DevOps.


2. API Token (Personal Access Token)


Azure DevOps uses Personal Access Tokens (PATs).


How to create a PAT:

  1. Go to Azure DevOps:

    https://dev.azure.com

  2. Click your profile picture → Personal access tokens

  3. Click New Token

  4. Set:

    • Scope: Work Items (read & write)

    • Expiration as appropriate

  5. Create and copy the token


⚠️ Store this token securely. It will not be shown again.


3. Project Key


The Project Key is simply the Azure DevOps project name.


You can find this:

  • In the project selector dropdown

  • In the URL when viewing the project


Trello Integration Details


Agiloop requires the following values for Trello:

  • API Key

  • Token

  • Board ID


1. API Key


How to find your Trello API Key:

  1. Go to Trello’s developer page:

    https://trello.com/app-key

  2. Copy the API Key shown at the top of the page


2. Token


How to generate a Trello token:

  1. From the same page:

    https://trello.com/app-key

  2. Click the Token link

  3. Authorize access

  4. Copy the generated token


3. Board ID


How to find a Trello Board ID:

  1. Open the Trello board you want to push into

  2. Add .json to the end of the board URL in your browser

  3. Search for "id" at the top of the JSON response

  4. Copy the board’s id value


Alternatively, you can use:

https://developer.atlassian.com/cloud/trello/rest/api-group-boards/


After You’ve Collected the Details


Once you have the required values:

  1. Open Project Settings in Agiloop INVENT

  2. Select Push To

  3. Choose the destination tool

  4. Enter the required values

  5. Verify the connection


When connected successfully, Agiloop can push features and stories directly into your execution tool.


Need Help?


If you run into issues:

  • Double-check permissions on API tokens

  • Ensure the project or board exists

  • Contact support if you need help validating your configuration


Related Articles

  • Pushing Features to Execution Tools

  • Configuring Project Export Settings

  • What Is a Feature Bundle?



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article