Node: Create Follow-up Task (CRM)
How to use the Create Follow-up Task (CRM) node to schedule actionable reminders on a contact, company, or deal's 360 timeline.
The Create Follow-up Task (CRM) node generates a task with a due date on a contact, company, or deal's 360 timeline — ideal for automating sales or post-sale cadences (e.g. "day 4 of the sequence → call the lead"). Unlike Log Activity / Note (CRM) (which only leaves a note), this task shows up as pending until a salesperson marks it complete.
When to use it
- Automating sales cadences with tasks scheduled across different days.
- Creating an actionable reminder right after creating a deal or a company.
- Ensuring follow-up after events like "contact didn't respond" or "deal stalled".
Configuration
- Title (required): the task's name. Supports variables.
- Body (optional): extra description, supports variables.
- Due in days (optional, default 1): the task becomes due N days after creation.
- Due date (optional): an exact date; when set, it takes priority over "Due in days".
- Subject type and Subject ID (optional): which CRM record the task attaches to (contact, company, or deal). When not set, the node auto-detects the subject from the workflow's trigger (deal, contact, or the deal/contact linked to a board item).
Example
In a sales-cadence automation triggered when a deal is created, you add Create Follow-up Task (CRM) with Title = Call {{trigger.contact_name}}, Body = First cadence touch and Due in days = 2. Two days later, the task shows up pending on the deal's timeline.
Tips
- If the workflow has no clear CRM subject (e.g. it was triggered from a channel without a conversation linked to a deal/contact), the task is simply skipped without an error — make sure this node runs in a context with a contact or deal available.
- Use Due date instead of "Due in days" when you need an exact time (e.g. "tomorrow 9am").
Troubleshooting
- The task doesn't appear: check that the workflow has a contact, company, or deal resolved in context; without a CRM subject, the node skips silently.
- It's due on the wrong date: if Due date can't be parsed, the node falls back to "Due in days".
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.
-
Ready-to-use workflow templates
Start your automations in minutes from prebuilt flows you can customize.