SuiteCRM Trigger icon

SuiteCRM Trigger

Handle SuiteCRM events via webhooks (v.1.0.15)

Overview

This node acts as a trigger for SuiteCRM events via webhooks, specifically supporting operations like relationship deletion. It listens for events on specified SuiteCRM modules and triggers workflows based on defined conditions and logic. This is useful for automating processes in response to changes in relationships within SuiteCRM, such as deleting a relationship between records.

Use Case Examples

  1. Trigger a workflow when a relationship is deleted in the Contacts module to update related records.
  2. Automate notifications when a specific relationship is removed in the Opportunities module.

Properties

Name Meaning
Module The SuiteCRM module on which to trigger the operation (e.g., Contacts, Opportunities). This is dynamically loaded from SuiteCRM modules.
Relationship Name The name of the relationship to monitor for deletion.
Description A description for the trigger, useful for identifying the webhook's purpose.
Logic The logical operator (AND/OR) to apply between multiple conditions for triggering the webhook.
Conditions A collection of conditions to check before triggering the webhook. Each condition includes a field name, an operator (e.g., equal, greater than, has changed), and a value to compare against if applicable.

Output

JSON

  • workflowData - The JSON array containing the data received from the SuiteCRM webhook event.

Dependencies

  • SuiteCRM API access with appropriate credentials for webhook management

Troubleshooting

  • Webhook creation may fail if the SuiteCRM API credentials are invalid or lack necessary permissions. Verify credentials and permissions.
  • If the webhook does not trigger, ensure the module and relationship names are correctly specified and that the SuiteCRM instance is properly configured to send webhook events.
  • Errors during webhook deletion may occur if the webhook ID is missing or the webhook was already deleted; in such cases, re-creating the webhook may be necessary.

Links

Discussion