Workflow Actions
All five workflow actions use the same business-day logic: weekends are skipped automatically, public holidays come from your selected country, and company holidays layer on top when enabled. Multi-Country Calculate uses the country selected manually in that workflow action.
Calculate Business Days
Counts the working days between two dates. Free tier includes 3,000 calculations a month; Pro removes the cap.
Inputs: Start Date, End Date, country holiday calendar.
Output: A number representing elapsed business days.
Example: Start Date = Ticket Create Date, End Date = First Response Date. The action outputs elapsed business days for SLA reporting.
Multi-Country Calculate
Counts working days between two dates using the country selected manually for that workflow action. It shares the Free tier's combined 3,000-calculation monthly cap.
Inputs: Start Date, End Date, and a manually selected country.
Output: A number representing elapsed business days for the selected country.
Example: Select Brazil for one workflow and Germany for another when each process needs a different holiday calendar.
Add / Subtract Business Days
Moves a date forward or backward by a number of working days.
Inputs: Reference date, number of business days, add or subtract direction, country holiday calendar.
Output: A resulting business-day date.
Example: Start with Today, add 5 business days, and write the result to a Follow-up Due Date property.
Check If Business Day
Tests whether a specific date falls on a working day.
Inputs: Date to evaluate and country holiday calendar.
Output: A yes or no result you can use in branches.
Example: Check whether a requested send date is a business day before creating a handoff task.
Find Next / Previous Business Day
Snaps a date to the nearest valid working day.
Inputs: Reference date, next or previous direction, country holiday calendar.
Output: The next or previous business-day date.
Example: If a renewal reminder lands on a Sunday or holiday, move it to the next business day before creating the task.
How to save or use the result
Every action above calculates a value and returns it - it does not save anywhere by itself. That's a separate, one-time step in the same workflow, right after the action:
- Add the calculation action (e.g. Calculate Business Days) to your workflow, and map its inputs.
- Add a "Set property value" action immediately after it - this is a native HubSpot workflow action, not something NetworkDays adds.
- Set the property's value to the calculation action's output (use the token/insert-data picker in the property value field to select it), and choose which record property to write it to.
Now the result is a real HubSpot property - usable in reports, list filters, other workflow branches, or shown on the record. This is the same pattern for every action: Calculate Business Days → Set property value on a number property; Add/Subtract or Find Next/Previous → Set property value on a date property; Check If Business Day → branch directly on the output, or set it to a property first if you want it reportable.