// Tasks
One concrete action per risk
Sighub creates a single follow-up task per risk, assigns it to the right person, and resolves it automatically when the risk goes away.
When tasks are created
Tasks are created only after task automation has been activated. The first scan does not create tasks.
Tasks are created for high and critical risks only. Medium risks remain visible in the Sighub card without generating HubSpot tasks.
Task subjects
- Renewal:
Sighub: Review renewal risk before contract end - Engagement:
Sighub: Follow up on engagement risk
The body includes a short explanation, up to three evidence lines, and a link to the Company record. Tasks are associated to the Company in HubSpot.
Due dates
- Renewal: due today if overdue or within 7 days; in 1 day if within 14 days; in 3 days otherwise.
- Engagement: due today if critical; in 1 day if high; in 3 days otherwise.
How tasks are assigned
Assignment follows the owner routing chosen during setup:
- Company owner: the company's
hubspot_owner_id. - Specific user: one selected HubSpot owner for all companies.
If the specific user is missing at runtime, Sighub falls back to the company owner. If no owner is available at all, the task is created without an assignee.
How tasks are resolved
Sighub stores one risk snapshot per company. On each scan:
- If the same risk persists and the existing task is still open, it stays.
- If the risk state changes, the previous task is completed and a new one is created (if the new state is task-eligible).
- If risk resolves, drops to medium, or becomes insufficient data, the previous task is completed with no replacement.
Sighub only resolves tasks whose subject starts with Sighub:.
Edge cases
- User completes a Sighub task manually: if the same high risk still exists on the next scan, Sighub may create a new task. Completing a task does not clear the underlying risk.
- User deletes a Sighub task: if the same risk state remains unchanged, Sighub currently does not recreate the task. This is a known limitation.