Skip to main content

Disconnect

Removes a stored Airtable API key token from memory.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

  • Key Id - The key identifier returned from the Connect node that should be removed.

Output​

  • None

How It Works​

The Disconnect node removes a stored API key token from memory. When executed, the node:

  1. Retrieves the Key Id from the input
  2. Calls the removeToken function to delete the token from the global tokens map
  3. The token is permanently removed from memory and can no longer be used

Requirements​

  • A valid Key Id from a previous Connect node
  • The Key Id must exist in the tokens map

Error Handling​

The node will return specific errors in the following cases:

  • Empty or invalid Key Id
  • Key Id not found in the tokens map (though the current implementation doesn't check for this)

Usage Notes​

  • The Disconnect node should be used at the end of flows to clean up stored credentials
  • Once a Key Id is removed, it cannot be used by other Airtable nodes
  • The node doesn't communicate with Airtable's servers; it only removes the local token reference
  • It's good practice to use Disconnect nodes to prevent credential leaks
  • If your flow has multiple exit points, consider using a Disconnect node at each exit

Example​

To properly clean up after Airtable operations:

Inputs:

  • Key Id: (from Connect node)

The node will remove the stored API key from memory, ensuring that the credential is not left in memory longer than necessary.

Security Considerations​

  • Always use Disconnect nodes to remove stored credentials when they are no longer needed
  • Tokens are only stored in memory and are automatically removed when the flow stops
  • For maximum security, use Disconnect nodes immediately after the last Airtable operation in your flow
  • Never hardcode API keys in your flows; always use the Connect/Disconnect pattern with credentials