Aidelly Docs
Integrations

n8n

Call the Aidelly API from n8n using the HTTP Request node.

Connect Aidelly to n8n using the HTTP Request node. Works with self-hosted and n8n Cloud.

Prerequisites

  • An active Aidelly paid plan
  • An API key from Settings → API Keys
  • An n8n instance (self-hosted or cloud)

Setup steps

1. Create a new workflow

Add your trigger node (Webhook, Schedule, Airtable, etc.).

2. Add an HTTP Request node

Search for HTTP Request and add it after your trigger.

3. Configure the node

SettingValue
MethodPOST
URLhttps://app.aidelly.ai/api/public/v1/posts
AuthenticationGeneric Credential Type → Header Auth
Header Auth NameAuthorization
Header Auth ValueBearer YOUR_API_KEY
Send BodyOn
Body Content TypeJSON

4. Add required headers

In Headers, add:

Content-Type: application/json
Idempotency-Key: n8n-{{ $workflow.id }}-{{ $runIndex }}
x-aidelly-workspace-id: YOUR_WORKSPACE_ID

5. Set the JSON body

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

Replace {{ $json.content }} with the expression for your content field.

Storing credentials securely

Use n8n Credentials to store your API key:

  1. Go to Credentials → Add Credential → Header Auth
  2. Name: Aidelly API
  3. Name: Authorization, Value: Bearer YOUR_API_KEY
  4. Select this credential in the HTTP Request node

Example: Schedule trigger → post to social

Cron trigger (daily at 9am)
  → Airtable node (fetch today's scheduled post)
  → HTTP Request node (POST to Aidelly /posts)
  → Airtable node (mark as published)

Error handling

Add an Error Trigger node or use the HTTP Request node's Continue on Fail option. Aidelly returns standard HTTP status codes:

  • 200 — post created/published
  • 400 — validation error in your JSON body
  • 401 — invalid or expired API key
  • 429 — rate limited; retry after the Retry-After header value
  • 5xx — transient server error; retry with the same Idempotency-Key