Custom Webhook

Publishing via Webhook

Averi's Custom Webhook integration sends your published content as a POST request to any URL you choose. If a service accepts webhooks — Zapier, Make, n8n, or your own backend — you can publish to it from Averi.

What You'll Need

Before you start, grab two things:

1. A Webhook URL — any endpoint that accepts POST requests with a JSON body. Where you get this depends on what you're connecting to:
   • Zapier — Create a Zap with a "Webhooks by Zapier" trigger and copy the webhook URL.
   • Make.com — Add a "Webhooks" module and copy the URL.
   • n8n — Add a Webhook node and copy the production URL.
   • Custom endpoint — Any URL that accepts POST requests (e.g. https://api.yourdomain.com/webhooks/publish).
2. An Authorization Token (optional) — only needed if your endpoint is protected. Averi will send it as a standard Authorization: Bearer <token> header on every request.

How to Connect

Publishing Content

Once configured, you push content to your webhook by clicking Send to CMS in the editor or Publish from the finalized column.

Averi fires a POST request to your webhook URL with a JSON body containing your content. From there, whatever's on the receiving end — Zapier, Make, or your own service — takes over.

Example Request

Here's exactly what your endpoint will receive. This matches the Webhook Payload Format preview shown inside the configuration dialog, with all optional fields turned on:

POST https://your-endpoint.com/webhook
Content-Type: application/json
Authorization: Bearer <token>

{
  "title": "Raw Text Content Title",
  "content": "<H2>Subheading...</H2><p>Inspiring copy...</p>",
  "updated": "2026-01-09",
  "published": "2026-01-09",
  "featuredImage": "https://res.cloudinary.com/dbkv1xnv9/image/upload/example.jpg",
  "slug": "raw-text-content-title",
  "meta_description": "SEO optimized description...",
  "read_time": "5"
}

And here are the types for each field, so you can wire up your receiving flow:

{
  "title": "string",
  "content": "string (HTML)",
  "updated": "string (YYYY-MM-DD)",
  "published": "string (YYYY-MM-DD)",
  "featuredImage": "string (URL)",
  "slug": "string",
  "meta_description": "string",
  "read_time": "string"
}

A few things worth knowing:

• All values are strings, including read_time — so expect "5", not 5.
• content is HTML, not plain text or Markdown (with formatting like headings, bold text, and images preserved).
• Optional fields are only included if you toggled them on during setup, so design your receiving flow to handle them being absent.
• The Authorization header is only included if you set an Authorization Token. Otherwise the only header is Content-Type: application/json.

Tips

• Test before you rely on it. Use Send Test after saving to confirm your endpoint is reachable and the payload looks right on the receiving end.
• Zapier and Make are the easy path. If you don't have a custom endpoint, tools like Zapier or Make give you a webhook URL in a few clicks, then let you route the content anywhere — Notion, Airtable, Slack, a CMS, you name it.
• You can reconfigure anytime. Head back to Integrations to change the URL, update the token, or toggle payload fields.
• Don't see your CMS listed? We're adding more integrations by request. Email us at [email protected] or click Send Suggestion on the Integrations page.

Troubleshooting

If you're running into issues connecting or your content isn't publishing as expected, check the following:

• Webhook not receiving data — Confirm the URL is correct and that your endpoint accepts POST requests with a JSON body.
• Authentication errors — If your endpoint requires an authorization token, make sure you've entered it in the configuration. Averi sends it as a Bearer token in the Authorization header.
• Featured image missing — The Include featuredImage option must be toggled on in your configuration, and your content needs at least one image for Averi to pull from.
• Slug or meta description not showing — Make sure the corresponding field is toggled on in your configuration, and that those fields are filled in on the content itself.
• Timeout errors — Averi waits up to 15 seconds for your endpoint to respond. If your endpoint takes longer, consider using an intermediary like Zapier or Make to queue the request.
• Still stuck? — Book a technical help call with our team and we'll walk through it together.

Need Help?

Reach out to us at [email protected] - you'll always get a human to talk through solutions with.