Tailflow
Skip to article
Browse documentation

Manage and troubleshoot

Connections, settings, and usage

Manage shared service access and understand action credits.

Connections belong to your account

Open Settings → Connections to find, connect, and manage services. Select the appropriate connection on each action. A single connection can be shared across several flows.

Follow the current dialog for Slack, X, or Anthropic. If a service is marked unavailable, creating a flow does not configure it. Email requires no connection.

Connections Settings and Action Selection
Settings · Connections
Slack · Team workspaceConnected
X · Alerts accountConnected
Connect
Slack
Example. Open Settings → Connections, then choose that connection in the action inspector.Changes stay in this example. Nothing is saved or sent.

Disconnect with the affected flows in mind

Open the connection detail and review the flows using it before disconnecting. Disconnecting removes access for all of them; it does not remove their actions or replace their credentials.

Reconnect the service or choose another valid connection in affected actions, then test and review the flow status. A saved connection is not a guarantee that permissions remain valid forever.

Connection Details and Affected Flows
Slack · Team workspace
StatusConnected
Used byLarge USDC transfers
Used byTreasury alerts
Disconnect
Slack · affected action
Reconnect the service or select another connected workspace.
Example. A shared connection can be used by several flows. Choose a replacement in each affected action after disconnecting.Changes stay in this example. Nothing is saved or sent.

Profile and usage

Settings includes Profile for account details and Usage for consumption. Review Usage alongside Activity when investigating which flows are doing work.

Credits are charged for completed actions, not simply for having a flow. Each matching path contributes its completed actions: two matching paths can consume twice as much as one. Failed or skipped actions do not consume action credits, but completed actions earlier in a failed run still do.

Agent uses 2 credits, Transform 2, and other available actions 1 each. Test runs use no Tailflow credits. Refer to the account’s current plan and pricing for allowances rather than assuming a displayed allowance stops a flow automatically.

Usage Summary and Credits by Flow
Settings · Usage
PeriodSeptember 2026
Credits used120
Runs100
Agent calls0
Usage by flow
Large USDC transfers · 80 runs80 credits
Formatted alerts · 20 runs40 credits
Example. Select a period in Usage and compare the per-flow totals with Activity. These are example totals, not a plan allowance.Changes stay in this example. Nothing is saved or sent.