Skip to main content

Workflows

Workflows allow you to compose integration flows from pre-defined actions (HubSpot, Jira, Google Workspace, and others), and the orchestration is then triggered by agents or directly by users. This section is currently in beta mode.

Where to find them​

  • In the left menu, click on Workflows (Beta).
  • A list of existing workflows will appear, along with search, pagination, and a button Create workflows. An empty list displays the text No results.

List of workflows – empty state

Creating a new workflow​

  1. Click on Create workflows.
  2. In the right panel, fill in the Name and Description – these are also used for searching.
  3. Drag actions from the left panel Connections onto the canvas (e.g., HubSpot, Jira, Google Calendar, Google Drive).
  4. Connect the nodes by dragging lines – the output of the previous action is the input of the next.
  5. In the node settings, fill in the parameters (record IDs, emails, calendars, projects, etc.).
  6. Save by clicking on Save workflows.
  7. Zoom controls are at the bottom left, mini-map at the bottom right.

Empty canvas with the first trigger: Empty canvas with webhook

Adding a node from the catalog: Node selection (Triggers/Tools/Agents)

Edge settings (Conditions)​

You can open Edge settings on the lines between nodes. In this section, you set conditions that determine when the workflow should take a specific branch.

Configurable items:

  • Label for naming the branch.
  • One or more rules in the Condition section.
  • Operator (e.g., Text equals) and comparison value.
  • Add rule to add another condition.

Edge settings - conditions

Typical actions and examples​

  • HubSpot: GetDealById, GetContactById – reading a deal/contact before passing it to other systems.
  • Jira: GetUserAsync, AssignTicketAsync, CreateTicketAsync – enriching a contact or creating a ticket.
  • Google Calendar: CreateEventAsync – creating a meeting after successful data enrichment.
  • Google Drive: ListFilesAsync, ReadFileAsync – working with documents.
  • LLM / Webhook: calling a model or webhook to supplement logic, validation, or notification. You can find the procedure for creating a webhook on the Webhooks page.

Best practices​

  • Input validation: verify IDs, emails, and required parameters before connecting additional nodes.
  • API errors: account for errors from integration services (timeout, rate limit) and add a fallback.
  • Naming: name nodes according to their function (e.g., “Find HubSpot Contact”, “Create Jira Ticket”).
  • Security: work only with access rights that are necessary for the given workflow; keep sensitive values in a vault/secrets.

Editing and management​

  • In the list of workflows, search for the name/keyword and open the item.
  • You can edit, save, and rerun the workflow – changes will take effect in new runs.
  • Recommended: after significant changes, test the flow on non-production data (test deals/tickets/calendar).

Change history​

In the right panel History, you can view previous changes to the workflow (added/moved nodes, initial state) and revert to earlier versions.

Workflow history

Sharing workflow​

In the Access / Sharing section, you can set:

  • Visibility (Private / Shared),
  • Organization Access (e.g., Can Use),
  • Team Access to add specific teams.

This determines who can use or manage the workflow within the organization.

Workflow sharing access

Common scenarios​

  • Sync HubSpot → Jira → Calendar: obtaining a deal and contact, finding a user in Jira, creating a ticket and meeting.
  • Incident intake: creating a ticket, attaching files from Drive, and notifying via webhook/LLM.
  • Onboarding: creating a user in internal systems, adding to groups, and scheduling an introductory meeting.

Sample workflows: Sample workflows with HubSpot and Outlook