Beex Trigger icon

Beex Trigger

Recibe actualizaciones de contactos desde Beex Contact Center
Join our community

Overview

This node acts as a webhook trigger for receiving contact updates and related events from the Beex Contact Center platform. It listens for specific event types sent via HTTP POST requests to a configured webhook URL. When an event matching the selected types occurs, the node triggers the workflow with the event data.

Common scenarios include:

  • Automatically processing updated contact information when contacts are modified in Beex.
  • Reacting to new call management records or manual outbound calls logged in Beex.
  • Integrating Beex contact center events into broader automation workflows such as CRM updates, notifications, or analytics.

For example, you could use this node to start a workflow that updates your CRM whenever a contact's details change in Beex, or to log call activities in an external system when manual calls are made.

Properties

Name Meaning
Event Types Select one or more event types to listen for:
- Al Actualizar Contactos: Updates to general and custom contact data
- Al Registrar Tipificación: Registration of call management entries
- Al Llamar Manualmente: Records manually made outbound calls

Output

The node outputs JSON data representing the event payload received from Beex. The output structure directly reflects the webhook request body and can be either a single object or an array of objects depending on the incoming data.

  • json: Contains the event data as received from Beex.
  • No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Beex Contact Center service.
  • The node must be configured with a webhook URL accessible by Beex to send event notifications.
  • No additional external dependencies beyond the Beex API and n8n webhook infrastructure.

Troubleshooting

  • No workflow trigger despite events occurring: Ensure the selected "Event Types" include the event being sent by Beex. If none match, the node will ignore the webhook.
  • Webhook not reachable: Verify that the webhook URL is publicly accessible and correctly configured in Beex.
  • Invalid or missing credentials: Confirm that the API key credential is set up properly in n8n.
  • Unexpected payload format: The node expects JSON payloads with an event property; if the structure differs, the node may not trigger.

Links and References

Discussion