kitful.aiKitful
Integrations

Webhooks

Send finished articles from Kitful to another tool with a webhook.

Use Webhooks when you want Kitful to hand off finished articles to another system that does not have a built-in integration.

If someone else on your team handles the technical setup, you can share this page with them.

What you need before you start

  • a public https:// webhook URL
  • access to the tool or service that will receive the article
  • optional: a shared secret if your team wants signed requests

Connect Webhooks in Kitful

  1. Open your workspace in Kitful.
  2. Go to Integrations.
  3. Click Add on Webhook.
  4. Fill in:
    • Integration Name
    • Webhook URL
    • Secret (Optional)
  5. Click Save.

What Kitful sends

When Kitful sends an article to your webhook, it includes the main publishing details your receiving system usually needs, such as:

  • article title
  • slug
  • HTML content
  • excerpt
  • SEO title and description
  • featured image details
  • tags
  • publish date

If you add a secret during setup, Kitful also signs the request so your receiving system can verify it came from Kitful.

Publish an article manually

  1. Open the article in Kitful.
  2. Click Publish.
  3. Choose your webhook integration.
  4. Confirm the publish.

Use Webhooks with Autoblog

  1. Open Autoblog.
  2. Create a campaign or edit an existing one.
  3. Choose your webhook integration in Campaign Configuration.
  4. Save or launch the campaign.

Troubleshooting

Failed to create integration

  • Confirm the webhook URL is a valid https:// address.
  • Make sure the integration name is not already being used in the same workspace.

Webhook returns 401 or 403

  • Check the receiving service's authentication rules.
  • If you use a secret, confirm both sides are using the same value.

Webhook returns 404

  • Double-check the exact webhook path.
  • Make sure the receiving endpoint is live and publicly reachable.

Publishing fails with a non-2xx response

  • Check the receiving service logs.
  • Make sure the destination only returns success after it accepts the article.

On this page