New · 31 AugSimulate a record before it existsRead the release notes

DOCUMENTATION · v4.0

Documentation

Everything you need to know about using Entflow to map, audit, and manage your HubSpot workflows. Looking for what shipped recently? See the release notes for the latest changes, including new features that may need an in-app reconnect to enable.

Product walkthrough

LIVE · YOUTUBEvideo · watch on YouTube

A guided tour of Entflow: see how to connect HubSpot, map your workflows, and run your first audit.

🔒youtu.be/LTqDFaUR5lw

Getting started

Connect HubSpot, sync your portal, understand the plan limits. Most teams are productive within ten minutes.

Connecting HubSpot

Connect HubSpot from the landing page or the connect page. Entflow reads your workflow configurations, property definitions, pipeline and stage info, and email and list metadata to build your maps and audits. It never modifies or deletes your existing workflows or CRM records. The only time Entflow writes to HubSpot is the duplicate feature, which creates new draft workflows in a target portal you choose.

After authorising, Entflow begins syncing automatically. You'll see a real-time progress bar. Small portals (under 50 workflows) typically sync in 15 to 30 seconds. Large portals (200+ workflows) take 2 to 3 minutes.

Syncing your portal

Each sync runs a full diff against the previous state - new and modified workflows are detected and recorded in the changelog.

Every plan - and the 14-day trial - includes unlimited manual syncs via the Sync button in the top bar. Pro, Unlimited, Enterprise, and all agency plans add automatic background syncing on a configurable interval.

If your trial ends before you pick a plan, syncing pauses: the Sync button greys out and your data stays frozen at the last sync, still fully visible in view-only mode. Picking a plan resumes syncing immediately - see Plans and limits below.

Plans and limits

Entflow has two plan ladders: individual plans (per portal) and agency plans (account-level, covering multiple portals).

Individual plans

Every portal you connect starts with a 14-day free trial of Pro - no credit card required. The trial carries Pro's full feature set with trial-sized AI allowances: 25 AI analyses and 3 audit reports during the trial. Pick a plan whenever you're ready - during the trial or after it ends. Subscribing during the trial starts billing that day and ends the trial.

If the trial ends before you choose, the portal switches to view-only mode: everything already synced stays visible (map, workflows, cleanup, past audit reports) and nothing is deleted - but syncing, AI analysis, new audits, exports, and workflow duplication pause until you pick a plan. Upgrading lifts the freeze instantly.

Starter ($9/mo) - 50 workflows, dependency map, conflict detection, health scores, changelog, unlimited manual sync, workflow tagging, PNG/CSV export, 25 AI analyses/mo, 3 audit reports/mo, 2 workflow copies/mo.

Growth ($19/mo) - 100 workflows, everything in Starter, property conflict detail, canvas tools (sections and sticky notes), 75 AI analyses/mo, 10 audit reports/mo, 2 workflow copies/mo.

Pro ($29/mo) - 300 workflows, everything in Growth, full canvas toolkit, SVG/PDF export, auto-sync, 200 AI analyses/mo, 25 audit reports/mo, 2 workflow copies/mo.

Unlimited ($99/mo) - Unlimited workflows, everything in Pro, unlimited workflow copies + bulk duplication (up to 100 workflows per job), 200 AI analyses/mo, 25 audit reports/mo, priority support.

Enterprise - Unlimited workflows, everything in Pro, unlimited AI analyses + audits, unlimited workflow copies + bulk, dedicated support. Contact us for pricing. (White-labelled audit exports are an agency-plan feature.)

Agency plans (account-level, cover all your connected portals; all tiers include unlimited workflow copies + bulk duplication)

Agency Starter ($129/mo) - up to 3 portals, unlimited workflows per portal, all features including white-labelled audit exports, unlimited workflow copies + bulk, 150 AI analyses/mo pooled across portals, 15 audit reports/mo.

Agency Growth ($199/mo) - up to 10 portals, unlimited workflows per portal, all features, unlimited workflow copies + bulk, 600 AI analyses/mo pooled, 50 audit reports/mo.

Agency Pro ($399/mo) - up to 30 portals, unlimited workflows per portal, all features, unlimited workflow copies + bulk, 1,500 AI analyses/mo pooled, 90 audit reports/mo.

Agency Enterprise (custom) - for partner agencies that exceed Agency Pro's 30-portal / 1,500-AI / 90-audit envelope. Negotiated limits, dedicated support, custom SLA. Contact us for pricing.

Agency plans are billed at your Entflow account level, not per portal. They override each connected portal's individual tier while active. If you connect more portals than your agency plan's cap, you'll need to upgrade your agency plan before connecting another.

Individual plans are per portal. You can connect as many portals as you like, but each one has its own plan, its own trial and its own subscription, and its limits apply to that portal alone. Agency plans cover several portals on one bill.

Command palette (Ctrl+K)

Press Ctrl+K (Cmd+K on Mac) anywhere in the app to open the command palette. It searches across your portal - workflows, properties, emails, lists, even individual workflow actions - and it runs commands: jump to any page, or apply quick filters like "Filter to active workflows" (on Workflows and Analyst, which read them; anywhere else they open Workflows with the filter on).

Selecting a workflow opens its detail panel (on the map, the canvas also centers on its node). Selecting a property, email, or list takes you to the map with it highlighted. Your five most recently viewed workflows are offered the moment the palette opens, before you type anything.

Dashboard

The home screen for each portal - health at a glance, recent movement, and quick paths into the deeper tools.

Reading the dashboard

The dashboard opens on what needs you first. Its header names the portal, how many workflows it has and how many are inactive, and when it last synced; the Sync button sits in the same header.

Start here picks the one thing to do first. Sync problems come before anything else - a HubSpot connection that needs reconnecting, a failed sync, a portal that has not finished a sync - then high-priority cleanup issues, then conflicts to resolve. It carries the action that deals with it: a link to where you fix it, or a button that starts a sync.

Beside it, Portal grade shows the portal's letter grade and its score out of 100, how far the score moved at the last sync, and a sparkline of the score across the last four syncs once it has changed between them.

Destinations link to the Workflow Map, AI Analyst, Cleanup, Changelog, Compare and Simulate. Each shows one figure and what it counts: your workflows, how many are scored, the open issues in the cleanup queue, changes in the last 30 days and open conflicts. Simulate, which has no count of its own here, says what it shows instead.

Under Architecture, the workflow map groups your active workflows by object type into up to six clusters, with a connector wherever workflows on one object type touch another; Open map takes you to the full map. Beside it, Lowest scoring lists your five lowest-scoring workflows, each with its grade and either its most severe open cleanup issue or its score. Click one to open its detail panel.

Where things stand has four cards: Portal health (the average score across scored active workflows, after open issues are deducted), workflows scoring below 80, open conflicts by type, and changes recorded in the last 30 days. Below them, Top risks lists up to four open cleanup issues, highest priority first.

How activity is measured

Entflow records workflow activity at sync time: each sync samples HubSpot's enrollment data and notes which workflows have seen new enrollments since the previous sync. "No recent activity" badges are derived from those samples, so they're only as fresh as your last sync - if you sync rarely, a workflow can look idle simply because Entflow hasn't observed it recently.

Workflow map

The dependency map is the heart of Entflow. Every other feature reads from the same graph.

Reading the map

The workflow map shows every workflow in your portal as a node on an interactive canvas. Connections between nodes represent real dependencies - shared properties, cross-enrollment triggers, list memberships, and email audience overlaps.

Each node shows: workflow name, object type, action count, and health score badge. Click any node to open the Workflow Detail panel on the right.

Object types include the standard four (Contact, Deal, Company, Ticket) plus every custom object in your portal, each rendered with its real HubSpot label and a deterministic colour from a 10-shade palette so two custom objects in the same portal stay visually distinct. The Contact colour matches HubSpot's own brand contact-blue so the visual story carries across both apps.

Drag or scroll to pan; pinch, or scroll with Ctrl/⌘ held, to zoom. The minimap in the bottom-right shows your position. Use the filter sidebar to search by name, filter by status, object type, dependency type, tags, or property impact.

The Workflows and Hidden tabs

Two tabs sit at the top of the canvas:

Workflows - every active and inactive workflow on one map. Inactive workflows sit in a dashed band; use the Status filter in the sidebar to show only active or only inactive ones.
Hidden - workflows you've hidden from Entflow with Hide from Entflow (or the Del key). Click one and use Show in Entflow again in the detail panel to bring it back with the status it had.

Hiding a workflow in Entflow does not touch it in HubSpot. It takes it off your map and out of Entflow's counts and portal health. A workflow deleted in HubSpot itself is removed from Entflow on the next sync, so it doesn't appear in the Hidden tab.

Connection types

Each connection type has its own colour and dash:

Blue, dashed - Property dependency. Only a Set property step or a Copy property step records a write here; a Set marketing contact status step or a Create record step records none, so neither draws a line. One workflow's Set property step sets a property to a fixed value, and another workflow's enrollment criteria or one of its If/then branches checks for that value with "equals" or "is any of", or checks the property with "is known"; a fixed value draws no line to any other check, such as a range, "contains", "is none of" or "is unknown", or to a step that copies the property. A write with no fixed value - a Copy property step, or a Set property step whose value is copied, calculated or cleared (HubSpot stores a clear as an empty value) - draws a possible dependency to every workflow that reads the property in its enrollment criteria, an If/then branch or a Copy property step, or copies it from a fetched record in a Set property step (when the workflow's data sources say which object that record is). No line reaches a branch on one property's value or a Set property step that copies from another property of its own record, a Copy associated-object property step draws none either way, and two workflows that only write the same property are not joined.
Purple, long dashes - Cross-enrollment. One workflow enrolls records into another, or unenrolls them from it.
Teal, dotted - Shared list. One workflow adds records to a list, or removes them from it, and another workflow's enrollment criteria check membership of that list, whether they ask for members or for non-members. A list check inside a branch draws no line: every workflow is synced from HubSpot's v4 workflows API (/automation/v4/flows), and a v4 branch's list check is not counted.
Amber, dash-dot - Email. Both workflows send the same email. Every email line is marked as a warning, and a warning line is drawn in amber, a little thicker than the others.

The Key on the canvas lists every connection type. You can filter which connection types are visible using the Dependencies section of the filter sidebar.

Search and filtering

The filter sidebar on the left stacks these sections:

Search - filters the visible nodes by workflow name in real time. Clicking a result in the dropdown centers the canvas on that node and opens its detail panel.
Status - show only Active or Inactive workflows.
Object Type - filter by Contact, Deal, Company, or Ticket workflows, or by any individual custom object in your portal. Each custom object appears as its own filter row with its real HubSpot label (e.g. "Authorization", "Project") rather than collapsed under one "Custom" entry, so you can drill in to a single schema with one click.
Cleanup category - narrow the canvas to workflows flagged by a specific cleanup detector (broken references, loop risks, stale workflows, and so on) - the same categories the Cleanup page uses.
Users in workflows - filter to workflows that reference a specific HubSpot user - task assignees, internal email recipients, in-app notification targets, owner rotations, owner property writes. User names show as real names instead of numeric IDs (this requires the optional users scope; see Settings → HubSpot → Reconnect HubSpot if names appear as numbers).
Lists and Forms - filter to workflows that reference a specific HubSpot list or form.
Dependencies - filter by connection type (property dependency, cross-enrollment, list reference, email overlap).
Tags - filter by custom tags you've applied to workflows.
Property Impact - opens a flyout panel next to the sidebar: select any property to highlight every workflow that reads or writes it on the canvas. Inactive workflows that touch it are listed too, marked with a grey dot.

Undo and redo

The map supports undo and redo for node moves and hides.

Ctrl+Z - undo the last action (move or hide).
Ctrl+Y or Ctrl+Shift+Z - redo.
Del key - hide the selected workflow from Entflow (nothing changes in HubSpot; the toast offers Undo).

Node position changes are saved automatically to your layout.

Keyboard shortcuts

?
Open keyboard shortcuts reference
+ ** or **Ctrl or K
Open workflow search
Esc
Close panels, cancel tool, close search
F
Fit all workflows in view
H
Hand tool, where the map starts: drag to pan, click a workflow to open it
V** or **1
Select tool
S** or **2
Section
R** or **3
Rectangle shape
D** or **4
Diamond shape
O** or **5
Circle shape
C** or **6
Connector
N** or **7
Sticky note
T** or **8
Text
Shift + G
Toggle snap to grid

**G**, then a letter - Go to another tool (G then C opens Cleanup); the full list is under **?** on any page

Ctrl + Z
Undo
Ctrl + Y** + **Shift or Z
Redo
Ctrl + D
Duplicate selected element
Ctrl + C** + **Ctrl / V
Copy / Paste
Delete** or **Backspace
Delete selected element

Saved filter views

Apply any combination of filters in the sidebar (status, object type, dependency type, tags, properties) then click 'Save current filters' at the bottom of the sidebar to name and save the preset.

Saved views are stored locally in your browser. Click any saved view to instantly apply those filters. Hover to reveal the delete button.

Up to 10 saved views are stored per portal.

Scanning workflow rows

Every workflow in the analyst dashboard and the cleanup page carries a row of at-a-glance metadata designed to help you spot outliers without opening each workflow.

Capability badges - small icon chips under the workflow name showing what the workflow actually does:

  • Sends email - at least one marketing email action (HubSpot action type 0-4).
  • Writes N props - counts distinct properties the workflow sets.
  • N branches - single or multi-branch conditions.
  • Creates records - creates a deal or ticket as a step.
  • Enrolls into workflow - chains into another workflow.
  • Webhook / custom code - outbound webhook or custom code step.
  • Internal notification - in-app notification or internal email.
  • No recent activity - ACTIVE workflow with no enrollments observed in the last 90 days (amber / 💤).

Workflows table

Every workflow as a sortable, filterable table - the spreadsheet view of the same data the map draws.

Working in the table

The Workflows page (top navigation) lists every synced workflow as a row with its status, object type, health score, and created/edited/last-ran timestamps. Click a column header to sort; click a row to open the workflow's detail panel.

The filter sidebar carries the same sections as the map - search, status, object type, cleanup category, users, lists, forms, tags, and property impact - so a filter that answers a question on the map answers it here too. Filters live in the URL, which makes any filtered view shareable as a link, and filter combinations can be saved as named views.

Large portals paginate; sorting and filtering always apply to the full set, not just the visible page.

Multi-select and CSV export

Tick rows to build a selection - it survives paging, and "Select all matching" grabs the entire filtered set in one click. Export CSV downloads the full filtered view (not just the visible page), so you can slice first, export second, and hand a clean list to whoever asked.

Each row also carries a Duplicate button to copy that workflow into another portal - see Workflow Duplication.

Workflow detail panel

Click any node on the map to open the right-side detail panel. It surfaces seven cards - trigger, actions, health, dependencies, simulator, recent changes, and the per-workflow changelog.

Opening the detail panel

Click any workflow node on the canvas to open the Workflow Detail panel on the right side. The panel shows the workflow's full configuration as parsed from HubSpot's API.

The header shows the workflow name, status badge, object type, action count, and health score. Use the Open in HubSpot button to jump directly to the workflow editor in HubSpot.

Enrollment trigger

The Enrollment Trigger card shows how contacts enter the workflow. For event-based workflows (form submissions, page views, meeting bookings), Entflow shows the trigger type and the specific form or event. For filter-based workflows, it shows the property conditions that must be met for enrollment.

Re-enrollment and unenrollment settings are also shown here.

Actions

The Actions card shows every step in the workflow in order. Click any action to expand it and see the full configuration - email content, property values, delay durations, task details, and more.

Use "Expand all" to open every action at once. Actions that write properties are highlighted, as these are the most likely sources of conflicts with other workflows.

Health scores and AI analysis

Every workflow gets an A-F health score, calculated by Entflow's own rules when your portal syncs - no AI involved, included on every plan. This base score reflects the workflow's own structure: missing suppression on marketing-email sends, emails fired back-to-back with no delay, deep branch nesting without fallback paths, duplicate property writes, and property updates that could trigger a re-enrollment loop. Workflows designed to run straight through - property updates, task creation, internal notifications, data syncs - aren't penalised for having no goal or unenrollment criteria. That only counts against a marketing email sequence of two or more sends with no way for contacts to exit early (a goal, an unenrollment trigger, or an engagement-checking branch on opens/replies). Custom code steps are noted but barely move the score, since we can't statically analyse what the code does.

The "Run deep analysis" button sends the full workflow definition to the AI Analyst. Where the health score checks structure against fixed rules, the AI reads the workflow's logic for defects inside it - broken references, branches that can never run, a workflow that re-enrolls itself, required actions that are missing, contradictory property writes, and goals that contradict the trigger. Every issue is rated Critical or Warning and comes with a specific, HubSpot-native fix suggestion.

The grade you see on a workflow combines the base score with any open findings against it: each AI finding and each open cleanup issue subtracts from the score, with criticals weighing more than warnings. To raise a grade, open the workflow in the Analyst - the findings list is the explanation, and every finding carries a specific fix. Re-run the analysis after a change and the grade refreshes. If a finding doesn't apply to how you built the workflow, dismiss it instead: dismissed findings stop counting against the grade right away, with no re-run needed.

Monthly deep-analysis allowances: 25 on Starter, 75 on Growth, and 200 on Pro and Unlimited, with pooled allowances on agency plans. The 14-day trial includes 25.

Dependencies

The Dependencies card lists every workflow connected to the current one, grouped by connection type. Click any connected workflow name to jump directly to it - the canvas will center on that node and the detail panel will update instantly.

What if I deactivate this?

The Impact Simulator panel has two tabs: Impact and Unused properties.

Impact shows what would break if you turned off this workflow. It checks which other active workflows depend on it - through cross-enrollment, shared lists, or property chains - and lists every workflow that would be affected. It states what it found rather than calling the change safe or unsafe.

Unused properties lists every CRM property in your portal that no workflow currently reads or writes. Covers Contacts, Companies, Deals, Tickets, and each custom object schema, with per-object counts and a search box. Useful for spotting dormant fields that look important but aren't actually wired into any automation. Each row's pill shows the actual object label (e.g. "Authorization", "Project") so you can tell two custom objects apart at a glance.

Recent changes

The Recent Changes card shows the last 10 changelog entries for this specific workflow - actions added or removed, enrollment criteria changes, status changes, and more. Click "View full diff" to see the before/after state of any change.

Event-based enrollment triggers

Workflows that enroll on a behavioural event carry an event type ID rather than a name - HubSpot's flow payload gives Entflow the ID and nothing else. Entflow resolves those IDs to their real names through HubSpot's event-definitions API and caches them per portal, so the trigger reads "Has completed: Funding has been completed" instead of "Event 4-5076614".

Resolution needs one optional permission, Read event definitions, which HubSpot presents as a separate checkbox when you connect or reconnect. Without it the trigger shows the raw ID and a note explaining why, and nothing else about the workflow is affected. If your portal connected before this shipped, the notification bell will offer a reconnect link.

Form submission events (event type ID 4-1639801) are named without the permission, because that ID is the same in every portal. Every other event ID is portal-specific.

An ID that resolves to nothing even with the permission granted is genuinely absent from HubSpot - usually an event definition that was deleted after the workflow was built. Entflow shows the raw ID rather than inventing a name for it.

Comments and review

Leave comments on a workflow, tag a teammate, and assign workflows to yourself for review. Everything here is per-portal - only people with access to that portal can see or be tagged.

Commenting on a workflow

Open any workflow and switch to the Comments tab in the detail panel. Comments are attached to the workflow, not to a sync, so they survive every sync and stay in place as the workflow changes.

Each comment records who wrote it and when. Editing your own comment stamps it as edited rather than rewriting history silently. Comments have a 5,000-character limit.

Editing and deleting are author-only - nobody can rewrite your words. Marking a comment as read is open to any portal member, because whether a thread is finished is a team judgement rather than an authorship one.

Tagging teammates with @

Type @ in the comment box and a picker appears listing the people who have access to this portal. Pick a name and it is inserted as a tag.

Only portal members can be tagged. The tag is re-checked against real membership on the server when the comment is saved, so a tag for someone outside the portal is dropped rather than notified. A single comment notifies at most 10 people.

Everyone tagged gets a notification in the bell menu and an email. The email links straight to the map with the workflow open on the comment, so the recipient lands on the thing being discussed rather than on a dashboard.

Editing a comment does not re-notify anyone. Fixing a typo in a comment that tagged five people will not send five more emails. Tagging someone new in an edit does notify that person, and only that person.

Finding open comments

A workflow with unread comments wears a small amber badge on the corner of its node on the map, and the same badge appears on its Comments tab. It counts comments that nobody has marked as read yet, so it clears when the team is done rather than when the comment is merely seen.

The badge is the reason comments are useful during an audit: you can leave questions across a portal on Monday and see at a glance on Friday which ones are still open.

Assigning workflows to yourself

Assign to me assigns workflows to you, so a team auditing the same portal does not review the same workflow twice. Select rows in the Workflows table and choose Assign to me in the bar that appears; the confirmation offers Undo.

Anyone with portal access can assign. An assignment is a coordination signal, not a lock: it never prevents anyone from opening, editing, or acting on the workflow.

Workflow Compare

Pick any two workflows. Matched columns. Colour-coded diff. Deep-link URL for sharing.

Comparing two workflows

Select any two workflows using the search dropdowns at the top of the Compare page. Entflow fetches their full details - enrollment triggers, filter conditions, and every action - and renders them side by side.

Enrollment criteria are decoded into plain English. Filter conditions show the property name (not the internal ID) and the operator.

Any active conflicts between the two workflows are shown automatically below the headers.

Above the two workflows, a banner names the strongest relationship between them and says why. Compare looks for a resemblance only between two workflows that each have a stored trigger and at least one step, with a step that does something (not only delays and branches) as far as its steps can be read, and no data source it cannot read; for any other pair the banner names no resemblance. When either workflow's steps cannot be read in order (more than one first step, a step reached only round a loop, or a step pointing to one that does not exist), the banner says so, and that the look-alike check could not run; Where to start counts such workflows, and those holding a setting Compare does not read, under the families. When two such workflows on the same object have the same stored trigger and actions, it says so, and that settings HubSpot holds that are not synced may still differ. When two such workflows on the same object store the same trigger, built from filters or events, and are not identical, look-alikes or a pair it cannot judge, it says the same records qualify for both, and that suppression lists, which are not synced, may still keep different records out. When they are look-alikes (on the same object, with the same steps in the same layout, writing the same properties, and differing only in values, their trigger's filters or events, or re-enrollment), it lists each place they differ instead of a score. A pair it cannot judge says why.

With nothing picked, Where to start lists the open conflicts first, as the pairs of workflows they are between, then the workflows most tangled up with the rest of the portal, then look-alike families, the weakest reason to compare two. Each family says what its workflows share and what differs. Workflows with the same stored trigger and actions show as one row, and the pairs Compare could not judge are counted after the families.

Click 'Open in HubSpot' next to either workflow to jump directly to the workflow editor in HubSpot.

Compare is accessible from Cleanup (a look-alike question's Compare), from the Conflicts tab of the workflow detail panel, and directly at /compare?portal=YOUR_PORTAL_ID&a=WORKFLOW_A_ID&b=WORKFLOW_B_ID.

When to use Compare

Before merging workflows - compare two look-alike workflows to see exactly where they differ before consolidating them.

After a clone - if a workflow was cloned from another, compare them side-by-side to spot where the copy has diverged.

Debugging - if two workflows are creating competing outcomes, compare their enrollment triggers and actions to find the conflict.

Handoffs - compare a newly rebuilt workflow against the original to verify nothing was lost.

Workflow Duplication

Duplicate workflows between portals with full control over how properties, lists, forms, and marketing emails map across.

How duplication works

Workflow duplication copies a workflow from one connected portal to another. Entflow parses the source workflow, finds the portal-specific references it carries - properties, lists, forms, marketing emails, users and enrolled workflows - and walks you through mapping each one onto its equivalent in the target portal before anything is created.

The copy lands in the target portal as a draft workflow, never live, and the source is never modified. Review the draft in HubSpot and turn it on when you're happy.

Start a copy from the Duplicate button on any row of the Workflows table, from a workflow's detail panel, or from the map's right-click menu.

Mapping email actions

Every Send Email step in the source workflow becomes a mapping row, the same as a property or a list. Pick the equivalent marketing email in the target portal and Entflow rewrites the step to point at it.

Email IDs are portal-specific, so an unmapped send would land pointing at an email that does not exist in the target. Entflow will not mark a copy Ready until every reference is resolved, including the emails - so a workflow that sends email needs a decision on each send before it can run.

Your options per send are two: map it to an existing email in the target portal, or skip it. Skipping removes the Send Email step from the copy rather than leaving it broken.

Entflow suggests a match by name where one exists, but the suggestion is deliberately conservative - two portals often carry similar email names for genuinely different sends, so confirm each one rather than accepting on sight.

Dry runs

A dry run executes the whole copy pipeline without writing anything to HubSpot - it shows exactly what would be created and which references still need mapping. Dry runs are free on every plan and never count toward your monthly copy allowance. Use one to de-risk a copy before committing.

Bulk duplication

On Unlimited, Enterprise, and agency plans you can select up to 100 workflows and duplicate them to a target portal in one job. Mappings propagate across the batch - map a property once and every workflow in the job that uses it picks the mapping up. Each workflow succeeds or fails independently, and failed items can be retried without re-running the whole job.

Select the workflows on the Workflows page and choose Duplicate to… in the bar that appears. Its Duplicate history link opens a record of past jobs.

Copy allowances

Starter, Growth, and Pro include 2 successful single-workflow copies per month - enough for the occasional portal migration. Unlimited, Enterprise, and every agency plan include unlimited copies plus bulk duplication. Dry runs never count, and the 14-day trial follows Pro's allowance.

Property impact

W and R badges per property. Available on every plan; per-conflict detail on Growth and above.

How property impact works

Property impact opens from the "Property Impact" section of the filter sidebar and expands as a flyout panel. It shows every workflow that reads or writes any property in your portal, grouped by object type (Contact, Deal, Company, Ticket).

Each property row shows a W badge (writers - workflows that set this property) and an R badge (readers - workflows that use this property as an enrollment trigger or branch condition). Click a property to highlight the relevant workflows on the canvas.

Property impact view is available on all plans. Conflict detail is available on Growth and above.

Conflict detection

Entflow uses a two-gate system to tell write collisions apart from redundant writes:

Redundant writes (amber) - multiple workflows set the same property to the same static value. Safe to run together.

Write collisions (red) - multiple workflows write different or dynamic values to the same property AND their enrollment triggers overlap, meaning they can process the same contacts at the same time. The last writer wins, and the outcome is unpredictable.

Conflicts appear as coloured warning icons on the property row. You can dismiss a conflict if it's intentional. Dismissed conflicts can be restored from the dismissed filter.

Conflict detail is available on Growth plans and above.

Filtering by object type

Use the pills at the top of the property impact section to filter the property list by object type. Standard object pills (Contact, Deal, Company, Ticket) show by default; if your portal has custom objects with synced properties, each appears as its own pill with the schema's HubSpot label. The conflict count badge updates to reflect only the visible conflicts.

The "X conflicts" button filters the list to show only properties with active write conflicts.

AI Analyst

Deep AI analysis that reads your full workflow definition for defects inside its logic. Two severities: critical and warning.

AI Analyst overview

The Analyst page (top navigation) shows all your workflows in a table with their health scores. Click "Run analysis" on any workflow to get a deep review.

The AI looks for defects inside a workflow's own logic:
- References to properties, lists, emails or workflows that no longer exist
- Branches that can never run
- A workflow that re-enrolls itself
- Required actions that are missing
- Property writes that contradict each other
- A goal that contradicts the enrollment trigger

Consent, suppression and email spacing are checked by the health score's rules, not the AI, and problems that span several workflows (like two workflows enrolling each other) are Cleanup's job.

Every issue is rated Critical or Warning, with a specific fix suggestion you can action inside HubSpot immediately.

If a finding doesn't apply to you, Dismiss it - it won't be raised again for that workflow. If it's actually wrong, click "Not accurate" instead: it's dismissed the same way, and it also feeds detection tuning - patterns users consistently flag get tightened or retired.

Audit Reports

A shareable audit of the workflows you pick. Generate it in the background, export as PDF or DOCX for stakeholders or clients.

What audit reports are for

An audit report is a structured deliverable covering a set of workflows you select. It gathers what Entflow already knows about them - health scores, cleanup issues, critical conflicts, and findings from any AI Analyst runs - ranks the findings by severity, and produces a single document you can hand to a client or stakeholder. Generating it makes no AI calls of its own; it is AI-aware, using the Analyst's earlier findings where they exist.

Typical audit engagements: handing a new agency client a full portal review; a quarterly health check across an in-house team's marketing workflows; a pre-migration audit before moving portals; a deliverability review focused on email-sending workflows only.

Audit reports are included on every plan: 3 per month on Starter, 10 on Growth, and 25 on Pro and Unlimited, with pooled allowances on agency plans. The 14-day trial includes 3.

Creating an audit report

Go to the Audit page from the top navigation. Pick which workflows to include - search by name, filter by object type or status, or bulk-select by tag. You can audit a single workflow, a handful, or the entire portal.

Name the report (e.g. "Q2 marketing audit - Acme Corp") and hit Generate. Entflow assembles every selected workflow's scores and detected issues into a structured report: an executive summary, a risk assessment, critical conflicts, prioritised recommendations, and a section per workflow with its findings and fix steps.

Generation runs in the background - you can close the tab and come back. You'll get a progress bar and a completion indicator.

What's in the report

Each audit report groups findings into severity tiers: Critical (will break or cause data corruption - fix now), High (significant risk - fix this sprint), Medium (worth addressing - plan for the quarter), Low (housekeeping - optional).

Every finding includes: the workflows it applies to, a plain-English description, a HubSpot-specific fix recommendation, and the data that triggered the detection. Cross-workflow findings come from Cleanup and conflict detection: circular enrollment chains, loops between workflows, broken references and overlapping property writes.

Reports export as PDF (A4 or Letter) or as an editable DOCX. On agency plans, exports carry your own brand.

Simulate

Which workflows a new record sets off, and in what order.

Running a simulation

Describe a record - pick an object, set the properties that matter and a creation time - or fill in one of your own HubSpot forms, and Simulate runs it against every active workflow in your portal. It works from your last sync and writes nothing to HubSpot; the only call it makes reads a form's fields the first time you use that form.

The canvas lays the run out left to right: one column for each moment something happens, one row for each enrollment. Waits come from your workflows' own delays, so a two-day delay lands two days later. When one workflow sets a property that enrolls another, the second starts at the moment of that change, indented under the first.

On plans without the full simulation, the run shows the first few workflows and one cascade step, and says so.

Reading the result

Every workflow that didn't enroll is listed with the one condition that blocked it. After the run, Simulate compares the record as you described it with the record once every workflow has run, property by property.

Times come from the delays configured in your workflows. HubSpot's own enrollment and processing latency isn't included, so real runs land slightly later. Anything the simulation can't know - custom code, webhooks, a wait on a real-world event such as an email open or a page view, or two workflows writing the same property at once - is marked rather than guessed.

Changelog

What changed between syncs. Filter by workflow, change type, or date range, and open the before/after diff.

How the changelog works

Every time Entflow syncs your portal, it compares the current state of every workflow against the last known state, and records new workflows and every change to existing ones. (The first sync has nothing to compare against, so the changelog starts with your second sync. A workflow deleted in HubSpot is removed from Entflow rather than logged.)

Changes are recorded with a timestamp and a summary. Click "diff" on any change to open the full before/after view - the two versions side by side with additions, removals, and modified settings colour-coded, so you can pinpoint exactly which action was added, which property value changed, or what enrollment criteria was modified. The same view opens from the Recent Changes card in any workflow's detail panel.

The changelog is available on all plans.

Filtering the changelog

Use the filters to show only specific change types: workflow created, actions added, removed or changed, enrollment criteria changed, status changes, and more. You can also narrow the log to a date range, or to changes made by a specific HubSpot user when HubSpot reports who made them (it often doesn't).

Cleanup Recommendations

A ranked to-do list of cleanup tasks. Resolved / Ignored states persist across syncs.

How Cleanup works

The Cleanup page analyses your full workflow library and surfaces a prioritised list of issues. Each issue belongs to one category, and the categories sit in four groups so you can focus on one kind of problem at a time.

Data integrity - references that no longer work

  • Broken emails, Broken lists, Deleted forms - a step points at an email, list or form that no longer exists.
  • Links to inactive and Links to deleted - an active workflow enrolls into an inactive or deleted workflow, so those enrollments silently fail.
  • Missing properties and Blank tokens - a property that doesn't exist in the portal, or a personalisation token that renders blank.
  • Ownerless notifications and Deactivated user - a notification or assignment with no owner, or one aimed at a user who no longer exists.

Logic - things that won't behave as intended

  • Critical conflicts - circular enrollment chains, where workflows enroll records into each other. Write collisions and other conflicts are on the Map and the Dashboard.
  • Loops and Ping-pong - a workflow that re-enrolls itself through its own writes, or two that keep triggering each other.
  • Goal conflict - goal criteria overlap enrollment, so records enter and immediately leave.
  • Redundant and Identical workflows - a workflow whose actions change nothing, or two or more workflows that are on with the same stored trigger and actions. Each identical workflow carries a 60-point deduction.
  • Dead branch, Duplicate writes, No exit, Catch-all form, Email burst, Past delay and Future-only - branches that can't run, the same property written twice, email sequences with no way out, form triggers with no form chosen, back-to-back emails, delays that have already passed, and enrollment that can only start in the future.

Lifecycle data - writes that can damage data

  • Overwrite risk, Null overwrites and Lifecycle regression - a populated field overwritten with a blank or dynamic value, or a lifecycle stage moved backwards.

Hygiene - should this still be running?

  • Stale, Empty, Huge workflow, Long first delay, Test active and Test data - workflows that never enrolled anyone, have no actions, are unusually large, wait a long time before doing anything, look like tests, or carry test data.
  • AI issues - findings from the AI Analyst on active workflows.

Score reasons - the health score's own reasons for a workflow's grade - are listed in a separate, collapsed section below the queue. They explain a grade and need no fix, so they are not counted as issues.

Look-alikes are listed in a collapsed section of their own below the queue. A look-alike family is two or more workflows that are on, on the same object, with the same steps in the same layout, writing the same properties and differing only in values, their trigger's filters or events, or re-enrollment. Each family is a question, not an issue: do all of them need to exist? It says what they share and what differs, costs no points and is not counted as an issue. Compare opens two of them side by side; Dismiss keeps it in the section, marked dismissed, with Reopen.

Every issue carries one of three priorities: High (act this sprint), Medium (plan for the quarter), Low (optional housekeeping).

Priority levels and filters

Each issue has a priority: High, Medium, or Low.

High issues need immediate action - circular enrollment chains, broken references and other defects that stop a workflow doing its job.

Medium issues are important but not urgent - for example enrollment into paused workflows, identical workflows, and a workflow that has never enrolled anyone and has not changed in 12 months or more.

Low issues are housekeeping - for example a very long first delay, or an unusually large workflow.

Use the filters in the left rail to focus on one category or priority at a time, or use Resolve all… to dismiss every Low issue or mark everything resolved.

The Cleanup page is available on all plans.

Confidence tiers

Not every detection is equally certain, and Entflow says so. Each detector carries a confidence tier; lower-confidence issues are framed as "Worth checking" rather than stated as definite problems - a workflow that looks abandoned may simply run on a quarterly cadence only you know about.

Where possible, issues are also verified against your live HubSpot portal before they're shown - for example, confirming a property really no longer exists before flagging a broken reference. Issues that fail live verification are dropped rather than left to waste your attention.

Resolving and ignoring issues

Mark an issue as Resolved once you've fixed it in HubSpot, or Dismiss it if it's intentional and you don't want it resurfacing. Both move it to the Cleared section at the bottom, where Reopen brings it back.

Open an issue and use Copy fix prompt to copy a ready-made prompt describing the issue and its workflows, to paste into the AI assistant you use.

A look-alike question has a direct 'Compare' link that opens two of its workflows side by side.

Keeping data fresh

When your last sync is more than three hours old, the Sync button at the top of most tools turns amber. Data in Entflow is only as fresh as your last sync - for accurate cleanup recommendations, sync regularly.

Canvas tools

Sections, sticky notes, shapes, text, connectors, smart guides. Export PNG (all) · CSV (all) · SVG (Pro+) · PDF (Pro+).

Canvas overview

The bar above the map counts the workflows and dependencies on the canvas, then holds, in order:

Workflows and Deleted - which workflows the map shows.
Find on map - the magnifier: find any workflow by name (or press / or Ctrl+K).
View - one menu for how the map is drawn: Lines picks which dependency lines show (All, Only active, Only inactive or None), Arrange lays the nodes out by Object or by Cluster, Undo puts back the positions you had before the last arrange, and Compact shrinks every card. Hover View to read the current settings.
Undo arrange - appears beside View after an arrange, for a one-click undo.
Properties - opens the Properties panel: the Impact Simulator and unused properties.
… - Auto-sync (on, off or paused), Export, the guided tour where one is available, and the keyboard shortcuts reference. Hover it to see whether Auto-sync is on.
Sync and Saved views - at the end of the bar.

The Key at the top left of the canvas names each object's colour and each kind of dependency line.

The drawing bar at the bottom of the map is always there. It gives you annotation tools to document your workflow architecture on top of the live dependency map. Each tool also has a keyboard shortcut, and Esc puts you back on Select.

Sections - draw a labelled area around any group of workflows (e.g. "Marketing Owned", "Sales Handoff", "Onboarding").
Sticky notes - drop a note anywhere to document decisions, flag issues, or add ownership context.
Shapes - rectangles, diamonds, circles for custom diagramming.
Text - free-form text labels for anything that needs explanation.
Connectors - draw custom arrows between any elements on the canvas.
Smart guides - snap to grid and alignment guides when moving nodes.

Basic canvas (sections and sticky notes) is available on Growth and above, and during the trial. The full canvas toolkit is available on Pro plan and above.

Exporting the map

Open the … menu at the top right of the map and choose Export, or right-click an empty part of the canvas and choose Export map.... Both open the same export panel.

PNG - raster image, good for presentations and documents. Available on all plans.
CSV - spreadsheet of all workflows with status, action count, and dependency count. Available on all plans.
SVG - vector format, scales perfectly for large prints. Available on Pro and above.
PDF - print-ready document. Available on Pro and above.

To copy a single workflow as a picture, select it and click Copy as image at the top right of the map: a PNG of that workflow's card goes to your clipboard.

Tags

Coloured tags. Multi-assign per workflow. Starter plan and above.

Using tags

Tags let you label workflows for filtering and organisation. Create tags from the Tags section of the filter sidebar. Each tag has a colour, and you can assign multiple tags to any workflow.

Common uses: team ownership (Marketing, Sales, RevOps), funnel stage (Lead Capture, Nurture, Onboarding), status (Needs Review, Deprecated, In Progress).

Tags are available on Starter plans and above.

Settings

Profile, team, plan & billing, notifications, and the portal danger zone - everything about your account in one place.

Reconnecting HubSpot

Open Settings → HubSpot for the portal you want to reconnect and click Reconnect HubSpot. This re-runs HubSpot's OAuth consent flow with the current scope set, which is the right move when you need to grant a permission Entflow added after you originally connected (for example, the optional users scope that turns numeric user IDs into real names on the map).

Reconnecting is non-destructive: your synced workflow data, canvas, tags, changelog, dismissed conflicts, and saved filter views all stay intact. The only thing that changes is the OAuth token and the scope set. The consent screen opens at the top level so they work cleanly even when Settings is being viewed inside the dashboard's embedded sidebar.

Reconnect HubSpot is separate from Disconnect, which stays in Settings → Danger Zone. Disconnect removes your access to the portal entirely (and, if you're the only user, deletes the synced data). Reconnecting just refreshes the connection.

The reconnect prompt

When Entflow ships a feature that needs a permission your portal hasn't granted yet (for example, custom-object label resolution or owner-name resolution), the notification bell at the top of the app shows a Reconnect HubSpot card naming the affected feature.

Click Reconnect HubSpot to jump straight into the consent flow with the right portal pre-selected. Dismissing the card hides it for 7 days; it reappears after that if you still haven't reconnected. It clears itself once you complete the reconnect and the missing scope is granted.

If you'd rather receive the prompt by email (e.g. a portal that doesn't get opened often), the portal's owner gets a one-off reconnect email when scope-required features ship.

Plan & billing

Settings → Plan & Billing shows your subscription and usage. Every plan renders as an expandable row - click one to see exactly what the tier includes without leaving the app - and your current plan is highlighted.

Upgrades, downgrades, and cancellations run through Paddle, our merchant of record, which handles VAT and sales tax automatically. Past invoices are listed here for download, and usage meters show where you stand against your monthly AI-analysis and audit allowances.

Team

Settings → Team manages members and invitations for your Entflow account - invite teammates so they work from the same portals and synced data, and remove access when people move on.

Notifications

Slack webhook or generic JSON webhook - fired on sync completion, and on conflicts a sync is the first to see.

Webhook notifications

Go to Settings → Notifications to configure outbound webhook notifications.

Paste a Slack Incoming Webhook URL to receive a formatted message in Slack whenever a sync completes or new conflicts are detected.

Paste any generic webhook URL to receive a JSON POST on every sync. The payload includes the portal ID, portal name, event type, workflow count, conflict count, change count, and timestamp.

Both Slack and generic webhooks are optional and independent.