SuiteCRM Trigger icon

SuiteCRM Trigger

Handle SuiteCRM events via webhooks (v.1.0.15)
Join our community

Actions6

Overview

This node acts as a trigger for SuiteCRM events via webhooks, specifically supporting operations like adding relationships between modules. It listens for events such as relationship additions in SuiteCRM and triggers workflows based on specified conditions and logic. This is useful for automating processes that depend on changes in relationships within SuiteCRM, such as updating related records or notifying users when a new relationship is established.

Use Case Examples

  1. Trigger a workflow when a new relationship is added between two modules in SuiteCRM, such as linking a contact to an account.
  2. Set up conditions to trigger actions only when specific fields in the relationship change or meet certain criteria.

Properties

Name Meaning
Module The SuiteCRM module on which to trigger the operation, e.g., Contacts, Accounts.
Relationship Name The name of the relationship to monitor for additions.
Description A description for the trigger to clarify its purpose.
Logic The logical operator (AND/OR) to apply between multiple conditions.
Conditions A collection of conditions to check before triggering the webhook, each specifying a field, an operator, and a value to compare against.

Output

JSON

  • body - The JSON payload received from the SuiteCRM webhook, containing event data related to the relationship addition.

Dependencies

  • SuiteCRM API with appropriate credentials for webhook management

Troubleshooting

  • Ensure the SuiteCRM API credentials are correctly configured and have permissions to create and manage webhooks.
  • Verify that the specified module and relationship name exist in SuiteCRM to avoid webhook creation errors.
  • Check network connectivity and webhook URL accessibility from SuiteCRM to ensure events are delivered properly.
  • Common error: "SuiteCRM webhook creation response did not contain the expected data." indicates an issue with webhook creation, possibly due to API changes or permission issues. Verify API responses and credentials.

Links

Discussion