Automation における接続とは

A connection in Automation is a link that is created between your flow and a third-party product or application with which Atlassian has a supported integration. Find out which applications can be used in connections.

Connections allow your flows to perform actions or interact with other applications such as sending or retrieving data, or triggering events.

For example, you could configure a flow that:

• 作業項目が作成されたときにトリガーして、LaunchDarkly で対応する機能フラグを作成します。

• triggers when a step is created in Compass, which creates a corresponding page in Confluence.

接続を使用する

接続の使用には、次のようなメリットがあります。

• 複雑なワークフローや複数のアプリケーションでの繰り返しタスクの自動化によって効率を高め、時間を節約し、手作業を削減します。

• シームレスな統合によってアプリケーション間のコラボレーションを改善し、データの一貫性を確保するのに役立ちます。

Each connection is typically associated with a specific product or application. Once a connection is established, you can use it within your automation flow to perform various actions.

When editing a flow, add a connection by selecting an trigger or action that interacts with another application, for example the action Retrieve worker details from Workday. If there’s no existing connection, you’ll follow the process to connect the application to Atlassian Automation by providing the required credentials or API keys. Read how to connect your automation flow to another application.

実行中の接続

アクションの場合、他の製品で行われた変更は、連携をセットアップしたユーザーが行ったものと見なされます。次に例を示します。

• if a flow 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 flow in Confluence creates a work item in Jira, the person who set up the connection in Confluence will be listed as the work item creator.

Even if someone else edits the flow after a connection is set up, those changes will still be made by the person who originally set up the connection.

トリガー内の接続

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

注意事項

• 認証とセキュリティ: OAuth や API トークンなどの安全な認証方法を使用して、機密データを保護してください。

• 接続の制限: 外部サービスまたはアプリによって課せられる、接続数または API リクエスト数の制限に注意してください。

• Service availability: The availability and performance of your automation flows depend on the external application's uptime and reliability.