Overview
This node acts as a trigger for workflows based on events from the Whoz platform. It listens for specific event notifications (webhooks) related to workspace activities such as creation or updates of talents, accounts, deals, opportunities, tasks, and projects. When an event matching the configured criteria occurs in the specified workspace, the node activates the workflow.
Common scenarios include automating follow-up actions when a new talent is created, updating CRM records when deals change status, or triggering notifications when tasks are assigned or completed. For example, you could use this node to start a workflow that sends a welcome email whenever a "Talent Created" event is received.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Whoz event that triggers the workflow. Options include: Talent Created, Talent Updated, Account Created, Deal Created/Updated/Deleted/Restored, Opportunity Created/Updated/Won/Lost/Restored, Task Created/Updated/Assigned/Unassigned/Started/Stopped/Cancelled/Uncancelled/Deleted, Project Created. |
| Workspace ID | The unique identifier of the workspace to monitor for the selected events. This ensures the trigger only responds to events from this workspace. |
Output
The node outputs JSON data representing the event payload received from Whoz. The output includes all original event data fields plus an additional __webhook object containing metadata:
eventName: The name of the event that triggered the workflow.workspaceId: The workspace ID configured in the node.receivedAt: Timestamp when the webhook was received.headers: HTTP headers from the webhook request.
If the webhook payload is invalid or missing, the node outputs an error JSON with the raw headers and body for debugging.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication credential for Whoz (an OAuth2 API key).
- The node depends on Whoz's webhook subscription API to register and manage webhooks dynamically.
- The user must configure the workspace ID and select the event type to subscribe to.
- n8n must be accessible via a public URL to receive incoming webhook calls from Whoz.
Troubleshooting
- Webhook registration failure: If the node cannot create or verify the webhook subscription, ensure the API credentials are valid and have sufficient permissions. Also, confirm the workspace ID is correct.
- Invalid webhook payload: If the node outputs an error about invalid payloads, check that Whoz is sending data in the expected format and that the webhook URL is correctly configured.
- Missing events: Verify that the selected event matches the actual events generated in the workspace and that the webhook subscription exists and is active.
- Network issues: Ensure n8n instance is reachable from Whoz servers; firewall or NAT restrictions may block incoming webhook requests.
Links and References
- Whoz API Documentation (for webhook subscription and event details)
- n8n Webhook Node Documentation (general webhook usage in n8n)