What are connections in Automation?

Connections allow your automation rules to operate across multiple products. By setting up a connection between your rule and another product, you can configure your rule so that an event in one product triggers something to happen in another.

For example:

• In Jira automation, you could set up a rule that triggers when an issue is created which creates a corresponding feature flag in LaunchDarkly

• You could set up a rule that triggers when a component is created in Compass, which creates a corresponding page in Confluence.

Actions that require connections

For actions, changes made in other products will be seen as being made by the person who set up the connection. For example:

• if a rule in Jira creates a flag in LaunchDarkly, the person who set up the connection will also be listed as the flag creator in LaunchDarkly.

• if a rule in Confluence creates an issue in Jira, the person who set up the connection in Confluence will be listed at the issue creator.

Triggers that require connections

For triggers, permissions will be inherited from the person who sets up the rule. For example, the Component created in Compass trigger will use the permissions of the person who sets up the connection - this means that the rule will only have access to the same components they do.

Learn more

To learn more about how to set up a connection, see Connect your automation rule to another tool.