Documentation Index
Fetch the complete documentation index at: https://docs.nedzo.ai/llms.txt
Use this file to discover all available pages before exploring further.
Fires on a time-based schedule. Use it to run workflows at a specific date and time, or on a recurring cadence like every hour, daily, or weekly. Schedule triggers run against your contacts, so you can target specific segments with filters.
When it fires
The trigger fires at the scheduled time. For one-time schedules, it fires once and stops. For recurring schedules, it fires on every interval until you deactivate the workflow or the end date is reached.
When the trigger fires, it creates one workflow execution per contact that matches your contact filters. If no filters are set, it runs for all contacts in the workspace.
Configuration
Schedule mode
Choose between two modes:
| Mode | Description |
|---|
| One-time | Fires once at a specific date and time |
| Recurring | Fires repeatedly on a set interval |
One-time schedule
| Field | Required | Description |
|---|
| Date & time | Yes | When the workflow should run. Must be at least 1 minute in the future. |
| Timezone | Yes | IANA timezone for the scheduled time (e.g., America/New_York, Europe/Amsterdam) |
Recurring schedule
| Field | Required | Description |
|---|
| Frequency | Yes | How often to run: minutes, hours, days, weekly, or monthly |
| Interval | Depends | Number of units between runs. For minutes, minimum interval is 5. |
| Cron pattern | Alternative | Advanced: set a custom cron expression instead of using frequency/interval |
| Timezone | Yes | IANA timezone for the schedule |
| End date | No | Optional date when the recurring schedule stops running |
Frequency examples:
| Frequency | Interval | Result |
|---|
| minutes | 30 | Every 30 minutes |
| hours | 2 | Every 2 hours |
| days | 1 | Once a day |
| weekly | 1 | Once a week |
| monthly | 1 | Once a month |
For minutes frequency, the minimum interval is 5 minutes to prevent excessive workflow executions.
Narrow down which contacts the workflow runs for. Add filters to target specific segments instead of running for every contact in your workspace.
Each filter has three parts:
| Part | Description |
|---|
| Field | The contact field to check (e.g., email, phone, tag) |
| Operator | How to compare (equals, not equals, contains, is empty, etc.) |
| Value | The value to compare against |
All filters use AND logic — every filter must match for the contact to be included.
No filters: If you don’t add any filters, the workflow runs for every contact in the workspace.
Data available
When this trigger fires, the following data is available as variables in your workflow:
| Variable | Description | Example |
|---|
{{contactId}} | The contact’s unique ID | a1b2c3d4-e5f6-... |
{{firstName}} | First name | John |
{{lastName}} | Last name | Doe |
{{phone}} | Phone number in E.164 format | +14155551234 |
{{email}} | Email address | john@example.com |
{{businessName}} | Company name | Acme Inc |
Schedule status
After publishing a workflow with a schedule trigger, you can see the schedule status on the workflow:
| Field | Description |
|---|
| Next run | When the workflow will fire next |
| Last run | When the workflow last fired |
| Active | Whether the schedule is currently running |
Deactivating the workflow pauses the schedule. Reactivating it resumes from the next scheduled time.
Use case examples
One-time campaign blast
Send an SMS to all contacts tagged “promo-list” at a specific date and time.
- Trigger: Schedule (One-time) — January 15, 2026 at 10:00 AM EST
- Filter: Has tag → equals → “promo-list”
- Action: Send SMS
- Message: “Hi
{{firstName}}, we have a special offer for you! Reply YES to learn more.”
Daily follow-up calls
Call contacts who haven’t been reached yet, every day at 9 AM.
- Trigger: Schedule (Recurring) — Daily at 9:00 AM
- Filter: Has tag → equals → “needs-call”
- Filter: Has tag → not equals → “called”
- Action: Voice call — Sales agent
- Action: Update contact — Add “called” tag
Weekly check-in SMS
Send a weekly check-in message to active customers.
- Trigger: Schedule (Recurring) — Weekly, Monday at 10:00 AM
- Filter: Has tag → equals → “active-customer”
- Action: Send SMS
- Message: “Hi
{{firstName}}, hope your week is off to a great start! Let us know if you need anything.”
Monthly renewal reminder
Email customers 30 days before their subscription renews.
- Trigger: Schedule (Recurring) — Monthly
- Filter: Has tag → equals → “renewal-due”
- Action: Send email
- Subject: “Your subscription renewal is coming up”
- Body: “Hi
{{firstName}}, your subscription renews next month. Let us know if you have any questions.”
- Action: Update contact — Remove “renewal-due” tag