Webhook Block

Send your workflow to other apps

The Webhook block sends text and media links to a receiving URL as JSON. An automation in n8n, Zapier, Make, or your own service can use that content to publish a post, prepare an ad, save a file, or notify your team.

Choose a visual destination

Click the destination at the top of the block to choose Instagram, TikTok, Meta Ads, LinkedIn, Slack, or another destination. Its icon makes the block easy to recognize on your canvas. Use the pencil to give it a custom name, such as Weekly LinkedIn campaign.

Choose Custom webhook for any other destination. Changing the icon keeps your URL and payload settings intact, and preserves a custom name.

The destination is a visual label. It does not connect an account or choose a URL. Your receiving automation handles account access and the final action.

Set up a receiver

1. Create a webhook trigger in your automation service.
2. Copy the receiving URL into Webhook URL on the block.
3. Use POST, or select PUT or PATCH if your endpoint expects it.
4. Connect your text, image, video, or 3D blocks to the matching handles on the left. Text is optional; you can send just media or fixed values.

Use the guide for your automation service:

• n8n: Webhook node setup. Select POST. Use the test URL while listening for a test event; switch to the production URL when you publish the workflow.
• Zapier: Webhooks and Catch Hook. Add Webhooks by Zapier, choose Catch Hook, and copy its URL.
• Make: Custom webhooks. Start with a Custom webhook and copy its URL.
• Custom endpoint: accept a JSON request using the method selected on the block and return an HTTP response.

Choose the payload

In Payload, select Add field. Give each field the name your receiving automation expects, then choose its value:

• Fixed value sends text that stays the same, such as a campaign name.
• From block uses content from a connected block. Choose the block, then the available content field, such as text or imageUrl.

For example, your automation could receive:

{
  "campaign": "Summer launch",
  "caption": "A new collection is here.",
  "imageUrl": "https://example.com/your-image.webp"
}

Field names come from your mapping; they are not imposed by the destination picker. Every destination uses the same JSON delivery format. Map the received fields to the next action in your automation.

Media is sent as a URL, not an attached file. From block follows the active media version. Private media links are signed for access, so have your receiving automation fetch or store the media promptly instead of treating the link as permanent.

Preview, send, and check delivery

1. Open Preview to inspect or copy the JSON.
2. Make sure your receiver is listening, then select Send webhook.
3. Open Delivery to see the latest response, HTTP status, and time.
4. Map the received fields in your automation, connect the destination account there, and enable the automation.

A successful delivery means the receiver accepted the request. Check the receiving automation to confirm its publishing, storage, or notification action also succeeded.

In Interface mode, the webhook result card can send manually or Send after each run. Configure the receiving URL and payload on the canvas.

If delivery fails, check the URL, request method, and response. Confirm that a test receiver is still listening, or that the production automation is enabled.