Workflow automation is powerful, but its true strength lies in its ability to react intelligently to a myriad of events happening across your business. Not all events are created equal, and they certainly don't all carry the same type of data. This is where Triggers.do, the event-based workflow automation platform, shines. Triggers.do allows you to define and customize triggers that are sensitive to the specific data types and structures embedded within the events they receive.
Imagine you're automating your sales process. A "new order created" event from your e-commerce platform will contain different data (order ID, total amount, customer details) than a "customer feedback submitted" event from your CRM (customer ID, feedback text, rating). Triggers.do is built to handle this diversity, enabling you to build truly responsive and nuanced automation.
The type of data associated with an event significantly impacts how you should process it and, consequently, which workflow should be initiated.
Without the ability to understand and leverage these different data types, your automation workflows would be rigid and less effective.
Triggers.do provides the flexibility to define triggers that specifically anticipate and utilize different data types within your events. Here's how it works:
1. Event Definition: When you define a trigger in Triggers.do, you specify the event it listens for (e.g., order.created, feedback.submitted). You also associate a source to identify where the event originates.
const newOrderTrigger = new Trigger({
name: 'New Order Created',
description: 'Triggers when a new order is created in the system',
event: 'order.created',
source: 'ecommerce-platform',
// ...
});
2. Data Access in the Handler: The core of customizing for data types lies in the handler function of your trigger. This function receives the event data, allowing you to access and process it based on its expected type and structure.
async (event) => {
// Access event data based on its type
const orderAmount = event.data.amount; // Assuming 'amount' is a number
const customerName = event.data.customer.name; // Assuming nested data
// Use the data to inform workflow initiation or processing
if (orderAmount > 100) {
return {
workflowId: 'high-value-order-processing',
data: event.data
};
} else {
return {
workflowId: 'standard-order-processing',
data: event.data
};
}
}
3. Robust Filtering: Triggers.do's filtering capabilities are where data type understanding truly shines. You can define conditions based on specific data points within the event payload, ensuring workflows are triggered only when relevant.
filter: {
condition: 'amount > 100', // Filtering based on numeric data
priority: 'high'
}
This example filter directly operates on the amount field, expecting it to be a number. You could create filters for other data types too, such as:
By leveraging these features, you can create triggers that not only react to events but also intelligently interpret the data within those events to make informed decisions about which workflows to start and how to process the information.
The ability to handle diverse event data types with customized triggers is fundamental to building responsive and efficient business processes. With Triggers.do, you can:
Triggers.do is not just about initiating workflows; it's about initiating the right workflows based on the right data at the right time. This level of intelligent responsiveness is what sets truly effective automation apart.
Ready to build powerful, event-driven automation that understands your data? Triggers.do provides the platform and tools you need to define custom triggers tailored to the diverse events and data types within your systems. Start creating responsive business processes that react to changes in real-time.
Explore the possibilities of event-based workflow automation with Triggers.do and transform how your business operates.