# Schedules and triggers ### **Overview** We've already covered r[unning automations](https://docs.codewords.ai/~/revisions/CBsznWzxyNtIJHNMAo7I/core-concepts/running-automations) manually, but you can also set up schedules and triggers to run your automations in the background. * **Schedules:** These are automations that you set up to run at a specific time and frequency. For example, every day at 9am. * **Triggers:** These automations are set-off after a specific action is completed. For example, reacting to a Slack message with a specific emoji. These features allow you to create an autonomous system around your day-to-day life or work. ### Schedules Schedules let you run workflows automatically at set intervals. This is ideal for reports, reminders, or maintenance tasks. All schedule times are in UTC. You can choose how often your workflow automation should run, and at what time and frequency: * Hourly * Daily * Weekly * Monthly * Custom interval #### Setting up schedules It's easy to set up schedules for your automations from within CodeWords. Simply head to your automation's run page, and select `Schedule` in the top-right corner. From there: * Decide how often you'd like the automation to run. You can choose to run the automation once at a specific time, or on a recurring schedule. * Finish adding any inputs. * You can tick or untick whether you'd like to receive email confirmations when your workflow runs. * Click `Save` . Whilst you're building an automation with Cody in the chat, you can also ask Cody there to set up the schedule for you.
#### Managing schedules You'll find an overview of all your current schedules on the [**Scheduled Runs**](https://codewords.agemo.ai/workflows/schedule) page. From here: * You can see when your workflow last ran and when it's next scheduled to run. * You can search for schedules. * You can toggle on or off the schedule. * You can select three dots and * Edit the schedule. * Resume the schedule. * Delete the schedule. * Disable email notifications for the schedule. ### Triggers Triggers allow your automations to start running when a specific action is completed. For example, when a message is sent, a form is submitted, or a new record is created. You can ask Cody to set up a trigger for your workflow either during the building process or as a later edit. Once your trigger has been set up, you'll be able to test that it works with Cody. You can use real or fake data, and Cody will be able to confirm or debug the setup. #### **Examples of triggers** Let's go through some more specific examples for different triggers, depending on the integrations you'd like to use in your workflows. * **Slack:** New messages, reactions, or when a user joins a channel * **WhatsApp:** Incoming messages sent to the shared CodeWords DM bot number, group messages where the shared CodeWords group bot is a member, messages from your own connected WhatsApp number, and message reactions. * **Gmail:** New emails, label changes, or draft creation * **Google Calendar:** Event creation, updates, or deletions * **GitHub:** Code pushes, new issues, pull requests * **Notion:** Page or database updates * **Discord, HubSpot, Stripe, Airtable**, and many more In general, you don't need to check beforehand whether you can set up a specific trigger. Just ask Cody in the chat interface to set one up, or ask for examples you could use. If your app supports event-based actions, CodeWords can likely trigger from it. #### Managing triggers You'll find an overview of all your current triggers on the [**Triggers**](https://codewords.agemo.ai/workflows/triggers) page. From here: * You can check whether the trigger is active and when it previously ran. * You can search for triggers. * You can see how often the trigger has been actioned. * You can toggle on or off the workflow trigger. * You can select three dots and * Pause the trigger. * Delete the trigger. * Disable the email notification. #### **Custom Webhooks** If your system isn’t natively supported, CodeWords provides custom webhook URLs to handle external events. \ These URLs can be called from any platform capable of sending HTTP POST requests with JSON data. To create one, simply tell Cody which external system you want to connect. Cody will automatically generate and configure the webhook endpoint for you. To learn more about Webhooks in CodeWords, visit the [Webhooks](https://docs.codewords.ai/fundamentals/webhooks) documentation page. ### **When to use each** | Use Case | Best Option | | ------------------------------------------ | ---------------------- | | Reacting instantly to new data or messages | Event-driven trigger | | Running recurring reports or reminders | Scheduled trigger | | Connecting unsupported systems | Custom webhook trigger | Event-driven triggers are best for responsive workflows. Scheduled triggers are ideal for predictable, time-based automation. ### FAQs
What if my app isn’t supported? You can use custom webhooks. Cody will create a webhook URL you can connect to any system that sends HTTP POST requests with JSON data.
What are triggers? CodeWords supports 3,000+ event sources, including Gmail, Notion, GitHub, Stripe, and HubSpot. You can set up triggers for most popular apps without any extra configuration.
Can I see or edit my active triggers? Yes, visit the Triggers page in CodeWords to manage, pause, or delete any active event-based automation.
Do triggers run even when I’m offline? Yes. Once set up, triggers and schedules run automatically in the background — no manual action needed.
### **Overview** We've already covered r[unning automations](https://docs.codewords.ai/~/revisions/CBsznWzxyNtIJHNMAo7I/core-concepts/running-automations) manually, but you can also set up schedules and triggers to run your automations in the background. * **Schedules:** These are automations that you set up to run at a specific time and frequency. For example, every day at 9am. * **Triggers:** These automations are set-off after a specific action is completed. For example, reacting to a Slack message with a specific emoji. These features allow you to create an autonomous system around your day-to-day life or work. ### Schedules Schedules let you run workflows automatically at set intervals. This is ideal for reports, reminders, or maintenance tasks. All schedule times are in UTC. You can choose how often your workflow automation should run, and at what time and frequency: * Hourly * Daily * Weekly * Monthly * Custom interval #### Setting up schedules It's easy to set up schedules for your automations from within CodeWords. Simply head to your automation's run page, and select `Schedule` in the top-right corner. From there: * Decide how often you'd like the automation to run. You can choose to run the automation once at a specific time, or on a recurring schedule. * Finish adding any inputs. * You can tick or untick whether you'd like to receive email confirmations when your workflow runs. * Click `Save` . Whilst you're building an automation with Cody in the chat, you can also ask Cody there to set up the schedule for you.
#### Managing schedules You'll find an overview of all your current schedules on the [**Scheduled Runs**](https://codewords.agemo.ai/workflows/schedule) page. From here: * You can see when your workflow last ran and when it's next scheduled to run. * You can search for schedules. * You can toggle on or off the schedule. * You can select three dots and * Edit the schedule. * Resume the schedule. * Delete the schedule. * Disable email notifications for the schedule. ### Triggers Triggers allow your automations to start running when a specific action is completed. For example, when a message is sent, a form is submitted, or a new record is created. You can ask Cody to set up a trigger for your workflow either during the building process or as a later edit. Once your trigger has been set up, you'll be able to test that it works with Cody. You can use real or fake data, and Cody will be able to confirm or debug the setup. #### **Examples of triggers** Let's go through some more specific examples for different triggers, depending on the integrations you'd like to use in your workflows. * **Slack:** New messages, reactions, or when a user joins a channel * **WhatsApp:** Incoming messages sent to the shared CodeWords DM bot number, group messages where the shared CodeWords group bot is a member, messages from your own connected WhatsApp number, and message reactions. * **Gmail:** New emails, label changes, or draft creation * **Google Calendar:** Event creation, updates, or deletions * **GitHub:** Code pushes, new issues, pull requests * **Notion:** Page or database updates * **Discord, HubSpot, Stripe, Airtable**, and many more In general, you don't need to check beforehand whether you can set up a specific trigger. Just ask Cody in the chat interface to set one up, or ask for examples you could use. If your app supports event-based actions, CodeWords can likely trigger from it. #### Managing triggers You'll find an overview of all your current triggers on the [**Triggers**](https://codewords.agemo.ai/workflows/triggers) page. From here: * You can check whether the trigger is active and when it previously ran. * You can search for triggers. * You can see how often the trigger has been actioned. * You can toggle on or off the workflow trigger. * You can select three dots and * Pause the trigger. * Delete the trigger. * Disable the email notification. #### **Custom Webhooks** If your system isn’t natively supported, CodeWords provides custom webhook URLs to handle external events. \ These URLs can be called from any platform capable of sending HTTP POST requests with JSON data. To create one, simply tell Cody which external system you want to connect. Cody will automatically generate and configure the webhook endpoint for you. To learn more about Webhooks in CodeWords, visit the [Webhooks](https://docs.codewords.ai/fundamentals/webhooks) documentation page. ### **When to use each** | Use Case | Best Option | | ------------------------------------------ | ---------------------- | | Reacting instantly to new data or messages | Event-driven trigger | | Running recurring reports or reminders | Scheduled trigger | | Connecting unsupported systems | Custom webhook trigger | Event-driven triggers are best for responsive workflows. Scheduled triggers are ideal for predictable, time-based automation. ### FAQs
What if my app isn’t supported? You can use custom webhooks. Cody will create a webhook URL you can connect to any system that sends HTTP POST requests with JSON data.
What are triggers? CodeWords supports 3,000+ event sources, including Gmail, Notion, GitHub, Stripe, and HubSpot. You can set up triggers for most popular apps without any extra configuration.
Can I see or edit my active triggers? Yes, visit the Triggers page in CodeWords to manage, pause, or delete any active event-based automation.
Do triggers run even when I’m offline? Yes. Once set up, triggers and schedules run automatically in the background — no manual action needed.
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.codewords.ai/automations/schedules-and-triggers.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.