Skip to main content
Flow uses this integration to run Atlan actions from automations with the team connection selected during setup. Admins choose which actions that team can use, and automation runs call only those allowed actions through the connection.

​
Prepare in Atlan

Use an Atlan tenant URL such as https://acme.atlan.com. Flow accepts HTTPS tenant URLs that end in .atlan.com, without a path, custom port, query, or fragment.In Atlan, open Admin, then API access. Select Generate new, then Generate API token. Give the token a name and assign at least one persona that permits search of the glossaries your team needs. Select Save and copy the token before you close the dialog. Personas control glossary access. The token can retain administrative API permissions outside this integration. See Atlan API token setup.If Atlan rejects the token, check its expiry and create a replacement if needed. If Atlan denies search or returns no expected terms, check the token personas and their glossary access. An empty search result can be valid.This connection supports automation actions. It does not sync Knowledge or Assets.To replace an expired or rejected token, reconnect with the same tenant URL. Create a separate connection to use another tenant. A rejected replacement token blocks automation use until reconnect succeeds.

​
Connect in Flow

1

Find the Atlan integration

  1. Open Integrations.
  2. Choose Add connection.
  3. In Add connection, search for Atlan.
  4. Select the Atlan card.
Open Flow
2

Connect

  1. Pick the team that will use the connection.
  2. Enter a connection name and continue to Atlan tenant URL.
  3. Enter your tenant URL and select Continue.
  4. Select Connect to open the credential form.
  5. Enter your Atlan API token and submit the form. Flow checks glossary-search access before it saves the connection.
  6. After connection completes, enable Automation for each team that needs it.

​
Permissions and scopes

This integration does not define provider scopes.

​
Supported actions