Operations Hub Software flashcards
Operations Hub Software · Build recall with a focused review session.
33 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Operations Hub
- HubSpot's operations platform combining data sync, data quality automation, and programmable automation via custom-coded workflow actions.
- Data sync
- A connector that links HubSpot to an external system, mapping fields and syncing records in one or both directions.
- Sync direction
- The setting that determines whether records flow two-way, one-way from HubSpot, or one-way to HubSpot for a mapped field.
- Field mapping
- The definition linking an external field to a HubSpot property, including direction and any transformation applied during sync.
- Sync filters
- Criteria that limit which records participate in a sync, reducing volume and preventing unwanted records from entering HubSpot.
- Sync history
- A log of sync activity showing created, updated, failed, and skipped records along with error reasons for troubleshooting.
- Preferred source
- A conflict-resolution setting that designates which system's value wins when both sides change the same mapped field.
- Format data action
- A workflow action that standardizes values such as capitalization, dates, phone numbers, and numbers to a consistent format.
- Clean data action
- A workflow action that removes duplicates, fixes formatting issues, or clears property values to improve data quality.
- Enrich data action
- A workflow action that appends firmographic or company data from enrichment providers to fill missing properties.
- Custom code action
- A workflow action that runs JavaScript in a Node.js runtime, receiving inputs and returning outputs to HubSpot properties.
- Secrets
- Account-level stored credentials referenced in custom code via environment variables, keeping API keys out of source code.
- Callback
- The function a custom code action must call with outputFields to return results; failing to call it causes a timeout.
- Output fields
- Values returned by a custom code action's callback, declared in the action schema and mapped to HubSpot properties.
- Input fields
- Property values passed to a custom code action via event.inputFields, mapped from the enrolled record.
- Deduplication
- The process of identifying and merging duplicate records based on match keys such as email or domain.
- Merge rules
- Settings determining which record's property values survive a deduplication merge; the primary record's values are kept by default.
- Calculated property
- A read-only property whose value is derived from other properties using a formula and updates when sources change.
- Rollup property
- A property that aggregates values from associated records, such as count, sum, or average, supporting cross-object reporting.
- Workflow enrollment criteria
- Conditions that determine which records enter a workflow, such as record creation, property change, or form submission.
- Re-enrollment
- A workflow setting controlling whether a record can re-enter the workflow after completing it.
- Goal criteria
- Conditions that remove a record from a workflow once met, preventing redundant processing and conserving action executions.
- Workflow branches
- If/then logic that routes records to different actions based on property values, running actions only when conditions are met.
- Action history
- A per-record log showing each workflow action's status, including failures and skips with reasons.
- Property history
- An audit trail recording changes to a property, including the source such as sync, workflow, or user.
- Association labels
- Tags on object associations that distinguish relationship types, enabling workflows to act on specific associations.
- Datasets
- Multi-object data models that join records across objects for cross-object reporting and analysis.
- Sandbox
- A separate account environment for testing syncs, mappings, and custom code before promoting changes to production.
- API rate limits
- Per-account request caps that custom code actions and syncs must respect, often handled with batching and backoff.
- Sync conflict
- A situation where both sides change the same mapped field between syncs, resolved by preferred source or last-write-wins.
- Match key
- The field used to identify whether a synced record already exists, such as email for contacts or domain for companies.
- Connector
- A configured integration between HubSpot and an external app, with its own mappings, filters, and sync schedule.
- Operations Hub tiers
- Subscription levels that gate features such as data sync, data quality actions, custom code, and automated deduplication.