CRM conditions
Use relevant CRM states as starting points for follow-up rules. Make it clear what triggers the rule and why it exists.
Workflows / Conditions, tasks and notifications
Create tasks and notifications from suitable CRM conditions, making recurring follow-up visible to the team.
PRODUCT VIEW
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.
Identify the CRM condition that needs regular follow-up. Describe the concrete work and outcome the rule should support.
Arrange the work to create or information to pass to its owner when the condition occurs. Limit the rule to the actual need.
Check that generated steps fit real team work. Keep different actions, such as sending messages or starting campaigns, distinct from this rule.
DETAILED FEATURE GUIDES
FROM NEED TO OUTCOME
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.
Connect a recurring need to an explicit condition and owner, keeping what the automation does understandable to the team.
STEP BY STEP
Identify the CRM condition that needs regular follow-up. Describe the concrete work and outcome the rule should support.
Arrange the work to create or information to pass to its owner when the condition occurs. Limit the rule to the actual need.
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
Use relevant CRM states as starting points for follow-up rules. Make it clear what triggers the rule and why it exists.
Create a next action for an owner under suitable conditions. The output should clarify who follows up on what.
Make a relevant development visible through an in-app notification. Treat informing the team and messaging a customer as different purposes.
Use Sequences for individual Gmail conversations and Workflows for CRM tasks and notifications. Each tool has a clear role in its own workflow.
Use workflows within workspace and action permissions. Configuring a rule does not automatically enable closed modules or provider permissions.
IN EVERYDAY WORK
Arrange the condition and task step rather than handling the same reminder separately every time.
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
Workflows and Sequences for eligible Gmail conversations are included in Professional and Business. Conditions, owners and required connections are reviewed during setup.
YOUR QUESTIONS
No. Workflows creates tasks and notifications from CRM conditions. Sequences follows eligible Gmail conversations. Bulk campaigns and other provider actions have separate scopes.
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.
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.
MODULES THAT WORK TOGETHER
Organize work in lists and Kanban views, keeping customer follow-up visible with an owner and date.
Use in-app notifications for daily work, and connect authorized Gmail conversations with Professional and Business.
Review sales, customer relationships, support, operations and data quality through your existing records.