> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinq.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Blinq for GoHighLevel

> Map Blinq fields onto your custom GoHighLevel fields, and choose which team members sync.

Open **Settings → Integrations → GoHighLevel** to control what reaches GoHighLevel. These settings apply to your whole workspace.

## What reaches GoHighLevel

Each exported contact carries across their contact details, along with the notes recorded against them in Blinq, their tags, and the campaign they were captured in.

## Mapping your fields

The [field mapper](/features/field-mapping) decides where each Blinq field lands in GoHighLevel. You can map Blinq's standard fields and your hidden fields onto your own custom GoHighLevel fields, so contacts arrive structured the way your team already works rather than needing tidying up afterwards.

<Info>
  Map your fields before you export in bulk. Contacts that have already synced keep the mapping they arrived with, so it's much easier to get this right first than to correct records in GoHighLevel afterwards.
</Info>

## Choosing who syncs

Manual triage lets you pick which team members sync to GoHighLevel. Contacts captured by anyone you haven't selected stay in Blinq.

This is useful when only part of your team works out of GoHighLevel — an events crew or one agency pod, say — and you don't want everyone else's contacts landing there too.

## Saving your settings

Select **Save** to apply your changes.

## If a team member's contacts aren't arriving

Check these in order:

1. **Are they selected in manual triage?** Only the members you've picked sync to GoHighLevel.
2. **Do they have a team card?** Someone with no card, or on a personal card, has their captures saved as personal contacts, which never export and never raise an error.

If both check out, email [support@blinq.me](mailto:support@blinq.me) with the affected email addresses and roughly when the contacts were captured.

<hr />

### Need help?

For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me).