Overview
This node listens to various MOCO events via webhooks and triggers workflows when specified events occur. It is useful for automating processes based on changes or actions in MOCO, such as creation, update, or deletion of activities, comments, companies, contacts, deals, invoices, tasks, users, and many other entities. For example, it can trigger a workflow when a new deal is created or when a comment is updated, enabling real-time automation and integration with other systems.
Use Case Examples
- Trigger a workflow when a new contact is created in MOCO to automatically send a welcome email.
- Trigger a workflow when an invoice payment is updated to update financial records in another system.
- Trigger a workflow when a task is deleted to notify team members.
Properties
| Name | Meaning |
|---|---|
| Trigger On | Specifies the MOCO event that will trigger the workflow. The event is selected from a list of entity-action combinations such as 'Activity Created', 'Contact Updated', 'Invoice/Payment Deleted', etc. |
Output
JSON
body- The JSON payload received from the MOCO webhook event, containing details about the triggered event.
Dependencies
- MOCO API with webhookSecret credential for verifying webhook signatures
Troubleshooting
- Webhook signature verification failure: Ensure the webhook secret configured in credentials matches the one used by MOCO to sign webhook payloads.
- Webhook not triggering: Verify the webhook URL is correctly registered in MOCO and the selected event matches the webhook event.
- Missing required headers in webhook request: The webhook expects specific headers (x-moco-target, x-moco-event, x-moco-timestamp, x-moco-signature, x-moco-user-id, x-moco-account-url) to validate and process the event.
Links
- MOCO API Webhooks Documentation - Official documentation for MOCO webhooks, explaining event types and webhook setup.