Beyond Presence icon

Beyond Presence

Deploy video agents with Beyond Presence
Join our community

Actions2

Overview

This node processes webhook events from Beyond Presence, a platform for deploying video agents. Specifically, it handles incoming webhook payloads related to call and messaging events during agent interactions.

The main use case is to receive and process real-time event data such as when a call ends or when messages are exchanged during a call. This enables workflows to react dynamically to agent interactions, for example:

  • Logging call summaries after calls end.
  • Triggering notifications or analytics based on message exchanges.
  • Filtering events by specific agent IDs to focus on relevant agents only.

Practical examples include integrating Beyond Presence call data into CRM systems, generating reports on call durations and sentiments, or automating follow-up actions based on conversation content.

Properties

Name Meaning
Event Type The type of event to process. Options: "Call Ended" (when a call ends), "Message" (message exchanged during a call), or "All Events" (process all event types).
Filter by Agent IDs Boolean flag to enable filtering of events by specific agent IDs.
Agent IDs Comma-separated list of agent IDs to filter events by. Only used if "Filter by Agent IDs" is true.
Webhook Data The raw webhook payload data to process. Typically the JSON body of the webhook request. Required.

Output

The node outputs an array of JSON objects representing processed event data. Each output item corresponds to one webhook event that matches the configured filters.

Output structure varies by event type:

  • Call Ended event:

    {
  "event_type": "call_ended",
  "call_id": "string",
  "agent_id": "string",
  "call_details": {
    "duration_minutes": number,
    "message_count": number,
    "topic": "string",
    "user_sentiment": "string"
  },
  "user": {
    "name": "string"
  },
  "call_summary": {
    "duration_minutes": number,
    "message_count": number,
    "first_message": "string",
    "last_message": "string",
    "user_sentiment": "string"
  },
  "messages": [
    {
      "sender": "string",
      "message": "string",
      "timestamp": "string"
    }
  ]
}

  • Message event:

    {
  "event_type": "message",
  "call_id": "string",
  "agent_id": "string",
  "user": {
    "name": "string"
  },
  "message": {
    "sender": "string",
    "content": "string",
    "timestamp": "string"
  }
}

  • Other event types produce a minimal object with event_type, call_id, and agent_id.

If an error occurs during processing, the output contains an error field describing the issue.

The node does not output binary data.

Dependencies

  • Requires an API key credential for Beyond Presence API access.
  • The node expects webhook payloads in JSON format, typically provided by n8n's webhook trigger or similar.
  • No additional external dependencies beyond standard HTTP requests to the Beyond Presence API.

Troubleshooting

  • Missing webhook data: If the webhook payload is empty or invalid, the node throws an error "Missing webhook data" or "Invalid webhook JSON". Ensure the webhook trigger correctly passes the JSON body.
  • Agent IDs required when filtering enabled: When "Filter by Agent IDs" is enabled but no agent IDs are provided, an error "Agent IDs required when filtering is enabled" is thrown. Provide a comma-separated list of valid agent IDs.
  • Invalid JSON in webhook data: If the webhook data is malformed JSON, the node will report "Invalid webhook JSON" with details. Verify the source sending the webhook sends valid JSON.
  • Unsupported event types: Events other than "call_ended" or "message" are passed through with minimal data; ensure your workflow can handle unknown event types gracefully.
  • API authentication errors: For operations requiring API calls (not applicable to webhook handling), ensure the API key credential is valid and has proper permissions.

Links and References

Discussion