Prepare a product announcement
- Start with
- A new product is ready in your shop.
- In Wahlu
- Import its approved image and create a draft from the product details.
- Ready for
- A product post ready for content review and a publishing-readiness check.
Zapier + Wahlu
Use Webhooks by Zapier to call Wahlu’s REST API. Bring product updates, articles and approved briefs into a social workflow with a clear review point.
Instagram · Facebook · TikTok · YouTube · LinkedIn personal profiles · Threads · X · Bluesky · Telegram · Discord · Tumblr · Pinterest
01 Receive your source content
02 Import and check the media
03 Create a post draft
04 Check publishing readiness
05 Hold the schedule for reviewBuilt with Webhooks by Zapier → Custom Request. This guide uses the REST API; no native Wahlu marketplace app is required.
Example workflows to adapt to your own source data and review process.
Start with one draft and verify the returned result before adding the rest of your workflow.
In Wahlu, open Settings → API Keys. Create a key with the scopes your workflow needs and restrict it to the relevant brands. Save the secret in your automation platform’s credential store.
GET https://api.wahlu.com/v1/context
Authorization: Bearer <your stored API key>The context response lists accessible brands and useful resource links. Use a returned brand ID in the next request. Keep keys out of shared examples and source control.
Choose your trigger, then add a Webhooks by Zapier Custom Request action. Use POST, include the headers below and map the JSON fields from your trigger.
POST https://api.wahlu.com/v1/brands/:brand_id/content-items
Authorization: Bearer <your stored API key>
Content-Type: application/json
Idempotency-Key: zap-draft-{{product_id}}
{
"name": "Launch announcement",
"copy_mode": "single",
"single_copy": {
"caption": "{{product_name}}",
"hashtags": []
}
}Replace :brand_id and map the placeholder values. This example creates a text draft; add the required media and platform settings before scheduling. Use a stable key for each logical draft and reuse it when retrying the same request.
For posts with media, import it and read its readiness before creating the attached draft. Run preflight using your chosen accounts, a future time and pending_review. Follow the returned blockers and next actions.
A pending-review schedule is held: no execution, job, or provider request. The complete recipe shows how to carry forward IDs, use separate idempotency keys and confirm the held result.
Derive the idempotency key from a stable source event or row ID. Use a different key for the schedule. A network retry should not create duplicate content.
Check the API response at each step. If media or a publishing target is not ready, surface its guidance. Keep publication authority separate from content preparation.
Account and format requirements vary. Read capabilities and targets, and use the current privacy choices returned for a selected TikTok account.
Grant only the brands and operations your scenario uses. The authentication reference lists the scopes needed for media, drafts, preflight and schedules.
A complete example from account discovery through media, draft, preflight and status.
Select the scopes and brand access your automation needs.
Check current request setup, field mapping and platform requirements.
Understand preparation, approval and publishing results.
Connect your accounts, create a scoped API key and test your first preparation workflow.