Destinations

A Destination is a workflow that takes one or more target lists and pushes their companies and contacts into a connected CRM on a schedule you control, with full control over which fields go where.

Before you begin

To create a Destination, you need:

1. Access to a HubSpot or Salesforce account with admin or app-authorization permissions — you'll connect it while building the workflow

2. At least one Target List with contacts or companies in it

3. Admin or Marketer access to your 1eyeᴬᴵ workspace

For this guide, we'll use Snowbricks as the example workspace.

Where to find Destinations

1. Open your 1eyeᴬᴵ workspace

2. Select Destinations in the left-hand nav

You'll see every destination workflow you've created, along with its status.

The Destinations list

The Destinations list shows all your workflows, filterable by:

Each row shows:

1. Workflow name

2. Status (e.g. Running)

3. Created at

4. Updated at

5. Destination icon (HubSpot or Salesforce)

6. Actions menu (⋮)

Example, for Snowbricks:

Step 1: Create a destination workflow

1. Select Add Destination

2. Enter a Name for the workflow

3. Choose a Destination — HubSpot or Salesforce

For Snowbricks, this might look like:

You don't need to connect HubSpot or Salesforce before this step — you'll connect it in the next step, at the Destination node, if it isn't already connected.

Step 2: Build the workflow

After creating a destination workflow, you'll land on its workflow canvas with four nodes:

Start → Target Lists → Destination → End

Start → Target Lists → Destination → End

Start → Target Lists → Destination → End

Start

Select the Start node to configure when the workflow runs.

Select Save Workflow Settings after choosing an option.

Target Lists

Select the Target Lists node to choose which target lists feed this workflow.

1. Select Select Target Lists

2. Search or scroll to find a target list

3. Select each target list you want to include

For example, Snowbricks might push from:

Website Visitors (homepage)
Website Visitors (pricing page)
Website Visitors (enterprise page)
Website Visitors (EMEA)

Website Visitors (homepage)
Website Visitors (pricing page)
Website Visitors (enterprise page)
Website Visitors (EMEA)

Website Visitors (homepage)
Website Visitors (pricing page)
Website Visitors (enterprise page)
Website Visitors (EMEA)

You can select more than one target list per workflow. New contacts and companies added to any selected target list are picked up automatically while the workflow is running.

Destination

Select the Destination node to connect your CRM, if you haven't already, and map 1eyeᴬᴵ fields to fields in your CRM.

If HubSpot or Salesforce isn't connected yet, the node shows a Not Connected status with a Connect button — see Connect HubSpot or Connect Salesforce in Overview for the full walkthrough. Once connected, the node's status updates to Connected and the field mapping options appear.

Field mapping is organized into four sections:

Each standard field has a Push checkbox — uncheck it if you don't want that field sent to your CRM.

For example, Snowbricks' Standard Contact Fields might look like:

Custom Contact Fields let you push activity data that doesn't exist as a standard CRM field. For example:

Select + Add more to map additional custom fields. Select Save [Destination] (e.g. Save Hubspot) once your mapping is set.

End

The End node marks the end of the workflow — no configuration needed here.

Monitor pushed records

Select View console from the workflow canvas to see the status of every record in the workflow.

The Console shows contacts filtered by:

Select any contact to see the exact field values that were sent (or attempted) to your CRM.

Example, for a pushed contact:

If a contact is Pending, the detail view includes a reason, for example:

Reason: Email required for HubSpot push

Reason: Email required for HubSpot push

Reason: Email required for HubSpot push

Use this to understand what's blocking a push — usually a missing required field on the contact or company record.

Review a contact from the workflow

Select a contact from anywhere in Destinations to open their full record, including:

1. Persona and ICP match

2. Signal count

3. Person, Company, and Target Lists tabs

4. Full contact details — name, role, address, and contact & social fields (phone, email, LinkedIn, Twitter, Facebook, GitHub)

This is the same contact record you'd see from Target Contacts or Website Signals — Destinations just shows you its current push status alongside it.

Best practices

1. Map required fields first
   Make sure fields your CRM requires (like email) are mapped and populated before pushing, so records don't get stuck in Pending.

2. Start with one target list
   Test a workflow with a single, well-defined target list before adding more.

3. Use custom fields for signal context
   Map Target Page, Visit Count, and Last Visited fields so your CRM shows why a contact was pushed, not just who they are.

4. Check Pending before Failed
   Pending contacts usually have a clear, fixable reason. Review those first.

5. Choose the right run setting
   Use Runs continuously for always-on target lists, and Runs once only for a one-time push.

Troubleshooting

FAQ

Can one workflow push to both HubSpot and Salesforce?

No. Each destination workflow pushes to a single connected CRM. Create a separate workflow if you need to push the same target lists to more than one CRM.

Can I push companies without contacts, or contacts without companies?

Contacts are pushed with their associated company context. Company-level fields (Standard and Custom Company Fields) are mapped alongside the contact.

What happens if I remove a target list from a running workflow?

Contacts already pushed remain in your CRM. New contacts from the removed target list will no longer be picked up.

Can I edit field mapping after a workflow has started running?

Yes. Open the Destination node, update your mapping, and save. New pushes will use the updated mapping.

Why is a contact marked Failed instead of Pending?

Failed means the CRM rejected the push outright (for example, an invalid value). Pending means 1eyeᴬᴵ hasn't attempted the push yet, or is waiting on a missing required field.

Next step

Once your first Destination is running, check the Console regularly to make sure records are pushing cleanly, and refine your field mapping as you learn what your sales team needs in the CRM.