Enable non Atlassian app triggers in automation
You can trigger automation flows from events that occur in applications outside the Atlassian ecosystem. To use a trigger for a non-Atlassian app in Automation, an organization admin must first connect the app through Teamwork Graph connectors in Atlassian Administration.
Before you begin
Make sure you have:
Organization admin permissions in Atlassian Administration
The non-Atlassian app you want to use as a trigger
Any required permissions or administrator access for that app
Review your organization’s data policies before connecting an app. Connector permissions follow the permissions in the connected app.
Connect the non-Atlassian app
Go to Atlassian Administration at https://admin.atlassian.com.
Select your organization.
Select Connectors from the navigation.
Select the site where you want to use the trigger.
Select Add connector.
Select the app you want to connect, then select Next.
Review what the connector can access and how Atlassian handles the data.
Follow the instructions to authorize and configure the connector, then select Connect.
Some apps require additional steps in the app’s administrator console. Complete those steps before returning to Atlassian Administration.
Connector setup can vary by app. Some connectors sync data into Teamwork Graph, while others retrieve data directly from the connected app. The available options and setup requirements depend on the app.
Use the trigger in Automation
Return to the Atlassian app where you want to create the automation flow.
Open Automation, then create or edit a flow.
Select Add trigger.
Search for and select the trigger for the app you connected.
Configure the trigger conditions and complete the rest of the flow.
Save and enable the flow.
If the trigger doesn’t appear, confirm that you connected the correct app to the correct site. Then refresh Automation and check again.
Important information
Each site can usually connect a non-Atlassian app to one workspace.
Connecting an app in Atlassian Administration doesn’t automatically give every person access to its data. People can only use data they’re permitted to access in the connected app.
Disconnecting or disabling a connector can stop flows that depend on its triggers.
Trigger availability for non-Atlassian apps depends on the apps and triggers currently supported by Automation. Supported examples include Google Drive, Salesforce, Microsoft Teams, Slack, and GitHub.
Get help if a trigger doesn’t run
Check that the connector is connected and healthy, the trigger is configured for the correct site or workspace, and the account used to authorize the connection still has access to the connected app. You can also review the automation audit log for errors.
Was this helpful?