The First Node in a workflow sets the stage for all subsequent actions and controls how and when the workflow scheduling begins.
Suppose you want to send a reminder email to the candidate two days before the interview. You can configure when the First Node will execute using options like Trigger Now, Static Date, or Date Field with an offset. By default, scheduling is applied to the First Node, ensuring it runs according to the specified timing or date.
Scheduling Options for the First Node
When configuring the first node after the trigger, you can apply various scheduling settings.
You can also set when an action should occur, whether it's immediately, on a specific date, or based on a date variable with an optional delay.
These settings allow precise control over when actions (e.g., sending an SMS or email) are executed.
Scheduling Date
| Trigger Now | Executes the action immediately upon reaching the first node. |
| Static Date | This option allows you to select a specific date and time for the action to occur. Only dates after the current date are valid. |
| Date Field | Use a date variable within the system. This option includes an Offset feature, allowing you to adjust the date forward or backward by a set number of days, weeks, or months.
Offset:
|
Configure Scheduling for Static Date
Configure Scheduling for Date Field
Scheduling Time
| Trigger Time | Executes the action as soon as the trigger event occurs. This is the default option. |
| Static Time | Specify a fixed time for the action. The time zone aligns with the agency’s time zone, with options presented in 30-minute intervals. |
| Time Field | Similar to the Date Field, this setting allows you to select a time variable and adjust it with an offset in hours.
Offset:
|
Configure Scheduling for Static Time
Configure Scheduling for Time Field
Scheduling Based on Previous Node Output
Overview
Candidates often reply to your messages with a time that suits them, like "call me tomorrow at 3pm." With the Scheduled on Previous Node Output scheduling option, you can send your next workflow step at exactly that time instead of on a fixed schedule.
An AI Extractor picks up the date and time from the candidate's reply. Your voice call, SMS, email, or other step then goes out at that time, in the candidate's timezone. This way, you reach candidates when they said they'd be ready.
Use cases
Here are a few ways you can use this scheduling option in your workflows.
Call candidates back when they're available
You text a candidate to ask when they're free to talk about a role, and they reply, "I'm available today at 4 PM." Your AI Extractor picks up the time, and your Voice Call step calls them at 4 PM. There's no back-and-forth to arrange the callback.
Send interview messages at the confirmed time
A candidate confirms their interview slot over SMS or email. Your AI Extractor captures the date and time, and your next message goes out at that time.
Follow up on an offer when the candidate is ready
You share an offer with a candidate, and they reply that they'll confirm their decision by Friday afternoon. Your AI Extractor picks up that time, and your follow-up goes out when they said they'd be ready.
Check in after a placement at a time that suits them
After a placement, you ask the candidate when they're free to chat about their onboarding. Your check-in goes out at the time they give you, so you don't need to schedule it by hand.
Here's what you'll need in place:
- The AI Extractor enabled for your account. This scheduling option is available wherever the AI Extractor is enabled. If you're not sure, check with your CSM.
- An AI Extractor earlier in your workflow. You'll only see Scheduled on Previous Node Output on a step that has an AI Extractor before it.
- A step that asks for the candidate's availability. For example, an SMS asking when they're free for a quick call.
How it works
The AI Extractor turns the candidate's reply into a date and time. For example, "tomorrow at 3" becomes 3:00 PM the next day.
Your next step is scheduled for that date and time in the candidate's timezone. You set this up by selecting the AI Extractor in the step's scheduling settings.
A Path makes sure the AI Extractor reads the reply. Without a Path that waits for the candidate to respond, the AI Extractor runs as soon as your message is sent, before there's anything to read.
The candidate's requested time overrides blackout days. If they ask to be contacted on a blackout day, the step still goes out at the time they asked for. If the fallback runs, your blackout settings still apply.
Fallback controls what happens when there's no usable time. If the extracted time is missing, invalid, or in the past, the step either falls back to After Previous Node or skips the candidate.
Capture the candidate's preferred time
First, set up the part of your workflow that asks for availability and reads the answer. When you're done, the AI Extractor will hold the date and time the candidate gave you.
- Open the workflow you want to update.
- Add the step that asks for the candidate's availability, such as an SMS step.
- Add a Path after it that waits for the candidate to reply (e.g., Conversation Completed).
- Add an AI Extractor after the Path. Use the reply or transcript from the previous step as input, and set it up to extract the date and time.
Schedule the next step from the extracted time
Next, add the step you want to send at the candidate's preferred time and connect its schedule to the AI Extractor. At the end, the step will wait for the time the candidate asked for.
- Add the step you want to schedule after the AI Extractor, such as a Voice Call, SMS, or Email step.
- Open the step's Scheduling settings and expand Schedule Date.
- Under Send on, select Scheduled on Previous Node Output.
- In Select Node, choose the AI Extractor you added earlier.
- Select or clear Enable fallback, depending on what you'd like to happen when no usable time is found.
- Click Save.
| What the AI Extractor finds | Enable fallback selected | Enable fallback cleared |
|---|---|---|
| A date and time in the future | Sends at that date and time | Sends at that date and time |
| No date or time, an invalid one, or one in the past | Falls back to After Previous Node (blackout settings apply) | Doesn't send; the candidate is skipped |
Expected result
When a candidate replies with a preferred time, your scheduled step goes out at that time in their timezone, even on a blackout day. If no usable time is found, the step falls back to After Previous Node or skips the candidate, depending on your fallback setting. On the workflow canvas, the step's card shows Send at the time from previous node output.
To test it, run the workflow with a contact you control. Reply with a specific time a few minutes ahead, such as "call me today at 4:15pm," and check that the next step arrives at that time.
Example
Let's say you text candidates to ask when they can talk about a role, and you want your voice agent to call them back at that time.
| Step | What happens |
|---|---|
| SMS | "Hi Priya, when's a good time for a quick call about the Warehouse Associate role?" |
| Path (conversation completed) | Waits for Priya to reply: "Tomorrow at 3pm works." |
| AI Extractor | Picks up tomorrow's date and 3:00 PM. |
| Voice Call | Your voice agent calls Priya tomorrow at 3:00 PM her time. |
Important notes and limitations
- An AI Extractor must come earlier in the workflow. Without one, Scheduled on Previous Node Output doesn't appear in the scheduling options.
- Add a Path before the AI Extractor. Otherwise, the AI Extractor has no reply to read.
- Requested times override blackout days. Keep this in mind if you use blackout days to avoid contacting candidates at certain times. If the fallback runs, blackout settings still apply.
- With Enable fallback cleared, candidates without a usable time are skipped. They won't receive the step.
Troubleshooting
| Problem | Likely cause | What you can do |
|---|---|---|
| You don't see Scheduled on Previous Node Output. | There's no AI Extractor before the step, or the AI Extractor isn't enabled for your account. | Add an AI Extractor earlier in the workflow. If you can't, ask your CSM about enabling it. |
| The step goes out right after the previous step instead of at the requested time. | Enable fallback is selected and no usable time was found, often because the AI Extractor ran before the candidate replied. | Add a Path that waits for the reply (for example, conversation completed) just before the AI Extractor. |
| Some candidates never get the step. | Enable fallback is cleared and no usable time was found. | Select Enable fallback if you'd like those candidates to get the step right after the previous step instead. |
| A step went out on a blackout day. | The candidate asked for that time. | This is expected. Requested times override blackout days. |
FAQs
Which steps can I schedule this way? Voice calls, SMS, email, and other workflow steps.
What if the candidate doesn't mention a time? The step follows your fallback setting. If Enable fallback is selected, it falls back to After Previous Node. If it's cleared, the candidate is skipped. The same applies when the time has already passed.
Why did my step ignore my blackout days? The candidate's requested time takes priority, since they asked to be contacted then.
Why do I need a Path before the AI Extractor? The Path waits for the candidate's reply. Without it, the AI Extractor runs as soon as your message is sent.