Webhook triggers allow you to run workflows from external applications, scripts, or automation platforms. Send an HTTP POST request to your workflow's unique URL to trigger execution.
Setting Up a Webhook
- Add a Webhook trigger block to your workflow
- Click the block to open Webhook configuration
- Copy the Webhook URL to use in your integrations
Each workflow has a unique webhook URL that remains constant. Use this URL in any application that can send HTTP requests.
Webhook Configuration
Accept Data
Enable Accept data to receive GeoJSON or CSV data in POST requests. When enabled, the incoming data becomes available as input to subsequent workflow blocks.
When disabled, the webhook simply triggers the workflow without passing any data payload.
Webhook URL
The unique URL for triggering your workflow:
https://gis-api.atlas.co/workflows/{workflow-id}/webhooks/{webhook-token}
Click the copy button to copy the full URL to your clipboard.
Triggering the Webhook
Send a simple POST request to trigger the workflow. No data payload is required for basic triggers.
cURL
curl -X POST "https://gis-api.atlas.co/workflows/{workflow-id}/webhooks/{webhook-token}"
Python
import requests
url = "https://gis-api.atlas.co/workflows/{workflow-id}/webhooks/{webhook-token}" response = requests.post(url)
JavaScript
fetch(
'https://gis-api.atlas.co/workflows/{workflow-id}/webhooks/{webhook-token}',
{
method: 'POST'
}
)
Go
http.Post("https://gis-api.atlas.co/workflows/{workflow-id}/webhooks/{webhook-token}", "", nil)
Sending Data with Webhooks
When Accept data is enabled, include GeoJSON or CSV data in the request body:
GeoJSON Example
curl -X POST "https://gis-api.atlas.co/workflows/{workflow-id}/webhooks/{webhook-token}" \
-H "Content-Type: application/json" \
-d '{"type": "FeatureCollection", "features": [...]}'
CSV Example
curl -X POST "https://gis-api.atlas.co/workflows/{workflow-id}/webhooks/{webhook-token}" \
-H "Content-Type: text/csv" \
-d 'id,name,lat,lng
1,Location A,40.7128,-74.0060'
Testing Webhooks
Use the Try it out tab in the webhook configuration to test your webhook directly from Atlas. This sends a test request and shows the response.
Use Cases
| Scenario | Description |
|---|---|
| Scheduled tasks | Use external schedulers (cron, cloud functions) to run workflows |
| IoT devices | Process sensor data as it arrives |
| Third-party integrations | Connect Zapier, Make, or other automation platforms |
| CI/CD pipelines | Update map data as part of deployment workflows |
Monitoring Webhook Executions
Webhook-triggered runs appear in the workflow History with Triggered by: Webhook. Monitor this to verify webhooks are firing correctly and track any failures.