Configuration

Configuration Methods

Workstation offers two flexible ways to configure webhooks, each optimized for different use cases:

Visual Interface
Dynamic API

Permanent Configuration via Interface

Ideal for: Long-term integrations, production environments, multiple teamsConfigure your webhooks visually through the Workstation interface in just a few clicks and receive events automatically:

Intuitive interface: Configure everything visually without writing code
Centralized management: View and manage all your integrations in one place
Fixed headers: Configure authentication tokens and headers that will be sent automatically
Integrated testing: Test button allows you to validate your configuration before activating

How to Configure

Access settings

Access the app settings in Workstation

Navigate to Events

Access the “Events” tab

Enable Events

Enable Events in the app

Fill in the details

URL: Your endpoint that will receive notifications
Headers: Add custom headers

Test

Click “Test Request” to validate your configuration

Save

Save and start receiving notifications!

Dynamic Webhooks via API

Ideal for: Multi-tenant SaaS integrations, dynamic endpoints, temporary integrationsSend notifications to different endpoints with each call, without creating permanent subscriptions:

Total flexibility: Each call can notify a different endpoint
Zero prior configuration: Start using immediately without setup
Dynamic headers: Pass different credentials for each client/context
Native multi-tenant: Perfect for SaaS with multiple clients
Temporary webhooks: Useful for tests, demos, or one-time integrations

How to Use

Simply add webhook_url to your API request body and use x-tela-forward-* headers for authentication:

curl -X POST https://api.tela.com/v1/tasks \
  -H "Content-Type: application/json" \
  -H "x-tela-forward-authorization: Bearer client-123-token" \
  -H "x-tela-forward-custom-id: request-xyz" \
  -d '{
    "webhook_url": "https://example.com/webhook",
    "prompt": "Analyze this document",
    "files": []
  }'

When the task completes, the webhook will be sent to https://example.com/webhook with:

Header authorization: Bearer client-123-token
Header custom-id: request-xyz

Next Steps

Authentication

Learn about custom headers

Payload Reference

Understand the webhook payload

Get Started

Guides

Apps

Resources

Configuration

Configuration Methods

Permanent Configuration via Interface

How to Configure

Dynamic Webhooks via API

How to Use

Next Steps

Authentication

Payload Reference

Get Started

Guides

Apps

Resources

​Configuration Methods

​Permanent Configuration via Interface

​How to Configure

​Dynamic Webhooks via API

​How to Use

​Next Steps

Authentication

Payload Reference

Configuration Methods

Permanent Configuration via Interface

How to Configure

Dynamic Webhooks via API

How to Use

Next Steps