# Workflows

## Trigger Workflow

 - [POST /v1/workflows/{workflow_id}/trigger](https://developers.withlantern.com/openapi/workflows/trigger_workflow_v1_workflows__workflow_id__trigger_post.md): Triggers enrichment and routing workflows from external systems.

## Overview
The Workflow Trigger API provides a generic interface for initiating enrichment and routing
workflows from various external systems like Eloqua, Customer Data Platforms (CDP), Data Lakes,
and other marketing automation platforms.

## Authentication
Requires either an API key or OAuth2 bearer token in the Authorization header.

## Rate Limits
Designed to support bursty event traffic, capable of handling hundreds of requests per minute.

## Request Body
- record_data: Generic record payload containing fields for Lead, Contact, Opportunity, or other custom objects
- source_system: Optional source system identifier (e.g., 'eloqua', 'cdp', 'data_lake')
- enrichment_preferences: Optional enrichment preferences and configuration

## Response Fields
- success: Boolean indicating request success
- status: Workflow status (triggered, queued, failed)
- request_id: Unique request ID for tracking
- workflow_id: ID of the triggered workflow
- processing_time_ms: Processing time in milliseconds
- enrichment_job_id: ID of enrichment job created (if applicable)
- credits_consumed: Number of credits used
- credits_remaining: Credits remaining in account
- cached: Whether result was from cache

## Features
- Generic Payload: Accepts any record type (Lead, Contact, Opportunity, custom objects)
- Audit Logging: All requests and responses are logged for compliance
- Retry Logic: Automatic retries on failure with exponential backoff
- High Throughput: Optimized for bursty event traffic
- Credit Tracking: Transparent credit consumption tracking

## Credit Usage
Workflow triggers consume credits based on complexity:
- Basic Trigger: 1 credit per record
- With Enrichment: +2 credits for enrichment processing
- With Routing: +1 credit for routing logic