Skip to content

Records

Use this capability family for creating, updating, deleting, and merging CRM records after the exact target records and object types are clear.

Supported actionsBridge or hybrid actionsAccess used
50crm.objects.companies.write, crm.objects.contacts.write, crm.objects.custom.write, crm.objects.deals.write, tickets
  • Create a small batch of CRM records with required properties.
  • Update specific records after confirming IDs or names.
  • Merge duplicate records only after confirming which record should remain.
  • Confirm the target portal is correct.
  • Check the operation names, target assets, and required access.
  • Resolve missing-permission warnings before execution.
  • Review operation results after execution.
  • Verify record IDs, object types, and merge direction before execution.
  • Inspect HubSpot after batch changes to confirm the affected records look right.
Action IDWhat it doesExecutionRequired accessMain details
batch_create_recordsCreate multiple CRM records in a single batch.Does not require the bridge extensionDepends on the target object typeobject type, records
batch_delete_recordsDelete multiple CRM records in a single batch.Does not require the bridge extensionDepends on the target object typeobject type, record IDs
batch_update_recordsUpdate multiple CRM records in a single batch.Does not require the bridge extensionDepends on the target object typeobject type, records
merge_recordsMerge two duplicate CRM records.Does not require the bridge extensionDepends on the target object typeobject type, primary ID, merge ID
upsert_recordsCreate or update CRM records using a unique property.Does not require the bridge extensionDepends on the target object typeobject type, match property, records

Create multiple CRM records in a single batch

Section titled “Create multiple CRM records in a single batch”

Create multiple CRM records in a single batch. The draft records object type, records for review.

  • Action ID: batch_create_records
  • Change type: Create
  • Execution: Does not require the bridge extension
  • Required access: Depends on the target object type
  • Main details reviewed in the plan: object type, records

Delete multiple CRM records in a single batch

Section titled “Delete multiple CRM records in a single batch”

Delete multiple CRM records in a single batch. The draft records object type, record IDs for review.

  • Action ID: batch_delete_records
  • Change type: Delete
  • Execution: Does not require the bridge extension
  • Required access: Depends on the target object type
  • Main details reviewed in the plan: object type, record IDs

Update multiple CRM records in a single batch

Section titled “Update multiple CRM records in a single batch”

Update multiple CRM records in a single batch. The draft records object type, records for review.

  • Action ID: batch_update_records
  • Change type: Update
  • Execution: Does not require the bridge extension
  • Required access: Depends on the target object type
  • Main details reviewed in the plan: object type, records

Merge two duplicate CRM records. The draft records object type, primary ID, merge ID for review.

  • Action ID: merge_records
  • Change type: Update
  • Execution: Does not require the bridge extension
  • Required access: Depends on the target object type
  • Main details reviewed in the plan: object type, primary ID, merge ID

Create or update CRM records using a unique property

Section titled “Create or update CRM records using a unique property”

Create or update CRM records using a unique property. The draft records object type, match property, records for review.

  • Action ID: upsert_records
  • Change type: Update
  • Execution: Does not require the bridge extension
  • Required access: Depends on the target object type
  • Main details reviewed in the plan: object type, match property, records
  • Planning notes:
    • Use one stable unique property for the whole batch.
    • Prefer a custom unique property instead of email for contact upserts that omit unchanged properties.
    • Create associations in a later operation using any record refs emitted here.

Back to supported actions