Enginy doesn’t have a dedicated n8n node yet — one is planned. Until then, n8n’s built-in HTTP Request
and Webhook nodes cover the full integration: call any Enginy API endpoint from a workflow, and start
workflows from Enginy events.
What you need
- An Enginy API key from the API Dashboard (sent as the
x-api-keyheader). - Any n8n setup — cloud or self-hosted. Both nodes are core nodes, available on every plan.
Call the Enginy API from a workflow
1
Create a Header Auth credential
Add an HTTP Request node and under Authentication choose Generic Credential Type →
Header Auth. Create a credential with Name
x-api-key and your API key as the
Value — you configure it once and reuse it in every Enginy request.2
Configure the request
Set the URL to the endpoint you need, e.g.
https://openapi.enginy.ai/v1/contacts, pick the
method, and add a JSON body for writes. Browse the
API reference for endpoints and payloads.3
Or import a cURL command
The HTTP Request node has an Import cURL button — paste any example request from these
docs and n8n fills in the node configuration for you:
Start workflows from Enginy events
Enginy webhooks can push campaign events (replies, accepted connection requests, and more) into n8n.1
Add a Webhook node
Start your workflow with n8n’s Webhook node using the POST method, and copy its URL (use the test
URL while building, the production URL once activated).
2
Subscribe Enginy to that URL
In the API Dashboard (or via the webhooks
API), create a webhook subscription with the node’s URL and the events you
care about — for example
MESSAGE_REPLIED.3
Send a test event
Use the webhook test endpoint from the webhooks guide to send a sample
payload, then build the rest of the workflow from the captured data.
Next steps
Webhooks guide
Event types, payloads, and how to test subscriptions
API Reference
All endpoints you can call from your workflows