Webhooks in Pictor allow external systems to receive real-time updates from your event workflow. Whenever a specific action occurs - such as completing a session, submitting a survey, or generating outputs - Pictor sends a structured message to a URL you define. This makes it possible to automate tasks, sync data with external tools, and extend the power of your Pictor events.

Purpose of Webhooks

The Webhook feature is designed to help event owners:

Automatically send session-related data to third-party systems
Include photos, videos, survey responses, and any extra custom fields
Trigger downstream actions (e.g. analytics tracking, notifications, etc.)
Improve integration between Pictor and external platforms such as Zapier, Make.com, CRMs, or custom APIs

Webhooks open the door for advanced workflows and real-time automation outside of Pictor.

Where Webhooks Are Used in the App

Webhooks exist as a stage within the Event Workflow Builder.

You can place a Webhook step anywhere in the workflow
Data is collected and sent at the exact moment the guest reaches that workflow stage
What gets sent depends on the position of the Webhook (e.g., placing it after Survey includes survey data)

This placement determines what information is available and included in the Webhook payload.

How Webhooks Work

1. Permissions & Licensing

All registered Users in Pictor automatically have the appropriate permissions to use Webhooks. However, when a Webhook is added as a Stage in the workflow, the user will see a message informing them that this event will become a Premium Event if it is not already.

2. Webhook URL

This is the destination where your data will be sent.

You can paste any URL provided by your integration platform, such as:

Zapier
Make.com
CRM endpoints
A custom server or API
Analytics tools

Pictor will send data to this URL every time the workflow reaches the Webhook stage.

3. Request Type (GET or POST)

Choose how Pictor should send the data:

GET

Sends data as URL parameters
Often used for simple or lightweight integrations

POST

Sends a structured JSON payload
Best for APIs, CRMs, and data-based integrations

4. Add Custom Headers (Optional)

Some APIs require additional header information. Custom headers allow you to include data such as:

Authorization tokens
API keys
Custom identification strings

You can add as many header rows as you need.

Example:
Authorization: Bearer 12345

5. Add Custom Values to Payload (Optional)

Custom Values allow you to append your own key–value pairs to the payload.

Use this for:

Campaign names
Event types
Internal tags
Notes or identifiers

These values appear in the payload exactly as you define them and are useful for downstream automation.

6. Notify on Webhook Failure (Optional)

If the external service returns an error - such as 404, 401, or 500 - Pictor can automatically notify you.

You will receive an email containing:

The status code returned
A short error description (if provided by the external service)
The name of the affected Webhook

This makes troubleshooting quick and straightforward.

Example Email:
“Webhook failed with status 500 – Internal Server Error.”

Pictor does not automatically retry failed Webhooks.

What Happens When the Webhook Runs

When the guest reaches the Webhook stage in the workflow:

Pictor gathers all available data (outputs, survey answers, toggled fields, custom values, etc.)
A JSON payload (POST) or URL parameter string (GET) is built
The request is sent to the Webhook URL
Pictor checks the response
- 2xx or 3xx = Success
- 4xx or 5xx = Failure
If failure notifications are enabled, Pictor emails you immediately

All of this happens automatically - no action is required from you.