Zapier

Connect Aidelly to 7,000+ apps via Zapier. Use Webhooks by Zapier to call the Aidelly REST API from any Zap.

Prerequisites

• An active Aidelly paid plan
• An API key from Settings → API Keys
• A paid Zapier plan (Webhooks by Zapier requires a paid plan)

Setup steps

1. Generate an Aidelly API key

In your Aidelly dashboard, go to Settings → API Keys and create a new key with posts:write scope.

2. Create a new Zap and set your trigger

Choose any trigger — Gmail, Notion, HubSpot, RSS, or whatever starts your workflow.

3. Add a Webhooks by Zapier action

Add an action step, search for Webhooks by Zapier, and choose POST.

4. Configure the Webhook action

5. Set the Data fields (JSON body)

In the Data section, map your Zapier fields to the Aidelly request:

{
  "brand_id": "YOUR_BRAND_ID",
  "content": "{{your_post_content}}",
  "platforms": ["instagram", "linkedin", "x"],
  "publish_now": true
}

To schedule instead of posting immediately:

{
  "brand_id": "YOUR_BRAND_ID",
  "content": "{{your_post_content}}",
  "platforms": ["linkedin"],
  "schedule_at": "{{schedule_time}}"
}

6. Test and activate

Run a test in Zapier. A 200 response with "success": true confirms the post was created. Activate the Zap.

Supported platforms

Pass any combination in the platforms array:

instagram · tiktok · youtube · x · linkedin · facebook · bluesky

Popular use cases

• HubSpot deal closes → announce on LinkedIn and X automatically
• New blog post → RSS/WordPress trigger → format with ChatGPT → post via Aidelly
• Notion content calendar → when a post moves to "Ready" → publish via Aidelly
• GitHub release / changelog → trigger a social post the moment something ships

Troubleshooting

Getting a 400 error? Check that your JSON body is valid and that brand_id and platforms are included.

Getting a 401 error? Verify the Authorization header value starts with Bearer (with a space).

Idempotency-Key required? All POST endpoints require an Idempotency-Key header. Use a stable key like zap-{{zap_id}}-{{timestamp}}.