http trigger is the most common trigger type. It creates a REST endpoint that executes your flow when called.
Configuration
Config Fields
HTTP Methods
Path Patterns
Paths must start with/ and can include path parameters:
Path Parameters
Path parameters are accessible in the request context:Endpoint URL
Your flow’s endpoint URL is constructed from your project’s subdomain and the path:- Project slug:
acme-api - Path:
/payments - Full URL:
https://acme-api.dualship.run/payments
Content Types
HTTP triggers support these content types:Runtime Context
When an HTTP request triggers your flow, the context includes:Context References
Examples
GET Endpoint
Retrieve a user by ID:POST Endpoint
Create a new resource:PUT Endpoint
Replace a resource:DELETE Endpoint
Remove a resource:With Query Parameters
List resources with filtering:With Authentication
Validate authorization header:Request Validation
Use the request node to validate incoming data:File Uploads
Accept file uploads viamultipart/form-data requests. Uploaded files are available in request.files.
File Object Structure
Each uploaded file contains:File References
File Upload Example
Accept and validate a file upload:Multiple Files with Form Data
Handle multiple files along with form fields:CORS
Configure CORS in your project settings to allow cross-origin requests:Rate Limiting
Enable rate limiting in project settings to protect your endpoints:Common Patterns
REST API
Create a full REST API for a resource:Webhook Receiver
Accept webhooks from external services:API Gateway
Proxy requests to backend services:Plan Availability
HTTP triggers are available on all plans including Free.Related
- Request Node - Validate incoming data
- Validation Rules - Complete validation rule reference
- Response Node - Send HTTP responses
- Abort Node - Return error responses
- Project Settings - Configure CORS and rate limiting