Integrations

Agents connects with your existing tools to automate workflows across your tech stack. This section covers setup, configuration, and best practices for each integration.

Available Integrations

CRM Systems

Communication

How Integrations Work

Authentication

Integrations use OAuth to securely connect to external services:

1. User-level tokens - Each user authenticates with their own credentials
2. Organization-level tokens - Shared credentials for the workspace
3. Automatic refresh - Tokens are refreshed automatically when they expire

Connection Flow

[User] ──▶ [Connect Integration] ──▶ [OAuth Flow] ──▶ [Store Token]

1. Navigate to Workspace Settings → Integrations
2. Click Connect for the desired service
3. Complete the OAuth authorization
4. Integration is ready to use

Permissions

Each integration requests specific permissions (scopes) needed for its functionality:

• Read access - Fetch data from the external service
• Write access - Create and update records
• Channel/object access - Post to specific channels or access specific objects

Integration Setup Checklist

Before using integrations in workflows:

• Admin access - Ensure you have permission to connect integrations
• Service account - Consider using a dedicated service account for workflows
• Required scopes - Verify your connection has necessary permissions
• Test connection - Verify the integration works before releasing workflows

Using Integrations in Workflows

Action Nodes

Integrations are used through action nodes:

[Workflow] ──▶ [Slack Post] ──▶ Sends message to Slack
[Workflow] ──▶ [HubSpot Task] ──▶ Creates task in HubSpot
[Workflow] ──▶ [CRM Update] ──▶ Updates Salesforce opportunity

Required Data

Each integration node requires specific data:

Error Handling

Integration nodes can fail for various reasons:

• Authentication expired - Token needs refresh
• Permission denied - User lacks required access
• Rate limits - Too many API calls
• Invalid data - Required fields missing or malformed

Always connect error outputs to handle these cases gracefully.

Best Practices

1. Use Dedicated Service Accounts

For production workflows, use a dedicated service account rather than personal credentials:

• Workflows continue working if team members leave
• Easier to manage permissions
• Better audit trail

2. Test Before Releasing

Always test integrations with MANUAL trigger before releasing:

1. Set trigger to MANUAL
2. Run with test data
3. Verify external system received correct data
4. Switch to production trigger

3. Handle Rate Limits

External APIs have rate limits. For high-volume workflows:

• Add delays between operations
• Use batch processing where available
• Monitor for rate limit errors

4. Verify Permissions

Ensure the connected account has access to:

• Target Slack channels
• CRM objects (deals, contacts, tasks)
• Required fields and custom fields

5. Monitor Integration Health

Regularly check:

• Integration connection status
• Error rates in execution logs
• Token expiration warnings

Troubleshooting

Common Issues

Reconnecting Integrations

If an integration stops working:

1. Go to Workspace Settings → Integrations
2. Click Disconnect for the problematic integration
3. Click Connect to re-authenticate
4. Test a workflow to verify connection

Data Security

Token Storage

• Tokens are encrypted at rest
• Access tokens are refreshed automatically
• Refresh tokens are securely stored

Data in Transit

• All API calls use HTTPS
• Sensitive data is never logged
• Minimal data is stored (only what's needed for operation)

Compliance

Agents integrations are designed to work within your organization's security policies:

• No data is shared between organizations
• Integrations respect CRM field-level security
• Audit logs track all integration activities

Next Steps

• HubSpot - Set up HubSpot integration
• Salesforce - Set up Salesforce integration
• Slack - Set up Slack integration