From install to first run

Association Mirror Setup Guide

Connect an authorized HubSpot portal, configure the custom action, and test it safely before enrolling production records.

Before you begin

  • You need permission to install connected apps and create workflows in the HubSpot portal.
  • HubSpot workflow availability depends on your HubSpot subscription.
  • Object choices depend on the portal's enabled object library and the OAuth scopes its administrator grants. Products and Users are not available as target or associated-object choices because HubSpot does not allow them to be associated; executions enrolling either as a source are rejected. Contracts and Credit Memos are unavailable because HubSpot does not currently provide their public Marketplace OAuth scopes.
  • Start with test records. Sync and Remove can remove associations from the destination record.
1

Create an Association Mirror Account

Start free

Create an account at associationmirror.com/register. New accounts can use the Free plan without a credit card.

The Free plan includes 25 workflow executions per monthly period and one connected HubSpot portal. Standard is $25/month for 250 executions and up to three portals. Premium is $200/month for 5,000 executions and up to five portals.

Choose a plan after testing

The Free plan is ongoing, not a timed trial. You can upgrade from the pricing page and manage an existing paid plan through the Stripe billing portal linked from your dashboard.

Create Account
2

Connect Your HubSpot Portal

  1. Sign in to Association Mirror and open your dashboard.
  2. Select Add Portal or Connect HubSpot. The authenticated install URL is associationmirror.com/hubspot/install.
  3. In HubSpot, select the portal you are authorized to connect.
  4. Review the requested permissions and approve the connection.
  5. Return to the dashboard and confirm that the portal ID appears under Connected Portals.

Why these permissions are requested

Required permissions provide OAuth, workflow automation, and read/write association access for contacts, companies, deals, and tickets. Optional permissions cover additional standard object families and custom objects. Association Mirror uses only the object permissions that HubSpot grants to read record IDs and associations and to apply the default relationship changes you configure. Optional scopes unavailable to a portal do not block installation.

Disconnecting is different from uninstalling

Removing a portal from the Association Mirror dashboard deletes the saved connection and OAuth tokens from Association Mirror. It does not delete workflow actions already configured in HubSpot; those actions cannot run until the portal is reconnected.

To revoke the app in HubSpot, open Settings → Integrations → Connected Apps, select Association Mirror, and choose Actions → Uninstall. See the data-deletion instructions for the full sequence and account-deletion consequences.

3

Add the Workflow Action in HubSpot

  1. In HubSpot, go to Automation > Workflows.
  2. Create a workflow or open a workflow that uses the record type you want as the source.
  3. Set enrollment criteria that are narrow enough for a safe first test.
  4. Add an action and find Association Mirror > Mirror Associations.

The enrolled HubSpot record is the source. Target Object Type and Mirroring Mode identify the destination; Target Object ID is also required in specific-object mode.

4

Configure Mirror Associations

Target Object Type (required)

Choose an association-capable standard or custom destination type available to the connected portal. Choices are filtered by HubSpot object enablement and the OAuth scopes granted during installation. The selected type must match the record ID supplied below.

Mirroring Mode (required)

Choose One specific object to send associations to a single destination record. Choose All associated objects of the target type to send associations to every destination-type record already associated with the enrolled source. Choose Every associated record, across all types to connect the eligible records associated with the source to one another, including companion-to-companion relationships such as Company-to-Deal.

Required pairing for an entire group

When Mirroring Mode is Every associated record, across all types, Target Object Type must be All associated object types. This is separate from the optional Associated Object Types filter below.

Target Object ID

This field is used only for One specific object mode. Supply the destination record's HubSpot object ID. For a dynamic destination, insert a HubSpot object property. Do not paste a record URL.

Associated Object Types (optional)

Choose which authorized, association-capable object types should be mirrored. Select All associated object types, or leave the field empty, to include every eligible type available to that portal. Products and Users do not appear in this target/associated-object selector because HubSpot does not support associations for those objects.

Association Labels

Association Mirror creates HubSpot's default/unlabeled relationships. It does not select, copy, or reproduce custom association labels. If your records use custom labels, test Sync and Remove on non-production records before broader enrollment.

Operation Type

Add associations only

Adds relationships present on the source but missing on the destination. Existing destination relationships remain.

Sync exactly — adds and removes

In destination modes, adds missing relationships and removes extra destination relationships for the selected types. In Every associated record mode, Sync connects every pair in the group without removing unrelated relationships. Test carefully.

Remove associations only

Removes matching relationships according to the action configuration. Use only with test coverage and a recovery plan.

5

Test Before Publishing

  1. Create dedicated source and destination test records in HubSpot.
  2. Record the associations on both records before running the workflow.
  3. Use Add associations only for the first test whenever possible.
  4. Enroll one source record and wait for the asynchronous action to finish.
  5. Verify the destination in HubSpot and review the execution in the Association Mirror dashboard.
  6. Only then broaden enrollment criteria or use Sync/Remove.
A successful result should identify the action as complete and show the expected association counts. A result with zero changes may simply mean the destination already matches the requested state.

Troubleshooting

Action is not listed

Confirm that the correct HubSpot portal is connected, the app is installed, your user can edit workflows, and your HubSpot subscription includes the required workflow features.

Invalid destination or permissions

Confirm that Target Object Type matches the destination ID and that the connected user granted read/write access for the affected objects. If an optional object is missing, confirm that it is enabled in the portal's object library and reconnect to grant its optional scopes.

No associations changed

Check that the source has associations of the selected object types and that the destination does not already have the requested relationships.

Usage limit reached

Review usage on the dashboard. Execution resumes in the next plan period or after an eligible plan upgrade becomes effective.

Support

Email [email protected] with the subject Association Mirror Support. Include your Association Mirror account email, HubSpot portal ID, approximate execution time, workflow/action name, source and destination object types, and the visible error message. An execution ID is especially helpful.

Do not email your password, HubSpot OAuth token, Stripe secret, or payment-card details. Support requests are reviewed on normal business days; response times are not guaranteed.

Email Support Open Dashboard Data Deletion Instructions

Public support URL: https://associationmirror.com/setup-guide#support