Operations Hub Software cheat sheet

Operations Hub is HubSpot's operations platform; its three core capability groups are data sync, data quality automation (format, clean, and enrich data), and programmable automation via custom-coded workflow actions.

Data sync connects HubSpot to external systems (CRMs, ERPs, billing tools) with field mappings that can be bidirectional or unidirectional; each mapping defines a source, destination, and sync direction.

Sync direction options are two-way, one-way from HubSpot, or one-way to HubSpot; a field cannot be mapped two-way to more than one external field without conflict risk.

Default sync frequency is roughly every 5-15 minutes for most connectors; a manual sync can be triggered on demand, and sync history logs record created, updated, and failed records.

Field mapping types include direct field-to-field mapping, static value mapping, and custom mapping expressions; deduplication during sync uses email (contacts) or domain (companies) as the primary match key by default.

Format data actions standardize values: capitalization, date format, phone number formatting, number formatting, and trimming whitespace; these run as workflow actions and do not alter the original source record unless the property is overwritten.

Clean data actions include removing duplicates, fixing formatting, and clearing property values; enrich data actions can append firmographic or company data from enrichment providers.

Custom-coded workflow actions run JavaScript (Node.js runtime) inside a workflow; they receive inputs via the callback and return outputs plus an optional outputFields array, with execution time limits per action.

Operations Hub seat tiers historically gate features: data sync and data quality actions are available on Professional, while custom-coded actions and advanced sync scheduling require Enterprise.

Custom code actions use secrets for API keys; secrets are stored securely and referenced in code, never hardcoded, and are managed at the account level.

A custom code action's callback signature is exports.main = async (event, callback) => { ... callback({ outputFields: {...} }); }; event.inputFields holds the mapped input property values.

Errors in custom code actions surface in the workflow's action history with the error message and stack trace; a failed action stops downstream actions for that record unless the workflow is configured to continue.

Data quality automation runs inside workflows, so triggers (contact created, property changed, form submission) determine when formatting, cleaning, or enrichment executes on a record.

The deduplication tool compares records on chosen properties; merging keeps the most recent value by default per property, and the primary record's record ID survives the merge.

Property sync conflicts resolve by a last-updated-wins rule unless the mapping is set to a preferred source; audit the sync history for overwritten values.

Calculated properties derive values from other properties using formulas; they update when referenced properties change and can be used as inputs to workflow actions.

Association labels and association-based workflows let operations teams automate based on relationships between objects (for example, primary company vs. billing company).

Sandbox accounts allow testing syncs, mappings, and custom code before promoting changes to production; sandboxes do not include all connected app data.

Dataset and reporting operations: Operations Hub enables building datasets from multiple objects and joining them for cross-object reporting, distinct from single-object reports.

Workflow action limits: a workflow can contain a limited number of actions, and custom code actions count toward that limit; check the account's tier for exact caps.

Rate limits apply to external API calls made from custom code; batch requests and handle 429 responses with backoff to avoid action failures.

Property history and audit logs record changes made by syncs and workflow actions, enabling traceability of automated edits.

Data sync supports filtering which records sync via sync filters, reducing volume and preventing unwanted records from entering HubSpot.

Enrichment actions can fill missing company properties such as industry, size, and revenue; enriched values should be reviewed for accuracy before being used in segmentation.

Operations Hub's data quality actions are idempotent by design: running formatting twice produces the same result, which makes re-running workflows safe for formatting steps.

Custom code actions can call HubSpot APIs but must respect the private app token's scopes and the account's API rate limits.

Sync error handling: failed records appear in sync history with an error reason (missing required field, invalid value, permission); fix the source record or mapping and re-sync.

Record matching during sync: if no match key is found, a new record is created; if a match exists, the record is updated according to the mapping direction.

Workflow enrollment criteria determine which records enter automation; re-enrollment settings control whether a record can re-enter after completing the workflow.

Branching logic in workflows uses if/then branches on property values; custom code actions can be placed inside branches to run only for qualifying records.

Testing custom code: use the action's test panel with sample input fields, verify outputFields match expected property types, and confirm the action completes within the time limit.

Data sync connectors are configured per connected app; disconnecting a connector stops future syncs but does not delete previously synced records.

Calculated and rollup properties can aggregate associated records (count, sum, average), supporting operations reporting without external ETL.

Operations Hub complements rather than replaces ETL tools: it is best for record-level sync and workflow automation, not bulk historical data warehousing.

Custom code action output types must match the target property type; a string returned for a number property causes a type error in the action history.

Secrets are referenced in custom code via process.env.SECRET_NAME; rotating a secret requires updating the stored value, not the code.

Sync scheduling: near-real-time vs. scheduled syncs depend on the connector; high-volume syncs may be throttled, so schedule large initial syncs outside peak hours.

Deduplication rules can be automated with workflows that detect duplicates on email or domain and merge or flag them.

Property sync scope: only mapped properties sync; unmapped fields remain untouched, which prevents accidental overwrites of HubSpot-only data.

Operations Hub's format actions support locale-aware date and number formatting; specify the target format explicitly to avoid ambiguity between DD/MM and MM/DD.

Workflow history shows each enrollment with action-by-action status; use it to diagnose why a custom code action failed or was skipped.

Permissions: custom code actions and data sync configuration typically require super admin or appropriately scoped permissions.

Data sync mapping best practice: map the minimum required fields first, validate with a small record set, then expand mappings.

Sync conflict resolution: when both sides change the same mapped field between syncs, the configured preferred source wins; otherwise last-write-wins applies.

Custom code action debugging: log intermediate values with console.log; logs appear in the action's execution details for troubleshooting.

Enrichment and cleaning actions can be chained in one workflow: format first, then clean, then enrich, so downstream actions operate on normalized data.

Workflow re-enrollment and suppression lists prevent automated actions from re-processing records that already completed or were intentionally excluded.

API rate limits for HubSpot's CRM API are per-account per-second; custom code actions making many calls should batch and cache where possible.

Data sync does not automatically merge duplicate records created on either side; deduplication must be handled separately.

Operations Hub feature availability varies by subscription tier; confirm the tier's included actions (sync, data quality, custom code) before designing automation.

Calculated properties update asynchronously after source properties change; reports may lag briefly behind the latest edits.

Association sync: associations between objects can be synced if the connector supports it; otherwise associations must be created via workflow or API.

Custom code action inputs are limited to properties available on the enrolled object; to use associated record data, map it via a workflow or fetch it with an API call.

Error budgets: monitor sync and workflow failure rates; a rising failure rate usually indicates a mapping mismatch or an expired API credential.

Secrets and private app tokens should be scoped to the minimum permissions needed by the custom code action.

Sync filters can exclude test records or internal domains, keeping production data clean.

Workflow action order matters: actions run top to bottom, and a branch's actions run only when the branch condition is met.

Operations Hub's value is unifying sync, data quality, and custom automation in one platform, reducing the need for separate point solutions.

Custom code action timeout: actions have a per-execution time limit; long-running external calls should be avoided or offloaded to an external service.

Data sync history retention is limited; export or log sync results externally if long-term audit is required.

Property-level sync settings can mark a field as read-only from the external system, preventing HubSpot edits from overwriting source-of-truth values.

Deduplication merge rules: the primary record's values are kept by default, but individual property values can be chosen from either record during merge.

Workflow enrollment triggers include record creation, property change, form submission, and scheduled recurrence; choose the narrowest trigger to avoid unintended enrollments.

Enrichment providers supply firmographic data; enriched fields should be tagged or sourced so users know the value's origin.

Operations Hub custom code runs in a Node.js environment; use supported language features and avoid unsupported native modules.

Monitoring: set up workflow and sync failure notifications so operations teams can respond before data quality degrades.

Data sync setup order: connect the app, authenticate, choose objects, map fields, set direction, apply filters, then activate the sync.

Two-way sync requires a stable unique identifier on both sides; email for contacts and domain for companies are common keys.

Format actions should run before deduplication so that casing or whitespace differences do not create false non-matches.

Custom code actions can return multiple output fields in one call, reducing the number of actions needed in a workflow.

Workflow suppression and goal criteria stop automation when a record reaches a desired state, preventing redundant processing.

Calculated properties cannot reference properties on associated objects unless a rollup property is used.

Sync and workflow changes should be tested in a sandbox and documented, since automated edits can affect many records quickly.

Operations Hub integrates with HubSpot's object model (contacts, companies, deals, tickets, custom objects); custom objects are supported in sync and workflows on higher tiers.

Custom code action error types: input mapping errors (missing property), runtime errors (exception in code), and output mapping errors (type mismatch).

Secrets are not returned in logs; if code fails due to an undefined secret, verify the secret name matches exactly and is set at the account level.

Data sync can be paused without deleting mappings; pausing is useful during source-system migrations.

Deduplication can be run manually or automated; automated deduplication typically requires Enterprise-tier operations features.

Property sync and workflow actions both generate property history entries, so audit trails show what changed and when.

Enrichment should respect consent and data-processing agreements; do not enrich records without a lawful basis.

Workflow testing: enroll a single test record, inspect action history, then enable for all records once verified.

Operations Hub reduces manual data entry by combining sync, standardization, and automation, but it requires ongoing monitoring of sync health and workflow failures.

Sync direction decision rule: use one-way sync when one system is the system of record; use two-way only when both sides must be editable.

Field mapping decision rule: map only fields that need to be shared; every mapped field is a potential overwrite risk.

Custom code decision rule: use custom code only when built-in actions cannot achieve the transformation; prefer built-in format/clean actions for standard tasks.

Deduplication decision rule: dedupe on a stable unique key (email, domain) rather than fuzzy name matching to avoid false merges.

Workflow trigger decision rule: prefer property-change triggers over scheduled triggers when reacting to specific data changes.

Error-handling decision rule: log and alert on sync failures; silent failures are the main cause of data drift.

Tier decision rule: confirm whether the required feature (custom code, advanced sync, automated dedupe) is included in the account's Operations Hub tier before designing the solution.

Testing decision rule: validate mappings and code with a small sample before activating for the full record set.

Custom code action structure: define exports.main, read event.inputFields, perform logic, then call callback with outputFields.

Output fields must be declared so they can be mapped to HubSpot properties; undeclared outputs are not available downstream.

Secrets management: store API keys as secrets, reference via environment variables, and rotate on a schedule.

Sync history fields include record ID, action (created/updated/failed), field changed, and error message.

Data quality actions operate per record within a workflow; bulk cleaning of existing records requires enrolling them in a workflow or using import-based cleanup.

Association labels enable workflows to act on specific relationship types, such as primary vs. secondary company associations.

Rollup properties aggregate associated records and update when associations change, supporting cross-object reporting.

Operations Hub is distinct from Marketing Hub workflows: operations features focus on data sync, data quality, and programmable automation rather than campaign orchestration.

Data sync supports multiple connected apps simultaneously; each connector has its own mappings, filters, and sync schedule.

Sync conflicts are logged; review conflict logs to adjust preferred-source settings.

Custom code actions should handle null inputs defensively, since mapped properties may be empty for some records.

Format actions for phone numbers normalize to a chosen format; store the normalized value in a dedicated property if the original must be preserved.

Deduplication merges are irreversible; review merge previews before confirming.

Workflow goal criteria can remove records from a workflow once a condition is met, reducing unnecessary actions.

Calculated properties and rollups support operations reporting without external ETL, but complex transformations may still require custom code.

Regular audits of sync health, workflow failures, and duplicate rates are part of ongoing operations hygiene.

Custom code action limits: there is a maximum number of custom code actions per workflow and per account depending on tier; plan accordingly.

External API calls from custom code should include timeouts and retries with exponential backoff.

Sync filters can be based on property values or record ownership, limiting which records sync.

Property sync direction can differ per field within the same connector; mixed-direction mappings are allowed.

Enrichment actions append data but do not overwrite existing values unless configured to do so; check overwrite settings.

Workflow history retention is limited; export logs if audit requirements exceed retention.

Operations Hub supports custom objects in sync and workflows on Enterprise tiers; verify object support per connector.

Documentation of mappings, workflows, and secrets is essential for maintainability as operations teams change.

Sync activation checklist: authentication valid, objects selected, fields mapped, direction set, filters applied, test record verified, then activate.

Custom code testing checklist: sample inputs provided, outputs typed correctly, secrets resolved, execution within time limit, error paths handled.

Deduplication checklist: match key chosen, preview reviewed, merge rules confirmed, post-merge associations verified.

Workflow checklist: trigger narrow, enrollment criteria correct, re-enrollment setting intentional, goal criteria set, failure notifications enabled.

Data quality checklist: format before clean before enrich, preserve originals where needed, tag enriched values by source.

Monitoring checklist: sync failure alerts, workflow failure alerts, duplicate rate tracking, periodic mapping review.

Tier checklist: confirm custom code, advanced sync, and automated dedupe availability before design.

Change management: test in sandbox, document changes, and roll out to production in stages.

Data sync is not a backup: it syncs changes but does not preserve historical snapshots; use exports for backups.

Custom code actions cannot access the filesystem or install packages; use only supported runtime features.

Secrets are account-level and can be reused across custom code actions, reducing duplication.

Sync errors caused by invalid values usually require fixing the source record or adding a transformation step before sync.

Deduplication on companies commonly uses domain; contacts use email; deals may use a unique deal ID from the source system.

Workflow branches can run different custom code actions for different record segments, improving efficiency.

Operations Hub reporting uses datasets that join multiple objects, enabling analysis across sync and workflow outcomes.

Ongoing operations requires balancing automation with human review for high-impact changes such as merges and enrichments.

Custom code action callback is required; failing to call it results in a timeout error.

Output field names in the callback must match the names declared in the action's output schema.

Sync history can be filtered by status (success, failed, skipped) to isolate problems.

Property-level sync settings can prevent HubSpot edits from propagating to the source system.

Enrichment providers vary in coverage; validate enriched values against known records before relying on them.

Workflow re-enrollment should be disabled for actions that should run only once per record, such as welcome enrichment.

Calculated properties are read-only and cannot be edited manually; changes must come from source properties.

Operations Hub's programmable automation extends workflows with logic that built-in actions cannot express, such as conditional API calls.

Data sync connectors require OAuth or API key authentication; expired credentials are a common cause of sync failures.

Sync scheduling can be adjusted; more frequent syncs increase API usage and may hit rate limits.

Custom code actions should validate input types before processing to avoid runtime errors.

Deduplication can be scoped to specific object types and properties, not just global rules.

Workflow action history shows skipped actions with reasons, which helps distinguish failures from intentional skips.

Rollup properties can count associated records, sum deal amounts, or average values, supporting operations metrics.

Operations Hub supports association sync for some connectors; verify support before relying on it.

Regular review of mappings and workflows prevents drift as business processes change.

Sync conflict resolution settings include preferred source per field; without a preference, last-write-wins applies.

Custom code action outputs can be used by subsequent actions in the same workflow, enabling chained transformations.

Secrets should never be logged or returned in outputFields; doing so exposes credentials.

Data quality actions can standardize country, state, and phone formats to improve segmentation and deduplication accuracy.

Deduplication merges preserve associations from both records where possible; verify after merge.

Workflow goal criteria can stop processing when a record reaches a target state, conserving action executions.

Calculated properties cannot reference themselves or create circular dependencies.

Operations Hub is best suited for record-level sync and automation; bulk historical migration is better handled by import tools or ETL.

Custom code action error messages include the line number and exception type, aiding debugging.

Sync filters should be tested to confirm they exclude the intended records without excluding valid ones.

Property history shows the source of a change (sync, workflow, user), which is essential for troubleshooting data drift.

Deduplication on fuzzy fields such as name is risky; prefer deterministic keys.

Workflow enrollment criteria can reference associated record properties in some configurations, expanding automation scope.

Enrichment should be rate-limited and monitored for cost and data quality.

Operations Hub's value proposition is unifying data sync, data quality, and programmable automation, reducing tool sprawl.

Ongoing governance of mappings, secrets, and workflows is required to keep operations reliable.

Data sync field mapping supports transformation expressions for simple conversions, but complex logic belongs in custom code.

Sync history retention may be limited; export logs for compliance.

Custom code actions can make authenticated calls to external APIs using secrets, enabling integration with systems lacking native connectors.

Deduplication rules can be automated with workflows that flag potential duplicates for review before merging.

Workflow branches can route records to different custom code actions based on property values, improving efficiency.

Calculated properties and rollups support reporting on synced and workflow-modified data.

Operations Hub tiers gate features; confirm availability before design.

Regular audits of sync health, workflow failures, and duplicate rates are part of operations hygiene.

Custom code action inputs are mapped from enrolled object properties; associated record data must be fetched via API or mapped through a workflow.

Secrets are managed at the account level and referenced by name in code.

Sync direction per field can be set to one-way or two-way independently.

Deduplication merge rules determine which record's values survive; review before merging.

Workflow goal criteria remove records once a condition is met, conserving executions.

Enrichment appends firmographic data; tag enriched fields by source.

Calculated properties update asynchronously; reports may lag.

Operations Hub reduces manual data entry but requires ongoing monitoring.

Data sync setup requires authentication, object selection, field mapping, direction, filters, and activation.

Custom code actions run in a Node.js runtime with time limits and no filesystem access.

Secrets should be scoped to minimum permissions and rotated regularly.

Deduplication on stable keys avoids false merges.

Workflow triggers should be as narrow as possible to avoid unintended enrollments.

Format before clean before enrich in data quality workflows.

Calculated properties and rollups support cross-object reporting.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action callback must be called or the action times out.

Output fields must match declared schema and target property types.

Sync conflicts resolve by preferred source or last-write-wins.

Deduplication merges are irreversible; review previews.

Workflow branches run actions only when conditions are met.

Enrichment should respect consent and data-processing agreements.

Calculated properties cannot reference associated object properties without rollups.

Operations Hub tiers gate custom code, advanced sync, and automated dedupe.

Data sync history records created, updated, failed, and skipped records with error reasons.

Custom code actions should handle null inputs defensively.

Secrets are referenced via environment variables in code.

Deduplication on email and domain is standard for contacts and companies.

Workflow action order matters; actions run top to bottom.

Rollup properties aggregate associated records and update on association changes.

Operations Hub is distinct from Marketing Hub workflows in focus.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action structure: exports.main, event.inputFields, callback with outputFields.

Sync filters limit which records sync, reducing volume and errors.

Deduplication merges preserve associations where possible; verify after merge.

Workflow goal criteria stop processing when a record reaches a target state.

Enrichment appends firmographic data; tag enriched fields by source.

Calculated properties update asynchronously; reports may lag.

Operations Hub tiers gate features; confirm availability before design.

Regular audits of sync health and workflow failures are part of operations hygiene.

Data sync connectors require valid authentication; expired credentials cause failures.

Custom code actions should validate input types before processing.

Secrets should never be logged or returned in outputs.

Deduplication on fuzzy fields is risky; prefer deterministic keys.

Workflow branches route records to different actions based on conditions.

Rollup properties support cross-object reporting.

Operations Hub supports custom objects on higher tiers.

Regular review of mappings and workflows prevents drift.

Custom code action error messages include line numbers and exception types.

Sync history can be filtered by status to isolate problems.

Property history shows the source of a change, aiding troubleshooting.

Deduplication merges are irreversible; review previews.

Workflow re-enrollment should be disabled for one-time actions.

Calculated properties are read-only and cannot be edited manually.

Operations Hub's programmable automation extends workflows with logic built-in actions cannot express.

Ongoing governance of mappings, secrets, and workflows is required.

Data sync setup order: connect, authenticate, select objects, map fields, set direction, apply filters, activate.

Custom code actions run in Node.js with time limits and no filesystem access.

Secrets are account-level and referenced by name in code.

Deduplication on stable keys avoids false merges.

Workflow triggers should be narrow to avoid unintended enrollments.

Format before clean before enrich in data quality workflows.

Calculated properties and rollups support cross-object reporting.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action callback is required; failing to call it results in a timeout.

Output field names must match the declared schema and target property types.

Sync conflicts resolve by preferred source or last-write-wins.

Deduplication merges are irreversible; review previews.

Workflow branches run actions only when conditions are met.

Enrichment should respect consent and data-processing agreements.

Calculated properties cannot reference associated object properties without rollups.

Operations Hub tiers gate custom code, advanced sync, and automated dedupe.

Data sync history records created, updated, failed, and skipped records with error reasons.

Custom code actions should handle null inputs defensively.

Secrets are referenced via environment variables in code.

Deduplication on email and domain is standard for contacts and companies.

Workflow action order matters; actions run top to bottom.

Rollup properties aggregate associated records and update on association changes.

Operations Hub is distinct from Marketing Hub workflows in focus.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action structure: exports.main, event.inputFields, callback with outputFields.

Sync filters limit which records sync, reducing volume and errors.

Deduplication merges preserve associations where possible; verify after merge.

Workflow goal criteria stop processing when a record reaches a target state.

Enrichment appends firmographic data; tag enriched fields by source.

Calculated properties update asynchronously; reports may lag.

Operations Hub tiers gate features; confirm availability before design.

Regular audits of sync health and workflow failures are part of operations hygiene.

Data sync connectors require valid authentication; expired credentials cause failures.

Custom code actions should validate input types before processing.

Secrets should never be logged or returned in outputs.

Deduplication on fuzzy fields is risky; prefer deterministic keys.

Workflow branches route records to different actions based on conditions.

Rollup properties support cross-object reporting.

Operations Hub supports custom objects on higher tiers.

Regular review of mappings and workflows prevents drift.

Custom code action error messages include line numbers and exception types.

Sync history can be filtered by status to isolate problems.

Property history shows the source of a change, aiding troubleshooting.

Deduplication merges are irreversible; review previews.

Workflow re-enrollment should be disabled for one-time actions.

Calculated properties are read-only and cannot be edited manually.

Operations Hub's programmable automation extends workflows with logic built-in actions cannot express.

Ongoing governance of mappings, secrets, and workflows is required.

Data sync setup order: connect, authenticate, select objects, map fields, set direction, apply filters, activate.

Custom code actions run in Node.js with time limits and no filesystem access.

Secrets are account-level and referenced by name in code.

Deduplication on stable keys avoids false merges.

Workflow triggers should be narrow to avoid unintended enrollments.

Format before clean before enrich in data quality workflows.

Calculated properties and rollups support cross-object reporting.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action callback is required; failing to call it results in a timeout.

Output field names must match the declared schema and target property types.

Sync conflicts resolve by preferred source or last-write-wins.

Deduplication merges are irreversible; review previews.

Workflow branches run actions only when conditions are met.

Enrichment should respect consent and data-processing agreements.

Calculated properties cannot reference associated object properties without rollups.

Operations Hub tiers gate custom code, advanced sync, and automated dedupe.

Data sync history records created, updated, failed, and skipped records with error reasons.

Custom code actions should handle null inputs defensively.

Secrets are referenced via environment variables in code.

Deduplication on email and domain is standard for contacts and companies.

Workflow action order matters; actions run top to bottom.

Rollup properties aggregate associated records and update on association changes.

Operations Hub is distinct from Marketing Hub workflows in focus.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action structure: exports.main, event.inputFields, callback with outputFields.

Sync filters limit which records sync, reducing volume and errors.

Deduplication merges preserve associations where possible; verify after merge.

Workflow goal criteria stop processing when a record reaches a target state.

Enrichment appends firmographic data; tag enriched fields by source.

Calculated properties update asynchronously; reports may lag.

Operations Hub tiers gate features; confirm availability before design.

Regular audits of sync health and workflow failures are part of operations hygiene.

Data sync connectors require valid authentication; expired credentials cause failures.

Custom code actions should validate input types before processing.

Secrets should never be logged or returned in outputs.

Deduplication on fuzzy fields is risky; prefer deterministic keys.

Workflow branches route records to different actions based on conditions.

Rollup properties support cross-object reporting.

Operations Hub supports custom objects on higher tiers.

Regular review of mappings and workflows prevents drift.

Custom code action error messages include line numbers and exception types.

Sync history can be filtered by status to isolate problems.

Property history shows the source of a change, aiding troubleshooting.

Deduplication merges are irreversible; review previews.

Workflow re-enrollment should be disabled for one-time actions.

Calculated properties are read-only and cannot be edited manually.

Operations Hub's programmable automation extends workflows with logic built-in actions cannot express.

Ongoing governance of mappings, secrets, and workflows is required.

Data sync setup order: connect, authenticate, select objects, map fields, set direction, apply filters, activate.

Custom code actions run in Node.js with time limits and no filesystem access.

Secrets are account-level and referenced by name in code.

Deduplication on stable keys avoids false merges.

Workflow triggers should be narrow to avoid unintended enrollments.

Format before clean before enrich in data quality workflows.

Calculated properties and rollups support cross-object reporting.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action callback is required; failing to call it results in a timeout.

Output field names must match the declared schema and target property types.

Sync conflicts resolve by preferred source or last-write-wins.

Deduplication merges are irreversible; review previews.

Workflow branches run actions only when conditions are met.

Enrichment should respect consent and data-processing agreements.

Calculated properties cannot reference associated object properties without rollups.

Operations Hub tiers gate custom code, advanced sync, and automated dedupe.

Data sync history records created, updated, failed, and skipped records with error reasons.

Custom code actions should handle null inputs defensively.

Secrets are referenced via environment variables in code.

Deduplication on email and domain is standard for contacts and companies.

Workflow action order matters; actions run top to bottom.

Rollup properties aggregate associated records and update on association changes.

Operations Hub is distinct from Marketing Hub workflows in focus.

Regular audits of sync health and workflow failures are part of operations hygiene.

Custom code action structure: exports.main, event.inputFields, callback with outputFields.

Sync filters limit which records sync, reducing volume and errors.

Deduplication merges preserve associations where possible; verify after merge.

Workflow goal criteria stop processing when a record reaches a target state.

Enrichment appends firmographic data; tag enriched fields by source.

Calculated properties update asynchronously; reports may lag.

Operations Hub tiers gate features; confirm availability before design.

Regular audits of sync health and workflow failures are part of operations hygiene.