Create an advanced trigger on Cadulis

Guide Objective

This guide will help you configure advanced triggers in Cadulis, designed to automate complex action sequences based on conditional logic, including cross or inter-Business Unit scenarios.

These scenarios allow you to:

• Chain multiple automated actions
• Send conditional messages (email, SMS, push, etc.)
• Automatically re-engage an activity after failure
• Connect Cadulis to your third-party tools (CRM, ERP, ticketing, DMS, etc.)

⚠️ This guide assumes you are already familiar with simple triggers .

1. Typical Use Cases for Advanced Triggers

1.1 Automatic Re-intervention in Case of Failure

• Failed closure → automatic creation of a new intervention
• Possible sequence: customer notification + automatic assignment

1.2 Creation of Scheduled Follow-up Activities

• Intervention → follow-up check at D+30
• Trigger scheduled for 30 days later

1.3 Synchronization with External Tools

• HTTP calls to GLPI, HubSpot, Notion, ERP, etc.
• Automatic data transfer (SFTP) on each modification

1.4 Multi-Business Unit Management

• Activity in BU A → triggers an action in BU B

2. Scheduled Triggers (Planned Mode)

Unlike event-based triggers, scheduled triggers execute at a specific date or frequency.

Example:

• Goal: follow up with a client if no closure after 3 days
• Mode: scheduled
• Frequency: every day at 08:00
• Condition: activity created more than 3 days ago AND status is to be scheduled
• Action: send an email or HTTP call to a CRM

💡 Create a test Business Unit to validate your scheduled triggers.

3. Advanced Replacement Variables

Dynamically insert data into your messages or API requests:

• {intervention.reference} → intervention reference
• {intervention.date} → scheduled date
• {intervention.customer.name} → customer name
• {intervention.report.status} → closure status
• {system.dateTimeNow} → real-time timestamp

4. Creating a Trigger Chain

Complete example:

Failed closure → Notification → SMS → Create new activity → Team leader notification

Steps:

1. Create 4 separate triggers
2. The creation order determines the execution order
3. Enable or disable priority as needed
4. Use logical conditions and operators to link the steps together

5. Best Practices

🎯 For efficient and maintainable triggers:

• Clearly name each trigger:
  e.g. "[BU] - Failed Closure - Customer Notification"
• Always test on a pre-production BU
• Use logs to verify execution
• Group your triggers by type:
  • Communication
  • Automation
  • Integration

Need Help?