Guides

n8n

HTTP Request node recipes for posting, a Webhook node for events, and the MCP Client Tool for agents.

n8n needs nothing overads-specific: the HTTP Request node speaks the REST API, the Webhook node receives events, and the MCP Client Tool node gives an AI Agent the tools.

Credential#

Create one Header Auth credential and reuse it on every node: Name Authorization, Value Bearer sk_live_.... Keep the key out of node parameters so it is not exported with the workflow.

Create a scheduled post#

{
  "content": "{{ $json.copy }}",
  "connectionIds": ["3f1c1a2e-6b2a-4a0e-9a5f-0d5a7d0f2b11"],
  "scheduledAt": "{{ $json.publishAt }}"
}

The response lands in $json.data with $json.warnings beside it. Add an IF node on {{ $json.warnings.some(w => w.code === 'APPROVAL_REQUIRED') }} to notify a reviewer.

List today's scheduled posts#

Receive events#

• Add a Webhook node, method POST, and copy its production URL.
• Register it: POST https://api.overads.io/public/v1/webhooks with { "name": "n8n", "url": "<the URL>", "events": ["post.published", "post.failed"] }. Store the returned secret as an n8n credential.
• In the Webhook node set Response to Immediately and Raw Body on, so the signature can be checked over the exact bytes.
• Add a Crypto node: Action Hmac, Type SHA256, Value {{ $json.body }} (the raw body), Secret from the credential, Encoding hex. Compare its output to {{ $json.headers['x-overads-signature'] }} in an IF node and stop on mismatch.

Give an agent the tools#

Attach it to an AI Agent node. The agent sees every tool the key is scoped for; see MCP tools.