Your Trigger.do Questions Answered: A Comprehensive FAQ

Building cutting-edge AI applications and agentic workflows requires seamless automation and the ability to initiate actions at the right time. That's where trigger.do comes in. As a core component of the .do platform, trigger.do empowers you to trigger events and initiate workflows or actions within your AI applications with simple, powerful API calls.

But you might have some questions about how it all works. Let's dive into a comprehensive FAQ to shed light on how you can instantly activate your agentic workflows.

What is trigger.do?

trigger.do is your gateway to initiating any defined process, workflow, or action within your .do environment. Think of it as the central switch that lets you kick off complex operations, from data processing pipelines to agentic responses, with a single API call. It's designed to be easy to integrate into your existing applications and services.

Can I pass data when triggering an event?

Absolutely! One of the key strengths of trigger.do is its flexibility. When you make a trigger call, you can include a custom data payload. This payload allows you to pass crucial context and information to the initiated workflow or action. For example, you could pass a user ID, event type, or any other relevant data that the triggered process needs to operate effectively.

Here's a quick look at a TypeScript code example demonstrating how to include a payload:

import { Do } from "@do/sdk";

const doClient = new Do({
  apiKey: "YOUR_API_KEY"
});

async function triggerWorkflow() {
  try {
    const result = await doClient.trigger(
      "your-workflow-id",
      {
        payload: {
          "user_id": "abc123",
          "event_type": "user_registered"
        }
      }
    );
    console.log("Trigger successful:", result);
  } catch (error) {
    console.error("Failed to trigger workflow:", error);
  }
}

triggerWorkflow();

This simple snippet shows how you can provide valuable information like a user_id and event_type directly to the workflow being triggered.

How do I find the ID of the workflow or action I want to trigger?

Finding the unique identifier for the workflow or action you want to trigger is straightforward. All of your defined workflows and actions within the .do platform have unique IDs. You can easily locate these IDs within the .do platform interface. Navigate to the specific workflow or action you've created, and its ID will be readily available for you to use in your API calls.

Ready to Start Anything Now?

trigger.do is designed to empower you to build dynamic and responsive AI applications. By providing a simple and reliable way to initiate workflows and actions, it allows you to focus on building the intelligence of your agents and the logic of your applications, knowing that the underlying processes can be easily activated when needed.