Overview
The Solapi Trigger node listens for events from the Solapi platform by setting up webhooks. It supports multiple event types such as commerce actions, group reports, and single message reports. When an event occurs on Solapi, the node receives the webhook payload and triggers the connected workflow with the event data.
This node is useful for automating workflows based on real-time Solapi events, such as:
- Reacting to commerce-related actions (e.g., purchases or order updates).
- Processing group report notifications.
- Handling individual message delivery or status reports.
For example, you could use this node to automatically update your CRM when a new purchase is made or to log message delivery statuses for analytics.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests: - OAuth2 - API Key (HMAC-SHA256) |
| Event Type | The type of Solapi event to listen for: - On Commerce Action - On Group Report - On Message Report (Single) |
| Commerce Hook Name or ID | (Required if Event Type is "On Commerce Action") Select a specific commerce hook from the list or specify its ID manually. |
Output
The node outputs the webhook payload received from Solapi in the json field of the output data. If multiple events are received in one webhook call (as an array), each event is output as a separate item.
The output structure is essentially the raw JSON data sent by Solapi for the triggered event, allowing downstream nodes to process event details directly.
No binary data output is produced by this node.
Dependencies
- Requires valid authentication credentials for Solapi API, either via OAuth2 or API key with HMAC-SHA256 signature.
- Needs network access to Solapi's API endpoints to manage webhook registration and verification.
- The node uses n8n's HTTP webhook mechanism to receive incoming event notifications.
Troubleshooting
- Webhook URL mismatch: If the webhook URL registered on Solapi does not match the current node webhook URL, the trigger will not activate. Ensure the webhook URL is correctly set and synchronized.
- Invalid credentials: Authentication failures can occur if OAuth2 tokens expire or API keys are incorrect. Verify and refresh credentials as needed.
- Failed webhook creation: Errors during webhook setup may be due to network issues or invalid hook IDs. Check the hook ID validity and network connectivity.
- Event type misconfiguration: Selecting an unsupported event type or missing required properties (like hook ID for commerce actions) will prevent proper webhook registration.
- API rate limits or errors: The node relies on Solapi API calls; hitting rate limits or receiving API errors will cause failures. Monitor API usage and handle errors accordingly.
Common error messages include:
- "Failed to create Solapi webhook: [error message]" — indicates webhook registration failure; check credentials and parameters.
- Network or HTTP errors during API calls — verify connectivity and API endpoint availability.