Resources · n8n integration

Beyond Presence n8n integrationAutomate Beyond Presence with n8n.

Can a video agent go live straight from a workflow? That is what the Beyond Presence n8n integration does: 3 operations spread over 3 resources: create an agent, read the available avatars, and handle a webhook event. Nothing ships as a trigger here, so a Schedule Trigger or a Webhook starts the run.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-beyondpresence) you install from Settings › Community nodes on a self-hosted instance. npm

Try the Beyond Presence integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Beyond Presence n8n integration actually give you?

The Beyond Presence node lets a workflow deploy video agents, read the avatars available to your account, and process the events a call sends back. It covers 3 operations on 3 resources: agent.create, avatar.get and webhook.handleEvent, each one mapping directly to a call the Beyond Presence API already exposes, with no extra translation layer in between.

Spin up one agent per campaign. A landing page fills a sheet, the workflow reads the new row, and agent.create deploys an agent with its own System Prompt, its own Greeting and the right Language. The agent ID that comes back goes straight into the same row in Google Sheets, so the sales team always knows which agent belongs to which offer.

Pick the face before you deploy. Hardcoding an avatar ID ages badly. Run avatar.get first, keep the avatar you want, then pass its ID to the create step in the same execution. Two nodes, no copy and paste, and the workflow keeps working when the account gets new avatars.

Turn a finished call into a follow-up. Beyond Presence posts events to a URL. An n8n Webhook node receives them, webhook.handleEvent parses the payload and keeps only the call_ended events, and the rest of the workflow does the work: a recap in Slack for the account owner, a follow-up message through Gmail for the prospect. A webhook, here, is simply a URL that a service calls the moment something happens on its side.

When to drop down to HTTP Request. Three operations is a small surface. Anything the Beyond Presence API exposes beyond creating an agent, listing avatars and handling events is reachable with the HTTP Request node, which calls any endpoint of the API and reuses the same credential through predefined authentication. Same login, no extra setup.

Know the edges before you build. There is no Beyond Presence trigger node, so a workflow around this tool always starts somewhere else. And because the package is a community node, n8n Cloud only accepts it once it is verified, while a self-hosted instance installs it from Settings without waiting. If you are still choosing your automation platform, the n8n review lays out how self-hosting changes the equation.

Connect

How do you connect Beyond Presence to n8n?

  1. 01

    Install the community node

    Open Settings, go to Community nodes, and install the npm package n8n-nodes-beyondpresence, currently in version 0.4.0. This is a self-hosted move: n8n Cloud only accepts community nodes that have been verified. Once the install finishes, Beyond Presence appears in the node panel and n8n costs nothing extra for it.

  2. 02

    Create the credential once

    Grab an API key on the Beyond Presence side, following the official guide at docs.bey.dev/api-key, then open the Credentials menu in n8n and save a Beyond Presence credential with it. A credential in n8n is a stored login: you set it up once, and every workflow on the instance can reuse it without pasting the key again.

  3. 03

    Point the node at the credential

    Drop a Beyond Presence node on the canvas and pick the credential you just saved from the dropdown at the top of the node. Choose the resource, choose the operation, then run the node on a single item to confirm the call goes through. Start with avatar.get: it needs no parameter, so a clean response means the key is valid.

Actions

What can the Beyond Presence node do?

The Beyond Presence node exposes 3 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetHandle Event
Agent✓
Avatar✓
Webhook✓

Agent

1 operation
01

Create a new agent

agent.create

What you see in n8n

Notes & use cases

Deploys a new agent with the configuration you pass in, and hands back the agent so the next node can use it. No parameter is required, which means a bare call creates an agent on defaults.

Key parameters

  • Avatar ID: the ID of the avatar the agent wears on camera, usually {{ $json.id }} pulled from an earlier step.
  • System Prompt: the instructions the agent follows during the call.
  • Language: a single value from the list, en, fr, es, de, pt and others.
  • Greeting: the opening line the agent says.
  • Max Session Length (Minutes): the ceiling on one session.
  • Capabilities: tick webcam_vision to enable webcam vision.
Use cases
a demo agent per product launch, each with its own prompt and greeting.

Avatar

1 operation
02

Get the available avatars

avatar.get

What you see in n8n

Notes & use cases

Reads back the avatars your Beyond Presence account can use. There is no parameter to fill, so the node runs as is and returns the list, ready to be filtered by name or picked by position in the following node.

Use cases
feed a picker before creating agents, so the avatar ID is resolved at run time instead of being frozen in the workflow. It also works as a health check: if this operation answers, the credential is valid and the community node is installed correctly on the instance you are testing.

Webhook

1 operation
03

Handle webhook event

webhook.handleEvent

What you see in n8n

Notes & use cases

Processes the events Beyond Presence sends about a call, so the raw payload becomes something the rest of the workflow can branch on.

Key parameters

  • Webhook Data: required, the payload itself. For an n8n Webhook node that carries the data in the body property, pass $JSON.body.
  • Event Type: call_ended when a call ends, message when a message is exchanged during a call, or all to process every type.
  • Filter by Agent IDs: turn it on to keep only some agents.
  • Agent IDs: the comma separated list, for example agent_123,agent_456.
Use cases
route call transcripts and end-of-call recaps down two different branches.
Need help

Need help automating Beyond Presence with n8n?

A person reads every message.

FAQ

Beyond Presence and n8n: the questions that come up

01Is the Beyond Presence n8n integration free?
Yes on the n8n side, with one condition attached. Beyond Presence is a community node: it is not shipped with n8n, and it is not a paid add-on either. You install the npm package n8n-nodes-beyondpresence, version 0.4.0, from Settings and then Community nodes on a self-hosted instance, and nothing is billed by n8n for using it. n8n Cloud is the exception: it only accepts community nodes that have been verified, so the install path there depends on that status. What Beyond Presence itself costs for an account or for call minutes is a separate matter, and this page does not cover it.
02What credentials do you need for Beyond Presence in n8n?
One API key, saved once as a credential. The node has no authentication selector to choose from, so there is a single path: get the key on the Beyond Presence side by following the official guide at docs.bey.dev/api-key, then open the Credentials menu in n8n and save it there. A credential is stored at instance level, which means every workflow on that instance sees it in the node dropdown and no key ever gets pasted into a node. Create it once, reuse it everywhere, and rotate it in one place when the time comes.
03What are the limits of the Beyond Presence node in n8n?
The node covers 3 operations on 3 resources, and that is the whole surface: create an agent, get the available avatars, handle a webhook event. Anything else the Beyond Presence API exposes is not in the node. The workaround is standard n8n practice: the HTTP Request node calls any endpoint of the API and reuses the same credential through predefined authentication, so you keep one login for both. The node is in version 1, and the package itself is a community release at 0.4.0, which is worth knowing before you pin a production workflow to it.
04Does Beyond Presence trigger an n8n workflow in real time?
Not on its own, because there is no Beyond Presence trigger node in n8n. A workflow around this tool starts somewhere else, and you have three usual options. A Schedule Trigger fires at a fixed interval, which fits recurring jobs like creating the agents for tomorrow's demos. An n8n Webhook node gives you a URL that a third party service calls, and that is where the handleEvent operation earns its place. Or another tool's trigger starts the run, and Beyond Presence is simply one step in the chain.
05n8n or Make for Beyond Presence?
It comes down to hosting, data control and how you want to pay. Make is a hosted automation platform with no self-hosting option, billed per operation, so the cost follows volume. n8n runs either way: self-hosted with Docker or npm, or on n8n Cloud, the hosted offer from n8n, and a workflow behaves the same in both. For Beyond Presence specifically, self-hosting matters more than usual, since installing a community node from Settings is only possible there. Both are visual builders, so the real question is where the calls and the call data should live.
Same platform

Other docs you might need on this stack.

Browse all integrations