Workflows
Use this capability family for HubSpot workflows, workflow folders, enrollment, actions, and enabled state.
At A Glance
Section titled “At A Glance”| Supported actions | Bridge or hybrid actions | Access used |
|---|---|---|
| 8 | 4 | automation, crm.objects.custom.read |
Common Requests
Section titled “Common Requests”- Create a disabled workflow draft for follow-up tasks after a form submission.
- Update enrollment criteria or workflow actions after confirming the target workflow.
- Move workflows into a folder for organization.
Review Checklist
Section titled “Review Checklist”- Confirm the target portal is correct.
- Check the operation names, target assets, and required access.
- Resolve missing-permission warnings before execution.
- Review operation results after execution.
- Keep new or changed workflows disabled until triggers, actions, and enrollment rules are reviewed.
- Inspect suppression lists, re-enrollment, and workflow folder changes before activation.
Supported Actions
Section titled “Supported Actions”| Action ID | What it does | Execution | Required access | Main details |
|---|---|---|---|---|
create_workflow | Create a HubSpot workflow with actions and enrollment criteria. | Does not require the bridge extension | automation | name, workflow type, object type ID, actions |
create_workflow_folder | Create a workflow folder. | Requires the Daeda Bridge extension | No additional connected-portal scope | name |
delete_workflow | Delete a HubSpot workflow (irreversible). | Does not require the bridge extension | automation | workflow ID |
delete_workflow_folder | Delete a workflow folder. | Requires the Daeda Bridge extension | No additional connected-portal scope | folder ID |
move_workflows_to_folder | Move workflows to a folder. | Requires the Daeda Bridge extension | No additional connected-portal scope | workflow IDs |
set_workflow_enabled | Enable or disable a HubSpot workflow. | Does not require the bridge extension | automation | workflow ID, enabled |
update_workflow | Update an existing HubSpot workflow (name, actions, enrollment criteria). | Does not require the bridge extension | automation, crm.objects.custom.read | workflow ID |
update_workflow_folder | Update a workflow folder. | Requires the Daeda Bridge extension | No additional connected-portal scope | folder ID, name |
Action Details
Section titled “Action Details”Create a HubSpot workflow with actions and enrollment criteria
Section titled “Create a HubSpot workflow with actions and enrollment criteria”Create a HubSpot workflow with actions and enrollment criteria. The draft records name, workflow type, object type ID, actions for review.
- Action ID:
create_workflow - Change type: Create
- Execution: Does not require the bridge extension
- Required access: automation
- Main details reviewed in the plan: name, workflow type, object type ID, actions
- Planning notes:
- Prefer enrollment_trigger for supported EVENT_TRIGGER_SHORTCUT rows, especially property-change events, instead of hand-authoring raw UNIFIED_EVENTS branches.
Create a workflow folder
Section titled “Create a workflow folder”Create a workflow folder. The draft records name for review.
- Action ID:
create_workflow_folder - Change type: Create
- Execution: Requires the Daeda Bridge extension
- Required access: No additional connected-portal scope
- Main details reviewed in the plan: name
Delete a HubSpot workflow (irreversible)
Section titled “Delete a HubSpot workflow (irreversible)”Delete a HubSpot workflow (irreversible). The draft records workflow ID for review.
- Action ID:
delete_workflow - Change type: Delete
- Execution: Does not require the bridge extension
- Required access: automation
- Main details reviewed in the plan: workflow ID
Delete a workflow folder
Section titled “Delete a workflow folder”Delete a workflow folder. The draft records folder ID for review.
- Action ID:
delete_workflow_folder - Change type: Delete
- Execution: Requires the Daeda Bridge extension
- Required access: No additional connected-portal scope
- Main details reviewed in the plan: folder ID
Move workflows to a folder
Section titled “Move workflows to a folder”Move workflows to a folder. The draft records workflow IDs for review.
- Action ID:
move_workflows_to_folder - Change type: Update
- Execution: Requires the Daeda Bridge extension
- Required access: No additional connected-portal scope
- Main details reviewed in the plan: workflow IDs
Enable or disable a HubSpot workflow
Section titled “Enable or disable a HubSpot workflow”Enable or disable a HubSpot workflow. The draft records workflow ID, enabled for review.
- Action ID:
set_workflow_enabled - Change type: Update
- Execution: Does not require the bridge extension
- Required access: automation
- Main details reviewed in the plan: workflow ID, enabled
Update an existing HubSpot workflow (name, actions, enrollment criteria)
Section titled “Update an existing HubSpot workflow (name, actions, enrollment criteria)”Update an existing HubSpot workflow (name, actions, enrollment criteria). The draft records workflow ID for review.
- Action ID:
update_workflow - Change type: Update
- Execution: Does not require the bridge extension
- Required access: automation, crm.objects.custom.read
- Main details reviewed in the plan: workflow ID
- Planning notes:
- Prefer enrollment_trigger for supported EVENT_TRIGGER_SHORTCUT rows, especially property-change events, instead of hand-authoring raw UNIFIED_EVENTS branches.
Update a workflow folder
Section titled “Update a workflow folder”Update a workflow folder. The draft records folder ID, name for review.
- Action ID:
update_workflow_folder - Change type: Update
- Execution: Requires the Daeda Bridge extension
- Required access: No additional connected-portal scope
- Main details reviewed in the plan: folder ID, name