Workflows / Conditions, tasks and notifications

CRM workflows: task and notification rules

Create tasks and notifications from suitable CRM conditions, making recurring follow-up visible to the team.

PRODUCT VIEW

See how it works.

Not every repeated action requires a large automation project. A task created at the right time or a notification to its owner may be the step that keeps work from being forgotten. Hubz Workflows connects CRM conditions to task and notification steps. Gmail conversation follow-up remains a separate Sequences workflow with its own usage conditions.

Hubz.Workspace / WorkflowsDK
EXPLORE THE PRODUCT

Workflows

Sample view
1START

Choose the recurring situation

Identify the CRM condition that needs regular follow-up. Describe the concrete work and outcome the rule should support.

2CONDITION / PREPARATION

Define a task or notification

Arrange the work to create or information to pass to its owner when the condition occurs. Limit the rule to the actual need.

3NEXT STEP

Review the workflow

Check that generated steps fit real team work. Keep different actions, such as sending messages or starting campaigns, distinct from this rule.

01Choose the recurring situation
02Define a task or notification
03Review the workflow
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

FROM NEED TO OUTCOME

Where this helps.

Similar records can require the same manual reminders repeatedly. As the team grows, knowing who owns a rule and when it should apply can become personal knowledge rather than shared practice.

WHAT YOU CAN WORK TOWARDS

Connect a recurring need to an explicit condition and owner, keeping what the automation does understandable to the team.

STEP BY STEP

How to use it.

  1. 01

    Choose the recurring situation

    Identify the CRM condition that needs regular follow-up. Describe the concrete work and outcome the rule should support.

  2. 02

    Define a task or notification

    Arrange the work to create or information to pass to its owner when the condition occurs. Limit the rule to the actual need.

  3. 03

    Review the workflow

    Check that generated steps fit real team work. Keep different actions, such as sending messages or starting campaigns, distinct from this rule.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
Workflows
1Choose the recurring situation→Review

CRM conditions

Use relevant CRM states as starting points for follow-up rules. Make it clear what triggers the rule and why it exists.

FOCUS 02▤
Workflows
2Define a task or notification→Review

Task creation

Create a next action for an owner under suitable conditions. The output should clarify who follows up on what.

FOCUS 03↗
Workflows
3Review the workflow→Review

Notification steps

Make a relevant development visible through an in-app notification. Treat informing the team and messaging a customer as different purposes.

FOCUS 04◇
Workflows
4Choose the recurring situation→Review

Working alongside conversation follow-up

Use Sequences for individual Gmail conversations and Workflows for CRM tasks and notifications. Each tool has a clear role in its own workflow.

FOCUS 05⌁
Workflows
5Define a task or notification→Review

Existing access controls

Use workflows within workspace and action permissions. Configuring a rule does not automatically enable closed modules or provider permissions.

IN EVERYDAY WORK

What it looks like in practice.

Sales operations

A record reaching a particular CRM state needs a follow-up task for its representative.

Arrange the condition and task step rather than handling the same reminder separately every time.

Team manager

An owner needs to notice a development, but no direct customer message is required.

Notify the team while leaving the customer-communication decision with the relevant person.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

Workflows and Sequences for eligible Gmail conversations are included in Professional and Business. Conditions, owners and required connections are reviewed during setup.

  • Current Workflows create tasks and notifications from conditions; they do not automatically send bulk email or WhatsApp campaigns.
  • No unimplemented commercial workflow quota or unlimited-use promise is made.
Compare plans

YOUR QUESTIONS

About this feature.

01Is this multichannel marketing automation?

No. Workflows creates tasks and notifications from CRM conditions. Sequences follows eligible Gmail conversations. Bulk campaigns and other provider actions have separate scopes.

02What must we define before starting?

Identify the recurring situation, the action needed when it occurs and its owner. Starting with a small number of explicit needs helps the team understand the rule.

03Does configuring automation change access permissions?

No. Workspace, module and action permissions still apply. A rule does not connect a provider account or grant new communication authority on behalf of a user.