publish to webhook

Send finished articles to your own apps

Connect a public HTTPS address you control—Zapier, Make, or a custom app—then WritingTools delivers each finished article automatically when you publish. Nothing is scheduled.

How to connect

  1. Name the connection and paste a public https URL (not localhost).
  2. Copy or regenerate the secret so only WritingTools can deliver to you.
  3. Send a test to confirm your app receives the article.
  4. Save the webhook, then publish from the editor whenever an article is ready.

Good to know

  • Choose signed deliveries (recommended) or a simple bearer secret.
  • Test deliveries are marked as tests so your app can ignore them.
Open connectionsOpen the editorSee Premium

Other destinations: WordPress, Ghost, Webflow, Wix, Blogger, API.

Your endpoint, signed, on the public internet

Send every finished article to Zapier, Make, or your own app automatically. WritingTools delivers the article to a public HTTPS address you control—ideal when the destination is not WordPress, Ghost, Webflow, Wix, or Blogger.

Use a public https address. Localhost and private networks are blocked. A tunnel with a public hostname works if the app runs on your desk.

Name it, copy the secret, send a test

  1. 1

    Name the connection

    The name is required. The URL is a poor label once you have two endpoints. Put the name you want to see in the editor’s Publish menu.

  2. 2

    Choose how the secret is sent

    Signature mode sends X-WritingTools-Signature as the hex HMAC-SHA256 of the raw body, using the secret. Bearer mode sends Authorization: Bearer and the secret. Copy the secret when it is shown. You can regenerate it later from Edit, and then you must update the receiver.

  3. 3

    Read the test result

    Send a test before you trust the connection. The result includes the HTTP status, the duration, and the response body. A non-2xx response is shown. It does not throw away the form. Test payloads set test to true. A real article from the editor sets test to false and uses the draft or published status you picked.

What to verify on your side

  • Check the signature or the bearer token against the raw body, not a re-serialized object. Key order changes will break HMAC if you rebuild the JSON before verifying.
  • Treat test: true as a ping. Do not create a public article from a test payload.
  • Store the title, the HTML or markdown body, and the status your handler understands. The editor does not call your endpoint twice to mean “update.”
  • Rotate the secret from the connection card if it was copied into a log. Update the verifier in the same change.
  • Premium is required to save the webhook. The test button is how you confirm the URL before you depend on it.

A small receiver that is safe to leave running

Start with the test payload. Log the headers and the raw body once, confirm the signature or the bearer token, and return a 2xx with a short plain body so the test panel can show it. Do not create a public record when test is true. When a real article arrives, test is false and the status is the draft or published choice from the editor. Your handler decides whether “published” means visible on your site or “ready for a person to approve.” WritingTools will not call back to ask.

Timeouts and redirects are your problem to keep short. The test panel reports how long the request took. A receiver that waits on a slow third party will look like a failure even when it eventually writes the row. Acknowledge quickly, then do the slow work after you have stored the body. Reject unexpected hosts in your own code as well. The SSRF check on our side blocks private addresses. It does not know which public URL you intended.

If the destination is actually WordPress, Ghost, Webflow, Wix, or Blogger, use that card. A webhook that reimplements one of those APIs is extra code you have to keep. The webhook is for the system that does not have a card. Rotate the secret when it has been in a ticket or a screenshot, and update the verifier in the same change so the next test passes before you publish an article.

Other ways to publish, besides Webhook

Use the destination that already hosts the article. Each setup is different.

All connectionsEditorWordPressGhost

Webhook publishing is part of Premium

You can read the steps on the free plan. Saving the connection and sending a draft or a live post from the editor uses the Premium plan on the pricing page. Exporting a file does not.

See Premium

Frequently Asked Questions

Yes. Edit the connection, regenerate the secret, and update Zapier, Make, or your app.