Closum: Triggers, Actions and Tools
The Closum Marketplace allows you to connect the Closum application with other platforms, enabling automation across multiple systems in a simple and scalable way.
In this context, the Triggers and Actions described in this article are events and operations from the Closum application itself, which can be used to integrate and synchronize data with external tools (such as CRMs, marketing platforms, or internal systems).
The core logic is simple:
Triggers (Closum) → Tools → Actions (Closum or external applications)
What are Triggers
Triggers are events that happen inside the Closum application and can start an automation flow, either to perform actions within Closum or to communicate with external systems.
Available Triggers (Closum)
- New Lead (API)
Triggered when a new lead is created in Closum via API.
- Contact Updated
Triggered whenever a contact is updated in Closum.
- SMS: Status Updated
Triggered when an SMS status changes (e.g., sent, delivered, failed).
- WhatsApp: Message Received
Triggered when a message is received via WhatsApp in Closum.
👉 Integration example:
A WhatsApp message is received in Closum → Trigger fires → data is sent to an external CRM.
What are Actions
Actions are operations that Closum can execute, either internally or as a response to events coming from other applications.
These actions can be used:
- As a result of a Closum trigger
- Or as the destination of triggers from external tools
Available Actions (Closum)
Lead Management
- Lead: Add Lead
- Lead: Update Lead
- Lead: Edit by Email
- Lead: View Details
- Lead: Delete
Communication
- Email: Send Template
- SMS: Send One-Time Message
- WhatsApp: Send Message Template
Contact Management
- Contact: Add Tag
- Contact: Add Tag by Email
- Contact: Remove
- Contact: Remove Tag by Email
Other
- SMS: Check Credits
- Tag: Create New
- Custom API Request
👉 Integration example:
A new contact is created in an external form → Action in Closum automatically creates the lead.
The role of Tools
Tools allow you to transform data, control logic, and adapt flows between different systems.
They are especially important in integrations, where:
- Data comes in different formats
- Validation or enrichment is required
- Conditional logic is needed between systems
Example use cases in integrations
- Formatting phone numbers before sending to another app
- Parsing JSON from external APIs
- Applying conditions before creating or updating leads
- Distributing leads across teams (round robin)
- Adding delays between multi-channel communications
How it works in real integrations
Example 1: Closum → External CRM
- Trigger: WhatsApp message received in Closum
- Tool: Parse and structure data
- Action: Send data to external API
Example 2: External Tool → Closum
- Trigger: New contact in an external platform
- Tool: Format data
- Action: Create lead in Closum
- Action: Send automated WhatsApp message
Example 3: Bidirectional sync
- Trigger: Contact updated in Closum
- Action: Update external CRM
- Trigger: Update in external CRM
- Action: Update contact in Closum
Best practices for integrations
- Ensure data consistency across systems
- Use Tools to normalize data
- Avoid lead duplication
- Use conditions (branching) to control flows
- Monitor API errors
Conclusion
In the Closum Marketplace, Triggers and Actions from the application act as connection points between systems.
This allows you to:
- Automate processes across multiple tools
- Centralize communication and data in Closum
- Scale operations without increasing manual effort
By combining Triggers, Actions and Tools, you can build robust and flexible integrations tailored to any business workflow.
Updated on: 05/05/2026
Thank you!
