Skip to main content

Connect

Establishes a connection to the Calendly API using a Personal Access Token and returns a client ID for use in subsequent Calendly operations.

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.

Options​

  • Credentials - The Calendly API Token credential used to authenticate with the Calendly API. This should be a Personal Access Token generated from your Calendly account settings.

Output​

  • Client Id - A unique identifier for the established connection that must be passed to subsequent Calendly nodes to perform API operations.

How It Works​

The Connect node is the entry point for all Calendly automations in Robomotion. It authenticates your flow with the Calendly API and establishes a reusable connection.

When executed, the node:

  1. Retrieves your Calendly API token from the provided credentials
  2. Creates an authenticated HTTP client with the authorization header
  3. Validates the credentials by making a test request to the /users/me endpoint
  4. Returns a unique Client ID that references the authenticated connection
  5. This Client ID is then used by other Calendly nodes to make API calls

Requirements​

  • A Calendly account (Free, Standard, Teams, or Enterprise)
  • A Calendly Personal Access Token (generate from Account Settings > Integrations > API & Webhooks)
  • The API token must be stored as a credential in Robomotion's Vault

Creating a Calendly API Token​

  1. Log in to your Calendly account
  2. Navigate to Account Settings > Integrations
  3. Click on "API & Webhooks"
  4. Click "Generate New Token"
  5. Copy the token immediately (it won't be shown again)
  6. Store the token in Robomotion Vault as a "Calendly API Token" credential

Error Handling​

The node will return specific errors in the following cases:

ErrCredentials

  • The credentials parameter is missing or invalid
  • Solution: Ensure you've selected a valid Calendly API Token credential

ErrInvalidArg

  • The API token value is empty in the credential
  • Solution: Verify the credential contains a valid token value

ErrInternal

  • Network error connecting to Calendly API
  • Authentication failed (401 Unauthorized)
  • API returned an error status code
  • Solution: Check your API token validity and network connection

Usage Example​

Basic Connection Flow​

[Start] -> [Calendly Connect] -> [Get Me] -> [Disconnect] -> [End]

In this flow:

  1. Connect node establishes the API connection
  2. The returned Client ID flows to Get Me node
  3. Get Me retrieves user information
  4. Disconnect cleans up the connection

Usage Notes​

  • Always use Connect as the first node in your Calendly automation
  • The returned Client ID is stored in the message context and automatically flows to connected nodes
  • Each Connect creates a new authenticated session that persists for the flow duration
  • Alternative: Some Calendly nodes support direct credentials without using Connect (see individual node documentation)
  • The connection is stored in memory and automatically cleaned up when the flow ends

Best Practices​

  • Store your Calendly API token securely in Robomotion Vault
  • Never hardcode API tokens in your flows
  • Use a single Connect node at the beginning of your flow to avoid multiple authentication calls
  • Always pair Connect with Disconnect to properly release resources
  • Handle authentication errors gracefully to prevent flow failures
  • Test your API token validity before deploying production flows
  • Rotate API tokens periodically for security

Security Considerations​

  • Personal Access Tokens have full access to your Calendly account
  • Never share tokens or commit them to version control
  • Revoke tokens immediately if compromised
  • Use role-based access if working in team environments
  • Monitor API usage in Calendly's developer dashboard

Rate Limiting​

Calendly enforces API rate limits:

  • Standard accounts: 100 requests per minute
  • Enterprise accounts: Higher limits available

The Connect node makes one API call to validate credentials. Consider this when designing high-frequency automations.