n8n Atria Webhook: Forward Feed Events to Custom HTTP

Automatically forward Atria feed events to your custom HTTP endpoint

n8n Atria Webhook: Forward Feed Events to Custom HTTP listens for incoming Atria feed events, extracts the key metadata and event count from the payload, and then POSTs the formatted JSON to any HTTP endpoint you choose—such as a webhook.site URL for easy inspection. It also includes an optional manual path to verify your feed configuration.

What this workflow does

• Receives Atria events via an n8n-nodes-atriaatria trigger webhook.
• Extracts and formats payload data (event metadata and count) from the incoming Atria payload.
• Sends the formatted data as a JSON string in a POST request to your configured endpoint (e.g., webhook.site/REPLACE_WITH_YOUR_TOKEN).
• Supports manual execution to fetch feed details from Atria and confirm the feed configuration when run manually.

Use cases

• Event forwarding: route Atria feed events into your own API, microservice, or internal logging endpoint.
• Webhook testing: use webhook.site to validate that your Atria events arrive and are shaped correctly.
• SaaS operator workflows: trigger downstream processing whenever Atria emits new feed activity, without manual polling.
• Automation engineering: verify Atria feed configuration via the optional manual run before enabling live forwarding.

Technical details

• Triggers/Nodes: n8n-nodes-atriaatria trigger, set
• Data delivery: HTTP Request node sending a POST with JSON-formatted event data
• Manual support: manual trigger path for fetching feed details from Atria
• Requirements: Atria free account and an Atria API key

Setup checklist

• Create an Atria API credential in n8n and update the placeholder credential ID/name in the Atria nodes.
• Replace REPLACE_WITH_FEED_UUID with your Atria feed ID in both the trigger and feed retrieval step.
• Replace webhook.site/REPLACE_WITH_YOUR_TOKEN with your target HTTP endpoint.