Incoming content webhook
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
Ready-made Workflow
Turn incoming webhook content into a WordPress.com draft page. Connect WordPress.com and choose a Site. Send JSON containing title and content to the webhook URL, then activate the Workflow. The page remains a draft for review in WordPress; this template does not publish it. Use a backend sender and protect the webhook URL with source authentication. Only new requests after activation are processed. Repeated requests and manual reruns create additional pages rather than updating an existing page. Sample values are fictional.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
Run the Create a draft page action in WordPress.com.
Before activation
Send JSON submissions from your existing backend to the private webhook URL created in your Draft. No Webhook account is needed.
Connect your own WordPress.com account and review the provider settings used by this Workflow.
Webhook · WordPress.com
Upload media from incoming webhook URLs to the WordPress.com Media Library. Connect WordPress.com, choose a Site, and send JSON containing a media_urls array of publicly accessible image URLs to the webhook URL. WordPress downloads the files; private links requiring a separate login are not supported by this template. Protect the webhook URL with source authentication before activation. WordPress site permissions, supported file types and storage limits apply. Media URL accessibility is controlled by WordPress. Repeated requests or manual reruns can upload duplicate files. The example uses an official public WordPress image.
Webhook · WordPress.com
Turn incoming webhook content into a WordPress.com draft post. Connect WordPress.com and choose a Site. Send a JSON object containing title and content to the webhook URL, then activate the Workflow. The post stays a draft for review in WordPress; this template never publishes it. Use a backend sender and protect the webhook URL with source authentication. Only new requests after activation are processed. Each request or manual rerun creates another draft; this is not an upsert. Sample values are fictional.
Questions
No. FastHook creates a disconnected Draft. Connect your own WordPress.com accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.