Action buttons allow you to execute one or more actions on leads with a single click. They appear in various places throughout Hubhus and can perform tasks like sending emails, updating statuses, making phone calls to external systems, or triggering custom workflows.

What are action buttons

Action buttons are customizable buttons that execute one or more actions when clicked. They enable you to:

• Execute multiple actions with one click - Send email and update status simultaneously
• Standardize workflows - Ensure consistent processes across your team
• Save time - Automate repetitive manual tasks
• Integrate with external systems - Trigger actions in third-party applications
• Control when actions are available - Show buttons only when specific conditions are met

Where action buttons appear

Action buttons can be configured to appear in multiple locations:

Profile page: On the lead detail page where you view full lead information.

Table: In the leads table view as a column button.

Table context menu: In the right-click context menu when selecting leads in table view.

Summary card: In the compact lead summary card view.

In calendar events: As large buttons within calendar event details.

You can select multiple appearances for each button.

Creating an action button

Step 1: Access action buttons

Go to: Campaign settings → Action buttons

Click + New action button

Step 2: Configure basic settings

Name: Enter a descriptive internal name for the button (e.g., "Send booking invitation", "Escalate to manager").

Icon: Select an icon for the button. See available icons link in the interface.

Type: Choose button color:

• Blue
• Green
• Red
• Orange
• Gray

Title (on hover): Enter the tooltip text shown when hovering over the button.

Appearances: Select where the button should appear (Profile page, Table, Table context menu, Summary card, In calendar events).

Step 3: Add actions

Click + Add action to add actions that execute when the button is clicked.

You can add multiple actions that execute in sequence.

Available actions:

• Send email - Send a specific email template
• Send SMS - Send an SMS message
• Set status - Change the lead status
• Set reason - Update the reason field
• Assign user to lead - Assign lead to a specific user
• Set assigned person - Change the assigned person
• Set follow-up date - Create or update follow-up date
• Set field value - Update a text or number field
• Set select value - Update a dropdown/select field
• Submit HTTP request - Send data to external API
• Go to URL or page - Open URL or navigate to Hubhus page
• Fill out checklist - Complete checklist items
• Upload file - Attach a file to the lead
• Add comment - Add an internal comment
• Close lead - Close/archive the lead

Step 4: Configure each action

Each action type has specific configuration options.

Example: Send email

1. Select "Send email" from action dropdown
2. Choose email template
3. Optionally set status after sending

Example: Go to URL or page

1. Select "Go to URL or page"
2. Enter URL (can include placeholders)
3. Example: http://localhost:8733/CallNumber?Number=%lead_phone%
4. Choose whether to open in new tab

Example: Set field value

1. Select "Set field value"
2. Choose which field to update
3. Enter the new value (can include placeholders)

For email template creation, see How do I create and customize email templates?

Step 5: Configure requirements (optional)

Click Requirements button to set conditions for when the button is active.

Requirement options:

Always active: Button is always available for all leads.

Conditionally active: Button only appears when specific conditions are met.

Condition categories:

• Hubhus ID requirements - Filter by lead ID
• Created requirements - Filter by origin, creation date
• Follow-up requirement - Has/doesn't have follow-up
• Status requirements - Current status, status history
• Reason - Current reason value
• Assigned person requirements - Who lead is assigned to
• Field value requirements - Specific fields filled/empty, files uploaded
• Select field requirements - Dropdown field values
• Subscription and blacklist requirements - Email subscription status
• Calendar requirements - Has calendar events or meetings
• Custom placeholder requirements - Advanced conditional logic using placeholders

Example requirement: Only show "Call customer" button if lead has a phone number filled in.

Configuration:

• Set to "Conditionally active"
• Field value requirements → Must have checked or filled → Select "Phone" field

Step 6: Configure confirmation and success messages

Show confirmation dialog:

• Auto: Show if action could cause data loss
• Always: Always ask for confirmation
• Never: Execute immediately without confirmation

Confirmation dialog settings:

• Confirmation dialog title (e.g., "Default (name)")
• Confirmation dialog content (e.g., "Are you sure?")

Show success message:

• Auto: Show if appropriate
• Always: Always show success message
• Never: No success message

Success message settings:

• Success message title (e.g., "Thank you")
• Success message body (e.g., "Your click has been registered")

Step 7: Save the button

Click Save to create the action button.

The button will now appear in the configured locations for leads that meet the requirements.

Available actions

Communication:

• Send email (with template selection)
• Send SMS

Lead management:

• Set status
• Set reason
• Close lead
• Add comment

Assignment:

• Assign user to lead
• Set assigned person

Data updates:

• Set field value
• Set select value
• Set follow-up date
• Upload file
• Fill out checklist

External integrations:

• Submit HTTP request
• Go to URL or page

Button requirements

Requirements control when action buttons are visible and clickable.

Common requirement patterns:

Show button only for specific status:

• Status requirements → Status → Select specific status

Show button only if field is filled:

• Field value requirements → Must have checked or filled → Select field

Show button only for assigned leads:

• Assigned person requirements → Assigned to → Select user or "Anyone"

Show button based on custom logic:

• Custom placeholder requirements → Enter conditional expression
• Example: @if(%lead_postal_code% == 2000){1}@endif

Hide button if already triggered:

• Automation history requirements → Must not have been triggered by any of → Select related automation

Button appearance settings

Appearances controls where buttons are visible:

Profile page: Appears on lead detail page. Best for actions requiring full lead context.

Table: Appears as button column in leads table. Best for quick bulk actions.

Table context menu: Appears in right-click menu. Good for secondary actions.

Summary card: Appears in compact lead cards. Best for frequently used actions.

In calendar events (large button): Appears prominently in calendar event details. Best for event-related actions.

Best practice: Select multiple appearances for frequently used buttons, fewer for specialized actions.

Using placeholders in actions

Many action types support Hubhus placeholders for dynamic values.

Common placeholders:

Lead information:

• %lead_name% - Lead's full name
• %lead_firstname% - Lead's first name
• %lead_email% - Lead's email address
• %lead_phone% - Lead's phone number
• %lead_company% - Lead's company name

User information:

• %user_name% - Current user's name
• %user_email% - Current user's email
• %assigned_person_name% - Assigned person's name
• %assigned_person_email% - Assigned person's email

Custom fields:

• %custom_field_name% - Value of any custom field

Where to use placeholders:

In URLs:

http://localhost:8733/CallNumber?Number=%lead_phone%

In field values:

Called by %user_name% at %timestamp%

In HTTP requests: Send lead data to external APIs using placeholders in the request body.

Common use cases

Send booking invitation:

1. Action: Send email (booking invitation template)
2. Action: Set status to "Booking invitation sent"
3. Appearances: Profile page, Table
4. Requirements: Email field must be filled

Call customer via phone system:

1. Action: Go to URL http://localhost:8733/CallNumber?Number=%lead_phone%
2. Appearances: Profile page, Summary card
3. Requirements: Phone field must be filled

Escalate to manager:

1. Action: Set assigned person (Manager)
2. Action: Set status to "Escalated"
3. Action: Add comment "Escalated by %user_name%"
4. Appearances: Profile page
5. Requirements: Status is "Open" or "In progress"

Quick close won:

1. Action: Set status to "Won"
2. Action: Send email (thank you template)
3. Action: Close lead
4. Confirmation: Always ask
5. Appearances: Profile page, Summary card

Schedule follow-up:

1. Action: Set follow-up date (7 days from now)
2. Action: Set status to "Follow-up scheduled"
3. Appearances: Profile page, Table

Action buttons vs automation

Use action buttons when:

• You need manual control over when actions execute
• Actions should only happen after human review
• Different actions needed for different situations
• Team members need flexibility in workflow

Use automation when:

• Actions should happen automatically based on triggers
• Consistent process required for all leads
• Actions should execute without human intervention
• Time-based or event-based triggers needed

For automation setup, see How do I set up automated email flows?

Combine both: Use action buttons for manual steps and automation for automatic follow-ups. For example: Action button sends initial email, automation sends follow-up 3 days later if no response.

Summary

Action buttons in Hubhus execute one or more actions on leads with a single click and are configured in Campaign settings → Action buttons by setting name, icon, type, and appearances (Profile page, Table, Table context menu, Summary card, In calendar events). Add multiple actions that execute in sequence including send email, send SMS, set status, set field values, assign person, go to URL, submit HTTP requests, and more. Configure requirements to control when buttons are active using conditions based on status, field values, assigned person, custom placeholders, and other criteria. Use placeholders like %lead_phone%, %lead_email%, %user_name% in URLs, field values, and HTTP requests for dynamic content. Configure confirmation dialogs for destructive actions and success messages for user feedback. Action buttons provide manual control over workflows while automation handles automatic triggers, and combining both creates flexible, efficient processes. Follow best practices including clear naming, logical action sequencing, appropriate requirements, and thorough testing before deployment.