Overview
This node triggers workflows in n8n when specific events occur in the awork platform. It listens for a variety of awork events such as additions, deletions, and updates to absences, companies, projects, tasks, time tracking entries, and users. This node is useful for automating processes that depend on changes in awork, such as notifying teams about project updates, syncing data with other systems, or logging activity.
Use Case Examples
- Trigger a workflow when a new task is added in awork to automatically assign it to a team member.
- Start a workflow when a project status changes to update related records in a CRM system.
- Listen for user activation changes to manage access control in integrated applications.
Properties
| Name | Meaning |
|---|---|
| notice | A notice indicating that admin credentials are required to set up webhooks in awork. |
| events | The specific awork events to listen to for triggering the workflow. Multiple events can be selected. |
Output
JSON
body- The JSON payload received from the awork webhook event containing event details.headers- HTTP headers received with the webhook request.query- Query parameters received with the webhook request.
Dependencies
- awork API with authentication
Troubleshooting
- Webhook will not work if the node is running on localhost without a tunnel or custom domain; ensure the webhook URL is publicly accessible.
- If webhook creation fails, check that the API credentials have admin rights in awork to set up webhooks.
- If the webhook is not triggering, verify that the selected events match those configured in awork and that the webhook is active.
- Error 404 when checking or deleting webhook indicates the webhook does not exist or was deleted; the node will handle this by cleaning up stored webhook data.
Links
- awork API Webhooks Documentation - Official documentation for setting up and managing webhooks in awork.