Overview
The Aimfox Trigger node starts an n8n workflow when specific events occur in the Aimfox platform. It listens for various user and messaging-related events such as account logins, message sends, connection requests, and profile views. This node is useful for automating workflows that respond to real-time activities on Aimfox, like sending notifications, updating CRM systems, or triggering follow-up actions based on user engagement.
Practical examples include:
- Triggering a welcome email when a new connection is made.
- Logging user login events into an external database.
- Starting a workflow to analyze message replies or InMail responses.
Properties
| Name | Meaning |
|---|---|
| Trigger On | Select one or more Aimfox event types to listen for. Options include: |
| - Account Logged In Event | |
| - Account Logged Out Event | |
| - Connect Accepted Event | |
| - Connect Sent Event | |
| - Inmail Reply Event | |
| - Inmail Sent Event | |
| - Message Request Sent Event | |
| - Message Sent Event | |
| - New Connection Event | |
| - New Reply Event | |
| - Profile Viewed Event |
Output
The node outputs JSON data representing the event payload received from Aimfox. Each execution returns an array with one item containing the full event details as provided by the webhook. The structure depends on the event type but generally includes information about the user action, timestamps, and related metadata.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Aimfox API.
- Needs network access to
https://api.aimfox.com/api/v2for webhook management and event reception. - The node registers a webhook URL with Aimfox to receive event callbacks.
Troubleshooting
- Webhook registration failure: Ensure the API key is valid and has permissions to manage webhooks. Check network connectivity to Aimfox API endpoints.
- No events received: Verify that the selected event types are correctly configured and that the webhook URL is publicly accessible.
- Authorization errors: Confirm the API key is correctly set up in the node credentials and has not expired or been revoked.
- Duplicate webhook registrations: The node checks for existing webhooks matching the URL and events; if issues arise, manually verify webhook status in Aimfox dashboard.
Links and References
- Aimfox API Documentation (for detailed webhook and event info)
- n8n Webhook Node Documentation (general concepts of webhook triggers)