Outbound Webhooks in Shape

Learn how outbound webhooks in Shape send data to external systems using triggers, drip campaigns, and bulk actions for seamless integration.

Outbound webhooks in Shape allow you to send data from Shape to external systems whenever an event occurs inside the platform. While webhooks are considered an advanced feature, anyone familiar with integrations will find them straightforward to configure. Webhooks can send data to tools like Zapier, spreadsheets, CRMs, or other third party platforms.

Creating a New Outbound Webhook

You can create a webhook from scratch or start with an existing example, depending on what you are trying to connect.

Give the webhook a clear, searchable title
Choose a POST or GET method
Enter the destination URL provided by the receiving platform
Select whether you are sending field data or files

Field data is used for information like names, emails, phone numbers, or loan details, while file payloads are used when sending documents from Shape.

Headers and Payload Type

Some platforms require headers to authenticate incoming data. These are typically API keys or authorization values provided by the receiving system.

Add required headers exactly as provided
Select a payload type, most commonly JSON or FORM
Confirm payload requirements with the destination platform if needed

Headers act as a security layer to ensure data is accepted and processed correctly.

Mapping Shape Data to External Systems

Data mapping controls which Shape fields are sent and how they are labeled when received by the external platform.

Select the Shape field you want to send, such as lead ID or first name
Enter the corresponding field name required by the destination system
Optionally include default values for static data

Default values are useful for fixed data points that never change, while dynamic fields pull live data from each record.

Sending Webhooks from Drip Campaigns

Webhooks can be added directly into drip campaign workflows to send data at specific points in an automation.

Add a webhook step to the campaign
Select the webhook you want to send
Position the step anywhere in the campaign timeline

This allows data to be sent on day one, day ten, or any point that aligns with your workflow.

Sending Webhooks with Triggers

Triggers are one of the most common ways to initiate outbound webhooks based on system activity.

Choose a trigger type such as a status change
Select the webhook as the action
Set the timing to immediate or delayed

This approach is commonly used to send data when a record reaches a specific status.

Sending Webhooks with Bulk Actions

Webhooks can also be initiated manually for multiple records at once using bulk actions.

Select individual records or an entire list view
Choose Bulk Actions
Select Initiate Webhook
Confirm the action

Confirm the action This method is useful for backfilling data or sending large groups of records to an external system.

Why This Matters

Outbound webhooks allow Shape to act as a central system while seamlessly sharing data with the rest of your tech stack. They give you complete control over when data is sent, what data is included, and how your systems stay in sync without manual effort.