Connect your automation flow to another tool
A connection allows your automation flows to perform actions or make changes in another third-party application with which Atlassian has a supported integration. Read more about connections.
For example, you could set up a flow that triggers when a work item is created, which creates a corresponding feature flag in LaunchDarkly.
Creating a connection
To connect your automation flow to another tool:
Go to Automation and select Create flow.
Select a trigger for your flow.
Select an action that interacts with another tool. This will prompt you to connect the application with Automation.
Follow the steps provided. These will vary depending on which application you are connecting to, but will usually involve providing the required credentials or API keys. Read more about the applications that can be used in connections.
Connections can be added when a flow is being edited so when creating your flow, be mindful of who you give editing permissions to.
Reusing established connections
Once a connection is established, it can be reused within the same automation flow. Connections can’t be reused in other flows, so if a new flow is created a new connection must be set up too.
Using an existing connection: When editing an automation flow, you can select from a list of that flow’s existing connections, simplifying the process and ensuring consistency.
Creating another connection: If you want to connect to a new service or use different credentials for the same application, you’ll need to create a new connection specifically for that purpose, for example two different instances of Workato.
Things to remember
Connections perform actions on your behalf: Connections perform actions as the person who set up the connection. For example, if an automation flow creates a feature flag in LaunchDarkly, the person who set up the connection will be listed as the person who created the flag. For triggers, permissions will be inherited from the person who sets up the flow.
Flow permissions: Because actions will always be performed by the person who set up the connection, you should be mindful of who you provide editing permissions to when publishing your automation flow. If someone else edits the flow after a connection is set up, they can reuse the connection and any changes will still be made by the person who set up the connection.
Best practices
Use clear, descriptive names for any connections you create, as this will help you to easily identify the connections in your automation flows.
Regularly review your connections and check the application credentials to ensure the connection is valid and secure.
Monitor usage of your connections to optimize performance and keep track of how they are used in automation flows.
Test thoroughly before deploying automation flows that use connections to ensure they work as expected.
Was this helpful?