Skip to main content
Push buyers and companies from your target lists into HubSpot, with full control over which fields go where.

​
Before you begin

  • Admin or app-authorization permissions in the HubSpot account you’re connecting
  • At least one Target List with contacts or companies in it
  • Admin or Marketer access to your 1eyeᴬᴵ workspace
For this guide, we’ll use Snowbricks as the example workspace.

​
Connect HubSpot

Connecting HubSpot happens inside a destination workflow, at the Destination node. Step 1: Open the Destination node Step 1 Open The Destination Node 4 If HubSpot isn’t connected yet, the node shows:
HubSpot · Not Connected [Connect]
Select Connect. Step 2: Confirm the connection in 1eye Step 2 Confirm The Connection In 1eye
Allow 1eye to access your HubSpot account? Link HubSpot to sync your target lists, deduplicate against existing contacts, and enrich your HubSpot records.
Select Yes, continue. Step 3: Continue to HubSpot Opens a HubSpot-hosted bridge screen in a new window. Select Sign in to your HubSpot account if you already have one. Step 4: Log in to HubSpot Enter your HubSpot email and password, or continue with SSO, then select Log In. This is HubSpot’s own secure login screen — your credentials are entered directly with HubSpot and never seen by 1eyeᴬᴵ. Step 5: Choose your HubSpot account, if prompted If you have access to more than one HubSpot account or portal, choose the one that matches your 1eyeᴬᴵ workspace. Step 6: Review and allow access Review the permissions screen, then select Allow (or Grant access). Step 7: Connection confirmed Step 7 Connection Confirmed 3 The Destination node updates from Not Connected to Connected, and field mapping options appear.

​
Field mapping

Mapping is organized into four sections — Standard Contact Fields, Custom Contact Fields, Standard Company Fields, and Custom Company Fields. Each standard field has a Push checkbox — uncheck it if you don’t want that field sent to HubSpot. Standard Contact Fields (example) Custom Contact Fields — push activity data that doesn’t exist as a standard HubSpot field: Select + Add more to map additional custom fields. Standard / Custom Company Fields work the same way, for company-level data (domain, description, employee count, revenue, address, and any custom company property). Select Save Destination once your mapping is set.

​
Monitor pushed records

From the Console, filter HubSpot pushes by All / Pushed / Pending / Failed. Select a contact to see the exact JSON payload sent to HubSpot — contact fields and associated company fields together.

​
Disconnect HubSpot

  1. Open the workflow and select the Destination node
  2. Select the (⋮) menu next to the Connected status
  3. Select Disconnect
Disconnecting stops any workflows using HubSpot as a destination until you reconnect. Records already pushed to HubSpot remain there.

​
Best practices

Connect with an account that has the right permissions Use a HubSpot login with admin or app-authorization rights, so the connection doesn’t get blocked by a permissions gap. Review the permissions screen before allowing access Know what you’re granting 1eyeᴬᴵ access to before you select Allow. Map required fields first Make sure fields HubSpot requires (like email) are mapped and populated before pushing, so records don’t get stuck in Pending. Re-authenticate if the connection breaks If HubSpot revokes access (password change, admin policy, expired token), reconnect from the Destination node.

​
Troubleshooting

​
FAQ

No. Authentication happens on HubSpot’s own login screen. 1eyeᴬᴵ never sees your credentials.
Workflows using HubSpot as a destination stop running until you reconnect. Records already pushed to HubSpot remain there.
Yes. Open the Destination node, update your mapping, and save. New pushes will use the updated mapping.

​
Next step

Go to Destinations to build your first HubSpot workflow.