Setting up a JIRA connection within Automate365 Automations opens up powerful possibilities for automating helpdesk requests for new workspaces. This integration allows you to fully automate the creation of Microsoft 365 workspaces directly from a JIRA request, for issues created in the scope of projects, based on that request's settings.
Set up a JIRA connection
Go to the BindTuning App.
Navigate to Automate365 > Connections.
Click the "Create connection +" button, and select "JIRA".
A pop-up will open to configure the JIRA connection.
JIRA authentication options
Below, you'll find an explanation of the different JIRA authentication options and the required parameters for each.
API token
Uses a unique, secret key generated in Jira to securely authenticate and authorize Automate365's requests. The API Token JIRA connection is useful for service accounts or environments that don't support interactive logins.
Parameter | Description |
Domain URL | |
Email address associated with your Jira account | |
API Token* | Token generated from your Atlassian account settings |
* Read more on how to obtain your API token from Jira.
About connection failure
API tokens are not automatically validated or refreshed. You must be aware of the token's expiration date in your environment. To maintain connectivity, you need to manually edit the connection and provide a new API token before the token expires. If you miss the expiration date, the system will notify you once it detects the key is no longer valid.
OAuth 2.0
Provides a secure, token-based authorization method allowing Automate365 to access Jira on a user's behalf without storing their credentials.
Just click "OAuth 2.0" > "Continue" and sign in with your Jira credentials. This is the recommended option for most users working with Jira Cloud.
About authentication tokens' expiration and renewal
OAuth tokens typically expire after 90 days. Automate365 manages this by automatically refreshing tokens before they expire, ensuring continuous connectivity and eliminating the need for manual intervention.
If the system cannot renew an OAuth token (maybe due to revoked permissions or changed credentials), you'll be notified immediately. This lets you fix the issue fast and keep your workflows running smoothly.
Once you've configured the connection, simply check your connections list to confirm its status is "Connected."
Note: For other types of connections, refer to the full list of connection types.