n8n integration
Setup and troubleshooting
Use n8n’s outbound HTTP Request nodes with one Automentor key per monitored workflow. The setup works independently of n8n’s public API.
Verify the connection
- Generate a scoped key in Automentor and select it through Header Auth on the templates’ HTTP Request nodes.
- Put the registered workflow and integration IDs into the heartbeat and test configuration nodes.
- Start a test in Automentor, paste the challenge into the manual branch in n8n, and run that branch within ten minutes. Refresh the connection status after the request returns.
The template doesn’t import
Check the node versions and availability in your n8n editor. The templates use Code v2, HTTP Request v4.2, Schedule Trigger v1.2, Manual Trigger v1, and Error Trigger v1. Use the matching available nodes if your editor can’t import a template.
An error workflow didn’t run
Set the error workflow in the monitored workflow’s settings. Trigger a failure from an active automatic workflow. Check that failed executions are saved and the Error Trigger payload contains the original execution ID.
401 or 403 from Automentor
Select the current Header Auth credential on each HTTP Request node. Check the Bearer prefix and replace expired or rotated keys. Scoped workflow keys allow writes and the connection test.
404 or a conflicting execution
Compare the n8n workflow editor ID and Automentor integration ID against the connection card. For failures, use the original execution ID from the Error Trigger payload. Reuse the exact request when retrying after an uncertain response.
Missing heartbeat
Check that the heartbeat workflow is published or active, its schedule matches the expected interval, and n8n can reach the Automentor HTTPS origin. A connection test verifies transport. The scheduled branch sends heartbeats separately.
429, timeout, or temporary outage
Honor Retry-After when present. The templates make up to three HTTP attempts when your n8n version supports Retry on Fail. After those attempts, inspect the saved execution and replay its original payload. A 202 response is a durable receipt.
For n8n’s current behavior, see error handling, Error Trigger, and HTTP Request.