Quepasa Trigger icon

Quepasa Trigger

Starts the workflow when Quepasa events occur

Quepasa Trigger

AI-generated

Overview

The Quepasa Trigger node starts an n8n workflow when events from the Quepasa API occur. It listens for incoming webhook POST requests from Quepasa, validates the user-agent to ensure requests come from Quepasa clients, and then triggers the workflow with the event data. This node is useful for automating processes based on real-time events from the Quepasa platform, such as receiving messages or status updates from a WhatsApp bot.

Use Case Examples

  1. Automatically process incoming WhatsApp messages received via Quepasa API.
  2. Trigger workflows to log or respond to specific Quepasa events in real-time.

Properties

Name Meaning
Authentication Selects the authentication method to use for connecting to Quepasa API, either via parameters or predefined credentials.
BaseUrl The base URL of the Quepasa API endpoint, required if using Parameters authentication.
Token The token for the WhatsApp bot to authenticate API requests, required if using Parameters authentication.
Forward Internal Boolean flag to indicate whether internal messages sent by the API should be forwarded.
Track ID Optional system identifier to avoid processing duplicated messages, shown only if Forward Internal is true.
Extra Attributes Optional key-value pairs to add extra attributes to the event data, supporting multiple entries.

Output

JSON

  • body - The JSON payload received from the Quepasa webhook POST request, containing event data.

Dependencies

  • Quepasa API with webhook support

Troubleshooting

  • If the webhook URL is not registered or recognized by the Quepasa API, the node will fail to create or verify the webhook. Ensure the webhook URL is correctly set and accessible.
  • If the incoming request's user-agent header does not start with 'Quepasa' or is identified as a bot, the node will reject the request with a 403 error. Make sure the webhook is only called by valid Quepasa clients.
  • Errors with HTTP status codes other than 200 during webhook registration or deletion indicate issues with API connectivity or credentials. Verify the BaseUrl and Token or stored credentials are correct.

Discussion