# Get card Source: https://docs.blinq.me/api-reference/cards/get-card /api-reference/openapi.json get /v1/workspaces/{workspace_id}/cards/{card_id} Gets a lightweight card summary from the specified workspace, including the public sharing URL for the card and a QR code image that encodes it. The workspace must be your personal workspace or a business workspace you own or administer. Missing cards, cards belonging to a different workspace, and inaccessible workspaces return `404`. Requires the `blinq:cards:read` scope. # List cards Source: https://docs.blinq.me/api-reference/cards/list-cards /api-reference/openapi.json get /v1/workspaces/{workspace_id}/cards Returns a paginated list of lightweight card summaries from your personal workspace or a business workspace you own or administer. Other workspaces, including business workspaces where you are only a member, return `404`. Deleted cards, drafts, and card templates are excluded. Each summary includes the public sharing URL for the card. Cards are sorted by creation time, newest first, with the card ID as a tie-breaker, so pages are deterministic. Cursors are bound to the requesting key owner and workspace. Requires the `blinq:cards:read` scope. # Get contact Source: https://docs.blinq.me/api-reference/contacts/get-contact /api-reference/openapi.json get /v1/workspaces/{workspace_id}/contacts/{contact_id} Gets a contact from the specified workspace, including contact details, tags, saved contact notes, linked note metadata, and capture context. Personal contacts must belong to the key owner. Business owners, admins, and members can retrieve a visible business contact when its ID is known; business members cannot discover these IDs through the list endpoint. Missing contacts and inaccessible workspaces return `404`. Requires the `blinq:contacts:read` scope. # List contacts Source: https://docs.blinq.me/api-reference/contacts/list-contacts /api-reference/openapi.json get /v1/workspaces/{workspace_id}/contacts Returns a paginated list of contact summaries from your personal workspace or a business workspace you own or administer. Business members receive an empty list. The workspace path segment only narrows which accessible contacts are returned; it never grants additional access. Deleted contacts, hidden contacts, and company-directory entries are excluded. Contacts are sorted by creation time, newest first, with the contact ID as a tie-breaker, so pages are deterministic. Use a contact's `id` to retrieve its full details from the same workspace. Requires the `blinq:contacts:read` scope. # Blinq Public API Source: https://docs.blinq.me/api-reference/introduction The Blinq API provides programmatic access to your contacts and notes. Download OpenAPI Document: [JSON](/api-reference/openapi.json) · [YAML](/api-reference/openapi.yaml) The Blinq API provides programmatic access to your contacts and notes. Connect Blinq to your existing tools, keep contact records in sync, and build workflows on note summaries and transcripts. API access requires a [Blinq Pro, Business, or Enterprise plan](https://blinq.me/pricing) and a verified email address. Keys are personal and scoped: they never grant access beyond what their owner can already see. ## Access scopes Choose one or more scopes when creating a key. | Scope | Grants access to | | - | - | | `blinq:contacts:read` | Your personal contacts. Business owners and admins can list contacts; members can retrieve a visible contact by a known ID. | | `blinq:cards:read` | Lightweight card summaries and sharing links in your personal workspace and business workspaces you own or administer. | | `blinq:notes:read` | Your own notes and transcripts. | | `blinq:identity:read` | Your identity and the workspaces you belong to. | ## Creating and revoking keys 1. In the Blinq web app, open Settings > API keys. 2. Select **Create new key**, choose a name and the scopes your integration needs, then select **Generate API key**. 3. Copy the key when it is shown. The secret is displayed only once; store it securely. To revoke a key, return to Settings > API keys and select **Revoke**. A revoked key stops authenticating new requests immediately. ## Quick start Send your key to `https://api.blinq.me` as `Authorization: Bearer `. In the documentation playground, enter only the key, without `Bearer`. List your notes (requires `blinq:notes:read`): ```bash theme={null} curl 'https://api.blinq.me/v1/notes?limit=5' \ -H 'Authorization: Bearer ' ``` Contact routes are scoped to one workspace. `GET /v1/workspaces` (requires `blinq:identity:read`) discovers workspace IDs; listing contacts from a known workspace ID needs only `blinq:contacts:read`: ```bash theme={null} curl 'https://api.blinq.me/v1/workspaces//contacts?limit=5' \ -H 'Authorization: Bearer ' ``` ## Errors All errors return a JSON body with `status` (the HTTP status code), `error` (the HTTP status name, such as `Bad Request`), `code` (a machine-readable error code), `message` (a human-readable description; wording may change, so branch on `code` instead), and `request_id` (the unique ID of the request, also returned as the `X-Request-Id` header). Validation errors may add a `details` array naming each parameter or body field that failed. Any route can return `400` when query parameters or the body are invalid (unknown query parameters are rejected), `401` when the API key is missing or invalid, `403` when the key is missing a required scope, its owner lacks permission, or the account plan does not include the operation, and `429` when the rate limit is reached (see Rate limits). Any route can also return `500` when an unexpected error occurs (quote `request_id` when contacting support) and `503` when API key verification or the requested operation is unavailable. The responses documented on each route below list only the status codes specific to that operation. ## Rate limits Each person can make up to **25 requests in any 5-second window**, or **300 requests per minute** at a steady rate. The quota is shared across all of their API keys; creating more keys does not increase it. When the limit is reached, the API returns `429 Too Many Requests` with a `Retry-After` header in seconds. Wait that long before retrying. ## Contacts List contact summaries or get contact details, saved contact notes, and linked note metadata. Contact lists include personal contacts and contacts in business workspaces the authenticated user owns or administers. Business members receive an empty list, but can retrieve a visible business contact by known ID. Requires the `blinq:contacts:read` scope. ## Cards List or get lightweight card summaries: the name, title, company, department, and public sharing URL on each card. Card routes are scoped to one workspace: your personal workspace or a business workspace you own or administer. Business members cannot read team cards. Requires the `blinq:cards:read` scope. ## Notes List note metadata, get note content and transcripts, search notes, or generate answers with citations. Only notes owned by the authenticated user are accessible. Requires the `blinq:notes:read` scope. ## Workspaces List every workspace the authenticated user belongs to, with its type and their role. Use a known workspace ID directly, or discover it here. Business contact listing requires owner or admin; retrieving a visible contact by known ID also allows members. Requires the `blinq:identity:read` scope. ## Me Identify the user the supplied API key acts as, with their ID and sign-in email. Confirm whose account an integration is accessing before listing workspaces or fetching data. Requires the `blinq:identity:read` scope. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Get the authenticated user Source: https://docs.blinq.me/api-reference/me/get-the-authenticated-user /api-reference/openapi.json get /v1/me Returns the user the supplied API key acts as: their `user_id` and their sign-in `email`, which is `null` when the user has none. Use it to confirm whose account an integration is accessing before listing workspaces or fetching data. The user is derived from the API key; the endpoint accepts no parameters. Requires the `blinq:identity:read` scope. # Ask a question about notes Source: https://docs.blinq.me/api-reference/notes/ask-a-question-about-notes /api-reference/openapi.json post /v1/notes/query Generates an answer to a question using the authenticated user's note titles and note bodies (AI summaries for recordings, saved text for typed notes). Transcripts are not used, and each note body is truncated to 8,000 UTF-16 code units. Pass between 1 and 8 of your own `note_ids` to answer from specific notes, or omit the field to let the API select up to 10 of the most relevant notes automatically. The answer contains inline markers such as `[1]` or `[1, 2]`: one-based positions in `citations`, where each unique note is numbered in order of first appearance and repeat references reuse the same number. When no accessible notes match, the answer is `No accessible notes were available to answer this question.` If an answer cannot be generated, the request fails with `503` and the message `Blinq could not generate an answer. Try again later.` Requires the `blinq:notes:read` scope. # Get note Source: https://docs.blinq.me/api-reference/notes/get-note /api-reference/openapi.json get /v1/notes/{id} Gets a note owned by the authenticated user, including its content or AI summary when available. Missing notes and notes owned by another user both return `404`. Requires the `blinq:notes:read` scope. # Get note transcript Source: https://docs.blinq.me/api-reference/notes/get-note-transcript /api-reference/openapi.json get /v1/notes/{id}/transcript Gets the complete plain-text transcript of a voice note or phone call owned by the authenticated user. Returns `text: null` when no transcript is stored. An empty stored transcript is returned as `text: ""` with `status: "available"`. Check `status` and `retry_after` before polling. Transcripts are returned in full, without pagination. Missing notes and notes owned by another user both return `404`. Requires the `blinq:notes:read` scope. # List notes Source: https://docs.blinq.me/api-reference/notes/list-notes /api-reference/openapi.json get /v1/notes Returns a paginated list of the authenticated user's note metadata. Notes are sorted by creation time, newest first, unless `order_by` specifies update time. Ties are broken by note ID, so pages are deterministic. For an initial sync, page with `order_by=updated_at` until `has_more` is `false`. For incremental syncs, record a checkpoint before each run, pass it as `updated_at_gte` (inclusive) with a small overlap, upsert by `id`, and advance the checkpoint only after every page succeeds. Deleted notes are omitted. There is no deletion feed; periodically reconcile a complete list of IDs to detect removals. Timestamp filtering alone does not provide lossless synchronization. Get an individual note to read its content. Requires the `blinq:notes:read` scope. # Search notes Source: https://docs.blinq.me/api-reference/notes/search-notes /api-reference/openapi.json get /v1/notes/search Searches the authenticated user's indexed note titles and bodies, including recording summaries and saved text, using keyword and semantic matching. Returns up to `limit` results ordered from most to least relevant. Search does not support pagination. `is_truncated` indicates that additional results were found. New or updated notes may be missing until indexing completes. Changing `limit` can change the ranking. Use the list endpoint to retrieve all notes and the get endpoint to read note content. Requires the `blinq:notes:read` scope. # List workspaces Source: https://docs.blinq.me/api-reference/workspaces/list-workspaces /api-reference/openapi.json get /v1/workspaces Returns every workspace the authenticated user belongs to, including member workspaces, in one response without pagination, filters, or a specified order. An empty array means the user belongs to no workspaces. Use a workspace's `id` to list or retrieve contacts. The `role` is the API key owner's role in that workspace. Membership alone does not grant contact-list access; the contact endpoints enforce their own permissions, and workspace discovery is only needed when the workspace ID is not already known. Requires the `blinq:identity:read` scope. # Blinq features Source: https://docs.blinq.me/features Explore the Blinq platform: digital business cards, event lead capture, contact management, and more. > **[Campaigns](/features/campaigns)** > > Attribute captured contacts to specific events and initiatives, with goal tracking and CRM sync. > **[Contacts](/features/contacts)** > > Capture, enrich, and organize every connection in Blinq. > **[Custom lead form](/features/custom-lead-form)** > > Set which details a new connection fills in when they receive a card, configured for each template or campaign. > **[Field mapping](/features/field-mapping)** > > Map Blinq contact fields to your CRM and customize the default field mappings for each integration. > **[Blinq MCP](/features/mcp)** > > Set up Blinq MCP to query your Blinq network from your favorite AI tools like Claude and ChatGPT. > **[Tags](/features/tags)** > > Categorize and segment contacts using contact, workspace, and campaign tags. > **[Team templates](/features/team-templates)** > > Define the layout, branding, and field configuration of every card in your workspace from a central template. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq campaigns Source: https://docs.blinq.me/features/campaigns Attribute captured contacts to specific events and initiatives, with goal tracking and CRM sync. ## Overview Campaigns lets teams attribute every contact they capture to a specific event or initiative. When a team sets up a campaign with a date range, location and assigned members, the campaign automatically tags every contact captured within that window. Teams can set goals, assign members, add tags and connect campaigns to a CRM. ## CRM integrations Campaigns integrates with CRM platforms so contact and attribution data flows through after every event, with no post-event data entry required. ### Campaigns with HubSpot When a campaign is connected to HubSpot, contacts captured during the campaign sync to a HubSpot list along with their attribution data. Contact details and event context flow into HubSpot automatically. Blinq Campaigns can be linked to corresponding HubSpot Campaigns directly. ### Campaigns with Salesforce When a campaign is connected to Salesforce, contacts sync with their campaign attribution attached. Contact details and attribution data flow into Salesforce in real time. Blinq Campaigns can be linked to corresponding Salesforce Campaigns directly. ### Campaigns with Dynamics When a campaign is connected to Microsoft Dynamics, contacts captured during the campaign sync with their attribution data. ## Creating a new campaign You can create a campaign from the Campaigns section of your Blinq workspace. **1. Start a new campaign** Go to **Campaigns** in the Blinq dashboard and click **+ New campaign**. **2. Add campaign details** Fill in the campaign details: campaign name, date & time, location... **3. Set goals** Set campaign goals/targets for your campaign to track progress. **4. Add team members** Add the team members who'll be attending and capturing leads. **5. Add a tag** Add a tag that will be automatically added to leads that need to be captured. **6. Configure lead capture (optional)** Optionally set up a lead template form to ask specific, set questions during your event, scan attendee badges with Cvent, or connect to your CRM to configure a leads export. **7. Review and launch** Review & launch, then click **Launch campaign**. > [!NOTE] > > Once the campaign is active, any lead scanned by an assigned team member during the event dates is automatically attributed to it! ### Campaign details When creating a campaign, you'll enter the campaign name, date range, time zone and location. These details define the window during which contacts are attributed to the campaign. ### Goals Goals let you set a lead generation target for the campaign. You can enter a target value to track progress against your campaign objectives. ### Team members Team members are the reps you assign to a campaign. You can add or remove team members when creating or editing a campaign. ### Campaign tags Campaign tags let you organize and filter campaigns in your workspace. You can add one or more tags when creating or editing a campaign. ## Campaign management From the campaign management view, you can add and remove contacts from a campaign. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq contacts Source: https://docs.blinq.me/features/contacts Capture, enrich, and organize every connection in Blinq with personal and company contacts, AI enrichment, notes, tags, and exports. ## Overview Every connection lands in Contacts. Blinq captures the details, enriches them, and keeps them ready to act on. Contacts can be created several ways: * **Card exchange:** when a Blinq card is shared, Blinq creates the contact automatically. * **Scanning:** scan a physical business card, event badge, or QR code using the universal scanner. * **Shared back:** a new connection fills in their own details through your card link. * **Manual entry:** add a contact directly from the app or dashboard. All contacts are personal by default. Contacts captured through a team card are automatically shared with the team and appear as company contacts. ## Company contacts > [!NOTE] > > Contacts created through a team card are automatically shared with your team. No manual sharing required. The **All company contacts** view is a directory of every contact visible to your team workspace. It includes: * Contacts captured through any team member's Blinq card. * Personal contacts shared with the workspace. Blinq integrations export contacts that are visible in **All company contacts**. ## Personal contacts The **My contacts** view shows all contacts owned by an individual user: ones captured or created manually. Contacts shared with the workspace also remain visible here. Personal contacts aren't visible to your team, and aren't exported to integrations. You can share a personal contact with your team at any time. ### Sharing a personal contact with your team **1. Open the contact** Open the contact you want to share from the contact list. **2. Open the Share menu** On the web dashboard, open the **Share** menu. On mobile, tap **More…**. **3. Share with your company** Choose the option to share the contact with your company. After sharing, the contact appears in **All company contacts** and becomes eligible for integration exports. ## AI contact enrichment When a new contact lands in Blinq, AI enrichment fills in missing details, allowing for richer context with your connections. Enrichment requires at least one of: a work email, a full name and company, or a LinkedIn URL. If those details aren't present, Blinq prompts for the missing information before running enrichment.\ \ **Blinq checks 25+ live data partners in order of reliability**, with AI search running when the sources don't return a result. Every email is verified before it's saved to the contact. If a detail can't be verified, the field is left blank. All enriched fields remain editable.\ \ Enriched details can include: job title, company, LinkedIn profile, profile photo, phone numbers, and verified emails (available on Pro, Business, and Enterprise plans). ### Disabling AI enrichment Owners and Admins can turn off AI contact enrichment for the entire workspace: **1. Go to Settings** In the Blinq dashboard, go to **Settings**. **2. Open the Workspace tab** Select the **Workspace** tab. **3. Scroll to the bottom of the page** Scroll down to the enrichment settings. **4. Toggle off Contact enrichment** Toggle off **Contact enrichment**. ## Contact notes Notes can be added to any contact from the app or dashboard. Notes sit on the individual contact record and stay visible whenever that contact is opened. When a CRM integration is active, notes export directly to the connected platform. ## Contact tags > [!NOTE] > > Read more about tagging here. [View article →](/features/tags) Tags make it easy to segment, filter, and report on contacts by source or activity. You can tag contacts at the point of capture or post-capture by editing the contact record. ## Exporting contacts > [!NOTE] > > Only Owners and Admins can view **All company contacts**. Whether team members can export their own contacts is a per-integration setting — see the configuration page for each integration. From **All company contacts**, contacts can be exported as a CSV or pushed to any enabled integration. **To export:** **1. Open the Contacts view** In your Blinq Business dashboard, open the **Contacts** view. **2. Select contacts** Optionally, select the specific contacts you want to export. **3. Click Export contacts** Click **Export contacts** in the top right corner. **4. Choose your format** Choose **Download CSV** or select your integration. If no contacts are selected, Blinq exports all eligible contacts. ### Sync & Export status The **Sync & Export** column shows the status and last export timestamp for each enabled integration. Use it to see which contacts have synced and which are still pending. ## Contact preservation When a team member is removed from the workspace, Blinq keeps the contacts they captured in **All company contacts**. Deleting a team card or member doesn't delete the contacts associated. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq custom lead form Source: https://docs.blinq.me/features/custom-lead-form Set which details a new connection fills in when they receive a card, configured for each template or campaign. ## Overview > [!NOTE] > > The custom lead form is available on Blinq Business and Enterprise. [View pricing →](https://blinq.me/pricing) The custom lead form sets which details a new connection fills in when they receive a card. Admins build it once and apply it across a workspace, so cards collect the same qualifying information every time. Admins configure the form at the template level and the campaign level. They can customize the fields, the form heading, and the button text, and they can require the form before the card is shown. ## Add a custom lead form to your card template > [!NOTE] > > Each template supports one custom lead form. Admins can attach a custom lead form directly to a card template, applying the custom form to all leads captured by any card on the template. In the **Team templates** section of the dashboard, you can add a custom lead form when you edit or create a template. In the template editor, select the **Custom Lead Form** tab. ## Add a custom lead form to your campaign > [!NOTE] > > Each campaign supports one custom lead form. Admins can attach a custom lead form directly to a campaign, applying the custom form to all leads captured while the campaign is active. In the **Campaigns** section of the dashboard, open the campaign details (**View campaign**) and custom lead forms can be added under the **Event lead capture** section. ## Form priority Blinq applies forms in priority order. A custom lead form added to a campaign takes priority over a custom lead form added to a template. Custom lead forms always take priority over the default Blinq form. A campaign form applies for the length of the campaign. If a member is in two overlapping campaigns, the custom form for the most recently created campaign is shown. When a campaign ends or a member leaves it, the form falls back to the member's template form, or to the Blinq default form if no template form is set. ## Lead capture mode (show the form first) By default, a recipient sees your Blinq card first and can fill in the form afterward. Turning on **Enable Lead Capture** requires the recipient to complete the form before they can view the card. ## Making a custom lead form **1. Open the editor** Open the custom lead form editor from either the campaign view or template editor. **2. Set lead capture mode** Toggle **Enable Lead Capture** on or off. **3. Set the skip button** Toggle **Add Skip form button** on or off. **4. Set the heading and button** Set a custom form heading and button text, or leave them default. **5. Add and configure fields** Add the fields you want to collect: set their type, label them, and drag them into the order you want. The **Identifying field** and **Primary contact** fields are always required. Toggle your other fields as Required, or leave them as optional. **6. Save your changes** As you edit, a live preview shows how the form will look to a recipient. To start over, select **Restore default form**. ## Fields and customization options Every form includes a required **Name** field and one primary contact field, either **Email** or **Phone**. Admins choose which other details to collect, set the label shown for each field, and drag fields to reorder them. Standard fields: * **Email** * **Phone** * **Job title** * **Company** Custom field types: * **Custom text** for a free-text answer. * **Dropdown** for a single choice from a list of 2 to 50 options, each up to 80 characters, so you can mirror your CRM picklists. * **Checkbox** for a checked or unchecked option. A custom form can have up to 100 fields. Custom fields are saved to the workspace, so admins can reuse them on other forms. Any field except a checkbox can be marked **Required**. ## Where captured details appear When someone submits the form, their answers are saved to the contact in Blinq. The submitted details appear in the contact view on the dashboard, iOS, and Android, alongside the rest of the contact's information. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq field mapping Source: https://docs.blinq.me/features/field-mapping Map Blinq contact fields to your CRM and customize the default field mappings for each integration. ## Overview Field mapping is built into each native CRM integration and is configured from that integration's settings page in your workspace. Field mapping is available on all native CRM integrations: * HubSpot * Salesforce * Dynamics * GoHighLevel * Marketo * Zoho CRM * monday.com * Pipedrive ## Using the field mapper **1. Open field mapping** Go to **Settings → Integrations**, then select **Configure** next to your CRM to open the field mapper. **2. Add a new mapping** Select **Add mapping** to create a new row. **3. Select the Blinq field** In the **Blinq field** column, choose the field you want to export. You can select any of the [supported Blinq fields](#supported-blinq-fields): a standard contact field or a custom form response. **4. Select the CRM field** In the **CRM field** column, choose the destination field in your CRM. **5. Save** Select **Save** to apply the mapping. New contacts sync using the updated configuration. ## Field mapping requirements > [!NOTE] > > First name, last name, and email are required fields in the field mapper. These can't be removed or edited. Text-based fields are the most widely supported custom field type. Other types are also supported, including dropdown menus and checkboxes from custom lead forms, and additional field types available on specific CRM platforms. Most field types, including checkboxes and dropdowns, can be mapped into a text field. You can't always map a text field into a checkbox or dropdown. ## Supported Blinq fields Two groups of Blinq fields can be mapped to your CRM: * **Standard contact fields**: a fixed set of card and contact fields: * First name * Last name * Job title * Company name * Primary email * Secondary email * Phone * Mobile phone * Website * LinkedIn * **Custom form responses**: any custom field or question from a custom lead form, including text, dropdown, and checkbox responses. ## Field mapping defaults When a CRM integration is created, Blinq loads a default set of field mappings as a baseline. You can customize this configuration after setup using the field mapping menu. > [!NOTE] > > The default mappings differ by CRM. Not every Blinq field is mapped by default on every integration, so review the loaded defaults after setup and add any mappings you need. ## Removing a field mapping To remove a mapping, select the delete icon on the row you want to remove, then save your changes. The required fields (first name, last name, and email) can't be removed. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq MCP Source: https://docs.blinq.me/features/mcp Set up Blinq MCP to query your Blinq network from your favorite AI tools like Claude, ChatGPT, and Microsoft 365 Copilot. ## Overview > [!NOTE] > > Blinq MCP is available on **Pro**, **Business**, and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Learn everything you need to connect and start using Blinq MCP: what it is, what your AI tool can do once it's connected, how permissions and privacy work, and how to set it up. Once connected, you can ask Claude, ChatGPT, or Microsoft 365 Copilot about your Blinq contacts, conversations, and notes — so you can open doors, build relationships, and create new opportunities from the people you've met. ## What is Blinq MCP? **Blinq MCP** is a connection between your Blinq account and AI tools like Claude, ChatGPT, and Microsoft 365 Copilot. It gives your AI tool access to your Blinq contacts and meeting notes, so you can ask about them in plain language and get answers from your own data. ## Why use Blinq MCP? * **Your network, in the tool you already work in:** Your contacts and notes are already where you're working, whether that's Claude, ChatGPT, or Microsoft 365 Copilot. No exporting a CSV, or copy-pasting conversation notes, or alt-tabbing back to Blinq to check something. * **Workspace-wide answers, sans dashboard:** Admins can pull the whole team's captures and conversations and stay close to their performance, spotting where coverage is thin and where an opportunity is stacking up. * **Power your workflows with real context:** Go beyond getting answers. Your Blinq network gives your AI tools the context they need to build, act, and carry insights into any workflows you're running, without starting from scratch. ## What can you do with Blinq MCP? Each example below is a prompt you can type straight into your connected AI tool. **For anyone with a Blinq account:** | If you want to... | Ask Blinq MCP | What you get | | - | - | - | | Get up to speed on someone | *"Tell me about this contact."* | Their company, role, and your previous conversation, pulled from one question. | | Recall who you met and when | *"Who did I meet at SaaStr last month?"* | Remember who you added during an event, without exporting a thing. | | Follow up faster and better | *"Draft me a follow up based on our last coffee chat."* | Send personalized follow-up messages based on your conversation summaries. | **For workspace admins (Business and Enterprise):** | If you want to... | Ask Blinq MCP | What you get | | - | - | - | | Spot gaps early | *"Which SaaStr leads haven't we followed up with yet?"* | A list of everyone who hasn't heard from you yet, so nothing slips through. | | Get field intel | *"Top 3 objections that came up at the booth last week?"* | Patterns in how prospects are responding, pulled straight from field transcripts. | | Prove event ROI | *"How much pipeline came out of Dreamforce?"* | A pipeline number tied to each event, without pulling up a dashboard. | ## Which tools does Blinq MCP include? All Blinq MCP tools are read-only. These are the tools your AI assistant can call: | Tool | What it does | | - | - | | Get contact (`get_contact`) | Get full details for a specific contact by ID (name, company, job title, and more). | | List contacts (`list_contacts`) | List contacts across your personal and team workspaces. | | List notes (`list_notes`) | List your AI Notetaker notes, newest first. | | Get note (`get_note`) | Get the full detail of a specific note. | | Search notes (`search_notes`) | Keyword search across your notes, ranked by relevance. | | Query notes (`query_notes`) | Answer a natural-language question, or summarize and recap, from your notes. | | List workspaces (`list_workspaces`) | List the Blinq workspaces you can access. | ## How do permissions and privacy work? Every Blinq MCP tool is read-only, so connecting it is low-risk. You can switch individual tools on or off from your AI tool's settings, and disconnect Blinq at any time. You only ever see data you already have access to in Blinq, because the connection uses your own login. Admin visibility covers business contacts in the workspace and their saved text notes. Contacts a team member captures into their personal cards stay private to them, along with any text notes or AI Notetaker notes linked to those personal contacts. Admins can see team members' AI Notetaker notes only when the note is linked to a business contact in a workspace they admin or own, and only if AI note syncing is turned on. This is controlled by a workspace-level toggle in workspace Settings (on by default), which syncs AI notes from team members' contacts up to the business contact. When you connect Blinq to an AI tool, the contacts and notes it reads are shared with that provider to answer your questions. Meeting transcripts can hold sensitive detail, so it's good to be deliberate about which tools you connect. See [Blinq's privacy policy](https://blinq.me/legal/privacy-policy) for the full picture. Blinq MCP is for reading your data from AI tools. To sync captured contacts into your CRM automatically, use Blinq's [Salesforce](/integrations/salesforce) and [HubSpot](/integrations/hubspot) integrations, among [others](/integrations). ## How do I connect Blinq MCP? You connect Blinq MCP with OAuth, using your existing Blinq account, so there's no separate API key to manage. **From your AI tool:** open its connector settings (in Claude, that's **Settings → Connectors**; in ChatGPT, that's **Settings → Plugins → Browse directory**). Search for Blinq, then sign in and authorize. **From Microsoft 365 Copilot:** install [Blinq for Microsoft 365 Copilot](https://marketplace.microsoft.com/en-us/product/WA200012579?tab=Overview) from the Microsoft marketplace, then select Blinq in the Copilot **Agents** panel and sign in when prompted. You'll need a Microsoft 365 Copilot license, and some organizations require an admin to approve the app first. Blinq doesn't appear in Copilot's agent store search yet, so use the marketplace link to install it. Full step-by-step instructions for each provider are in our [Help Center](https://support.blinq.me/en/articles/76274-blinq-mcp-bring-your-contacts-into-claude-chatgpt-and-more). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq tags Source: https://docs.blinq.me/features/tags Understand the types of tags in Blinq and how they help categorize and segment contacts. ## Overview Tags let teams categorize and segment contacts in Blinq. They can be applied at the point of capture or when editing a contact record, making it easy to filter and report on contacts by source or activity. Blinq has three types of tags, each with a different scope. ### Contact/Personal tags Contact tags are added by individual users to their own contacts. They can be created and applied directly on the contact. ### Workspace tags Workspace tags are shared across the workspace. Admins create these tags in **Settings → Tags** and they appear as a pick-list, where they can be applied to contacts. ### Campaign tags Campaign tags are applied automatically when a contact is captured through a Blinq campaign. Use campaign tags to quickly identify which campaign the contact came from. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq team templates Source: https://docs.blinq.me/features/team-templates Define the layout, branding, and field configuration of every card in your workspace from a central template. ## Overview Team templates give workspace admins a central place to define the layout, branding, and field configuration of digital cards. When an admin creates and publishes a template, team members can use it to build their own cards. Shared content stays consistent across every card in the workspace, while individual fields let each person personalize their details. ## Template view The Templates page lists every template available in the workspace. From here, admins can see and manage the full template library. Each template in the list has four actions available: * **Edit:** opens the template in the editor to update its layout, fields, or branding. * **Duplicate:** creates a copy of the template as a starting point for a new one. * **Delete:** removes the template from the workspace permanently. * **Create card:** generates a new card directly from the template. ### Template invite link Each template has a unique invite link. Sharing the link lets people create cards from that template without inviting each team member one by one. ## Creating a template Admins create new templates from the Templates page. Admins can start a template from a blank layout, or from a sample layout that includes fields and features already in place. Sample layouts are fully editable. ### Naming and management Admins name each template when they create it. The name appears in the template list and helps identify which template to use when creating a card. By default, a card inherits its template's name. Admins can duplicate, edit, or delete templates. ## Field types: shared and individual Cards built from a template can include two types of fields: shared and individual. Shared fields contain the same value on every card created from the template. Admins set shared field content in the template editor, and that content appears on every card using the template. Each team member completes their own individual fields. These fields let team members enter their own contact details or other information specific to them. ### Field visibility Admins can hide or show each field using the eye icon next to it. Hidden fields don't appear in a team member's card editor, so team members can't add them to their card. A master toggle at the top of the field list shows or hides all fields at once. ### Layout The template editor controls how fields are arranged on the card. Admins set the layout when they create the template (sample or blank) and can adjust it at any time from the template editor. ### Image types Templates support three image types. The card layout options depend on how many images the template uses: * **Profile picture** (recommended ratio 1:1) * **Company logo** (recommended ratio 16:9) * **Cover image** (recommended ratio 16:9) ## Identity, branding, and customization Templates include branding controls so every card in the workspace reflects the organization's visual identity. ### Custom font Admins add custom fonts in **Settings → Workspace**, or upload them directly from the template editor. Blinq accepts TTF and OTF font files. ### Color and theme The color picker in the template editor sets the color of icons on the card. Admins can choose from preset color options or set a custom color using the color picker or by entering a custom hex value. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # SCIM provisioning with Microsoft Entra ID (Azure AD) Source: https://docs.blinq.me/identity/entra Create, update, and deactivate Blinq users and their digital business cards from Microsoft Entra ID, formerly Azure Active Directory, using SCIM 2.0. > [!NOTE] > > SCIM provisioning is available on **Enterprise** plans, and is enabled per workspace. [Talk to your account team](mailto:support@blinq.me) to switch it on. Once it's enabled, generating your credentials is self-serve in the Blinq dashboard. SCIM provisioning connects Microsoft Entra ID to Blinq so your directory drives your team's digital business cards. Microsoft Entra ID was previously called **Azure Active Directory (Azure AD)**. If your team still calls it Azure AD, it's the same product and these pages apply. Assign a user to Blinq in Entra and their account and card are created automatically, pre-filled from their directory profile. Update the directory and the card follows. Remove the user and their access is revoked. Blinq is a pre-built app in the Microsoft Entra gallery, so the attribute mappings arrive pre-populated. ## Prerequisites * An **Admin** or **Owner** role in your Blinq workspace, on an Enterprise plan with SCIM enabled. * An Entra role that can manage enterprise applications: **Application Administrator**, **Cloud Application Administrator**, or **Global Administrator**. * No Microsoft developer account is required. SAML SSO and SCIM provisioning are configured separately. These pages cover SCIM only. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Create Blinq users and cards from the directory | Yes | — | | Sync attribute changes | Yes | On the provisioning cycle, roughly every 40 minutes | | Deactivate users | Yes | See [How provisioning works](/identity/how-provisioning-works) | | Apply team templates at provisioning time | Yes | With optional attribute filters | | Group provisioning | No | Users in an assigned group are provisioned individually | | Profile photos | No | Entra doesn't expose them over SCIM — added by the card owner or an admin | Sync is one-way, from Entra ID to Blinq. Changes made in Blinq don't flow back to your directory. ## Documentation for Entra ID provisioning > **[Connecting Entra ID](/identity/entra/connecting-entra)** > > Generate credentials in Blinq, add the gallery app, and confirm the connection. > **[Configuring Entra ID](/identity/entra/configuring-entra)** > > Choose which attributes to send, set your scope, and assign your first users. > **[Configuring Blinq](/identity/entra/configuring-blinq)** > > Control templates and activation emails for provisioned users. > **[Field reference](/identity/entra/field-reference)** > > Which directory attributes Blinq accepts, and which SCIM schema they belong to. > **[Troubleshooting](/identity/entra/troubleshooting)** > > Connection failures, values that don't appear, and provisioning that stops. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for Entra ID Source: https://docs.blinq.me/identity/entra/configuring-blinq Control which templates apply to provisioned cards and when activation emails are sent. Once Entra ID is connected, the **Card Settings** area of **Settings → Integrations → Team Card Provisioning** controls what provisioned users receive. | Setting | Behavior | | - | - | | Templates | Choose which team templates apply to newly created cards, with optional filters on directory attributes. For example, apply Template A when `department` is Marketing or Sales. | | Activation email | On: users are emailed as soon as they're provisioned. Off: no email is sent, and admins send activation emails manually from the **Team Cards** page. | ## Viewing a provisioned user To see a provisioned user's card, open **Team Cards** in the Blinq dashboard, select their row, and click **Edit**. For how provisioned cards behave once they exist — field locking and linking, template precedence, and what happens when a user is deactivated — see [How provisioning works](/identity/how-provisioning-works). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Entra ID Source: https://docs.blinq.me/identity/entra/configuring-entra Choose which attributes Blinq receives, set your provisioning scope, and assign your first users. ## Review the attribute mappings Open **Provisioning → Mappings → Provision Microsoft Entra ID Users**. The gallery app pre-populates these mappings. Delete any attribute you don't want sent to Blinq. > [!WARNING] > > **Check what your directory is putting in the phone fields.** Map only one of `telephoneNumber` and `mobile` to avoid stale-value conflicts. Check whether a fax number is present too — a fax number in the directory feed can end up on a card where a phone number was expected. ## Set your provisioning scope Under **Settings**, choose **Sync only assigned users and groups**. This lets you pilot with a small group before rolling out more widely. Set **Provisioning Status** to **On** and save. ## Assign users On the app's main page, open **Users and groups → Add user/group** and assign the people you want provisioned. Assigned users are picked up on the next provisioning cycle, up to 40 minutes, or immediately if you use on-demand provisioning. ## Validate with a test user **1. Provision a single test account** Assign one test user, then use **Provisioning → On-demand provisioning** to push them straight away. **2. Check the result in Blinq** Confirm the user and their card exist, with the attributes you expect. **3. Change an attribute** Update something in Entra — job title is easy to check — and confirm it flows through on the next sync. **4. Read the provisioning logs** Open **Provisioning → Provisioning logs** for per-user create and update results. > [!TIP] > > **Your mappings are working.** You can now assign the rest of your users. > [!WARNING] > > Use a dedicated test account rather than a real employee's, and turn activation emails off in Blinq while you're testing so test users aren't emailed. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Entra ID to Blinq Source: https://docs.blinq.me/identity/entra/connecting-entra Generate SCIM credentials in Blinq, add the Blinq gallery app in Entra, and confirm the connection. **1. Generate credentials in Blinq** * In the Blinq dashboard, select your workspace, then **Settings** and the **Integrations** tab. * Find the **Team Card Provisioning** section. It shows the tenant URL Entra needs. * Click **Generate** to create the secret token, and copy both values. **2. Add the Blinq app in Entra** * Go to [entra.microsoft.com](https://entra.microsoft.com) and open **Identity → Applications → Enterprise applications → New application**. * Search for **Blinq** and click **Create**. **3. Enter the credentials** * Open the Blinq app and select **Provisioning**. * Set **Provisioning Mode** to **Automatic**. * Under **Admin Credentials**, paste the Tenant URL and Secret Token from Blinq. **4. Test the connection** Click **Test Connection**. You should see a success message within a few seconds. Click **Save**. > [!TIP] > > **Entra ID is connected to Blinq.** Next, [choose what gets sent and who gets provisioned](/identity/entra/configuring-entra). > [!NOTE] > > Use the gallery application. A custom or non-gallery app won't have the pre-configured attribute mappings and isn't supported. > [!WARNING] > > Generating a new token immediately invalidates the previous one and breaks any existing connection. Active tokens are listed, and can be deleted, on the **Security** tab in Settings. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Entra ID field reference Source: https://docs.blinq.me/identity/entra/field-reference Which directory attributes Blinq accepts from Microsoft Entra ID, and which SCIM schema they belong to. > [!NOTE] > > The Blinq gallery app in Entra pre-populates these mappings. You can remove any you don't want to send, but you shouldn't need to add any. ## Attribute mapping | Entra attribute | SCIM field | Schema | | - | - | - | | `userPrincipalName` | `userName` | Core — required | | `Switch([IsSoftDeleted], , "False", "True", "True", "False")` | `active` | Core — required | | `displayName` | `displayName` | Core | | `mail` | `emails[0].value` | Core | | `givenName` | `name.givenName` | Core | | `surname` | `name.familyName` | Core | | `jobTitle` | `title` | Core | | `telephoneNumber` / `mobile` | `phoneNumbers` | Core — map one, not both | | `companyName` | `organization` | Enterprise extension | | `department` | `department` | Enterprise extension | Enterprise-extension attributes are sent under `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`. To control which card fields the directory manages, see [How provisioning works](/identity/how-provisioning-works). ## Profile photos Blinq can sync profile images over SCIM, but Entra ID doesn't expose them. Photos are added to a card by the card owner or a workspace admin. > [!NOTE] > > Microsoft's [Blinq provisioning tutorial](https://learn.microsoft.com/en-us/entra/identity/saas-apps/blinq-provisioning-tutorial) lists a broader attribute set than this page, including employee number and additional email and address types. This page is the authority on what Blinq does with an attribute once it arrives. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Troubleshooting Entra ID provisioning Source: https://docs.blinq.me/identity/entra/troubleshooting Connection failures, values that don't reach the card, and provisioning that stops unexpectedly. | Symptom | Cause and fix | | - | - | | Test Connection fails | Wrong tenant URL or token. Regenerate the token in Blinq and re-enter both values in Entra. | | Provisioning job stuck in Quarantine | The token has expired or been revoked. Generate a new token in Blinq and update it in Entra. | | Provisioning stopped after a staff change | The token belongs to the admin who created it. If that admin was deactivated or lost the admin role, a current workspace admin must generate a new token and re-enter it. | | A user isn't appearing in Blinq | The sync cycle hasn't run yet. Use on-demand provisioning to push them immediately, and check that Provisioning Status is **On**. | | A phone number won't update | Both `mobile` and `telephoneNumber` are mapped to the same card field. Entra only re-sends on a real source change, so remove one mapping and make a small edit to the one you keep. | | A directory value isn't on the card | Check three things in order: the attribute has an active mapping in Entra, the applied team template has a field for it, and the field on the card is still **linked**. A field that was hand-edited in Blinq becomes unlinked and stops accepting directory updates. | | A field shows as Linked but the value is stale | Contact Blinq support with the user's email address and the field. Don't assume the change didn't arrive from your directory — it may have reached Blinq without reaching the card. | | The wrong number appears on a card | Check whether your directory is populating a fax number. If it is, remove that mapping in Entra. | | A template didn't apply | Set the default template under **Team Card Provisioning** card settings. Template choices made during a bulk-invite CSV upload don't carry over to SCIM-provisioned users. | | A user signed in first and landed on a Free personal account | Contact Blinq support for an account merge — don't delete the account. Enforced SSO prevents this by directing domain users into your workspace. | ## Reading the provisioning logs In Entra, open **Enterprise applications → Blinq → Provisioning → Provisioning logs**. Logs show each user operation, whether it succeeded, and which attributes were sent. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # How SCIM provisioning works Source: https://docs.blinq.me/identity/how-provisioning-works What Blinq does when your directory creates, updates, or deactivates a user, whichever identity provider you use. > [!NOTE] > > SCIM provisioning is available on **Enterprise** plans, and is enabled per workspace. [Talk to your account team](mailto:support@blinq.me) to switch it on. Blinq exposes a SCIM 2.0 endpoint that your identity provider pushes changes to, authenticated with a bearer token you generate in Blinq. Your directory is the source of truth, and Blinq never pushes back to it. This page covers what happens inside Blinq. It applies the same way whether you provision from Microsoft Entra ID or Okta. ## Before you provision anyone Set up the Blinq side first. Provisioning creates cards immediately, so it's much easier to get the template right beforehand than to correct cards afterwards. **1. Create your team template** Build the template that provisioned cards will use, then lock or hide any card fields you don't want the directory to control. **2. Attach it in Card Settings** Go to **Settings → Integrations** and attach the template under the provisioning card settings. **3. Turn activation emails off while you test** This keeps test users from being emailed. Turn it back on when you're ready to roll out. > [!WARNING] > > **Provision people who aren't already in your workspace.** SCIM creates users — there's no documented step that reconciles someone who was already added by hand. Don't bulk-delete existing members to make way for provisioning either; check them individually instead, and ask Blinq support how your workspace should handle the overlap. ## Creating a user Assigning a user to Blinq in your directory creates their Blinq account and a digital business card. Blinq populates the card from their directory profile, applies any matching team template, and — if the activation email is switched on — emails them so they can activate their account. ## Updating a user When an attribute changes in your directory, the change flows to the card on the next sync. Only attributes with an active mapping are updated. ## Deactivating a user Unassigning a user in your directory, or disabling or deleting their directory account, deactivates them in Blinq. Deactivated users don't count toward your Blinq user count, so the seat is freed for someone else. ## Reactivating a user If you re-assign someone who was previously removed, Blinq matches them on email address and reactivates them rather than creating a second account. ## Fields the directory manages Each field on a provisioned card can be **locked**, so the card owner can't change it, and **linked**, so later directory changes flow through to it. You control this per field on the team template you attach for provisioning. If an admin edits a linked field in Blinq and saves, that field becomes **unlinked** — the change stands, and later directory updates won't overwrite it. Removing a lock so the card owner can edit a field has the same effect. > [!WARNING] > > **Unlinking is per field and it's easy to do by accident.** A card where several fields have been hand-edited will quietly stop accepting directory updates for those fields, even though the rest of the card keeps syncing. If directory values aren't appearing on a card, check which of its fields are still linked before looking anywhere else. ## Team templates Team templates apply to newly created cards only, and can be filtered on directory attributes — for example, apply the Sales template when `department` is Sales. After a user has been provisioned, assign templates to their card manually from the dashboard. Template values take precedence over directory values. If your directory says the company is `Blinq` and the applied template says `Blinq Inc.`, the card shows `Blinq Inc.` > [!WARNING] > > Precedence isn't the only way a directory value can go missing. If the applied template has no field for an attribute, the value simply won't appear on the card. Job title is the most common case. ## Activation emails With the activation email switched on, users are emailed as soon as they're provisioned. With it off, no email is sent and admins send activation emails manually from the **Team Cards** page. ## Who owns the SCIM token Provisioning stops if the admin who generated the SCIM token is deactivated or loses the admin role. A current workspace admin then has to generate a new token and re-enter it in your identity provider. > [!WARNING] > > Because SCIM is often what deprovisions people, it's possible to break your own provisioning by offboarding the admin who created the token. Check who owns it before removing an administrator. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # How SAML SSO works Source: https://docs.blinq.me/identity/how-sso-works What changes when your team signs in to Blinq through your identity provider, and what to set up before you start. > [!NOTE] > > SSO is available on **Enterprise** plans. Your domains are enabled by the Blinq team. [Talk to your account team](mailto:support@blinq.me) to get started. Blinq supports single sign-on over **SAML 2.0**. Your identity provider holds your team's accounts and credentials, and Blinq acts as the service provider. This page covers what happens inside Blinq. It applies the same way whichever identity provider you use. ## Before you start **1. Register your domains with Blinq** Email [support@blinq.me](mailto:support@blinq.me) with the domains you want covered and an example address for each. Blinq adds them for you — there's no self-serve screen for this. You can register more than one domain, including subdomains, and add or remove them later. **2. Confirm you're the workspace Owner** The SAML settings are reached from the Blinq dashboard under **Settings → SAML**. **3. Open Blinq and your identity provider side by side** Setup copies values in both directions, so keep both open in separate tabs. > [!WARNING] > > **Register your domains first.** Until at least one domain is registered, the SAML settings show an upgrade prompt — even on an Enterprise plan. If you're on Enterprise and being told to upgrade, a missing domain is the reason, not your subscription. ## Configuring safely > [!WARNING] > > **Stay signed in to Blinq while you configure SSO, and test in a separate browser or a private window.** A misconfigured certificate or URL can lock you out of the workspace you're editing, and only Blinq support can switch enforcement back off. ## What enforcement changes Enforcement is the switch that makes SSO mandatory. It's checked on Blinq's side against the email domain someone signs in with. | Behaviour | With enforcement on | | - | - | | Sign-in options for your domains | Only **Continue** — the password and email code options disappear | | Password and email code sign-in | Blocked for addresses on your registered domains | | Claiming a card for the first time | Also goes through your identity provider | | People whose address isn't on your domains | Unaffected — they keep signing in as before | | Multi-factor authentication | Handled by your identity provider, not by Blinq | Because enforcement is matched on the email domain, someone who signs in with an address outside your registered domains isn't routed through SSO at all. ## Claiming a card under enforced SSO Enforcement applies from the very first time someone accesses Blinq, not only on later sign-ins. Claiming a card uses the same sign-in path as everything else, so a new team member on one of your registered domains is sent to your identity provider when they follow their activation link. There's no separate password or email code step for new joiners to route around. > [!NOTE] > > **Allowed email domains and SAML SSO are mutually exclusive.** The allowed-domains setting, which limits who can join by invite link, is hidden once SAML SSO is enabled on a workspace. ## Starting from your identity provider By default, people start at Blinq: they enter their email address, and Blinq redirects them to your identity provider to sign in. You can also let people launch Blinq from a tile in their identity provider's app dashboard. This is an opt-in setting, and Blinq support enables it for your workspace. > [!WARNING] > > **Launching from the app tile currently requires enforcement to be switched on as well.** With enforcement off, that route returns a server error rather than signing the person in. If you want the app tile without enforcing SSO for everyone, talk to support before rolling it out. ## Setup guides > **[Microsoft Entra ID](/identity/sso/entra)** > > Add the Blinq enterprise application and exchange SAML details. > **[Okta](/identity/sso/okta)** > > Create a SAML 2.0 app integration and exchange SAML details. > **[Google Workspace](/identity/sso/google-workspace)** > > Create a custom SAML app and exchange SAML details. > **[Troubleshooting](/identity/sso/troubleshooting)** > > Sign-in failures, certificate errors, and people who can't reach the settings. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # SCIM provisioning with Okta Source: https://docs.blinq.me/identity/okta-scim Provision Blinq users and their digital business cards from Okta. Setup is done with the Blinq team. > [!NOTE] > > SCIM provisioning is available on **Enterprise** plans, and is enabled per workspace. [Talk to your account team](mailto:support@blinq.me) to switch it on. Blinq supports user provisioning from Okta over SCIM 2.0. Assign a user in Okta and their Blinq account and digital business card are created automatically; update their Okta profile and the card follows; unassign them and they're deactivated in Blinq. Unlike the [Microsoft Entra ID integration](/identity/entra), which you can set up yourself from the Entra gallery, **Okta provisioning is configured with help from the Blinq team**. Email [support@blinq.me](mailto:support@blinq.me) to get started and they'll work through it with your Okta administrator. ## What to have ready * An **Admin** or **Owner** role in your Blinq workspace, on an Enterprise plan with SCIM enabled. * Okta administrator access, with permission to add and configure applications. * A decision on which users or groups to provision first. A small pilot group is the easiest way to start. ## Prepare the Blinq side Do this before the setup call. Provisioning creates cards immediately, so it's much easier to get the template right first than to correct cards afterwards. **1. Create your team template** Build the template that provisioned cards will use, then lock or hide any card fields you don't want the directory to control. **2. Attach it in Card Settings** Go to **Settings → Integrations** and attach the template under the provisioning card settings. **3. Turn activation emails off while you test** This keeps your test users from being emailed. Turn it back on when you're ready to roll out. ## Generate your Blinq credentials You can generate these yourself before the setup call. **1. Open your provisioning settings** In the Blinq dashboard, select your workspace, then **Settings** and the **Integrations** tab. **2. Find Team Card Provisioning** The section shows your tenant URL. **3. Generate the token** Click **Generate**, then copy both the tenant URL and the secret token. The token is shown once. > [!TIP] > > **You have what Blinq support needs** to configure the Okta side with you. > [!WARNING] > > Generating a new token immediately invalidates the previous one and breaks any existing connection. Active tokens are listed, and can be deleted, on the **Security** tab in Settings. ## What the connection looks like Blinq support configures the Okta side with you, but it helps to know what they'll be setting. On the app's **Provisioning → Integration** page: | Setting | Value | | - | - | | SCIM version | 2.0 | | SCIM connector base URL | The tenant URL from your Blinq provisioning settings | | Authentication Mode | **HTTP Header** | | Authorization | **Bearer**, followed by your Blinq secret token | | Supported provisioning actions | Push New Users, Push Profile Updates, and Import New Users and Profile Updates | Leave **Push Groups** and **Import Groups** unchecked — group provisioning isn't supported. Use **Test Connector Configuration** to confirm the connection before you assign anyone. Once the connection is live, assign one or two test users first and confirm their cards look right, then scale up to the rest of your directory. ## Once provisioning is running Provisioned users, cards, team templates, activation emails, and field locking behave the same regardless of which identity provider you use. See [How provisioning works](/identity/how-provisioning-works). Group provisioning isn't supported. Users inside an assigned group are provisioned individually, and group membership isn't represented in Blinq. If something isn't working as expected, see [Troubleshooting](/identity/okta-scim/troubleshooting). > [!NOTE] > > **Using a different identity provider?** Blinq's SCIM service is standards-based — SCIM 2.0 with bearer-token authentication — so other SCIM-capable platforms can connect too. Contact support to discuss anything beyond Okta and Entra ID. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Troubleshooting Okta provisioning Source: https://docs.blinq.me/identity/okta-scim/troubleshooting Connection failures, values that don't reach the card, and users who stay active after being unassigned. Because Blinq support sets up the Okta side with you, they'll work through most of these with you directly. These are the checks that resolve the majority of cases. | Symptom | Cause and fix | | - | - | | Test Connector Configuration fails | The base URL or token doesn't match. Confirm **Authentication Mode** is **HTTP Header** and that the token follows the `Bearer` prefix in the Authorization field. If it still fails, generate a new token in Blinq and re-enter both values. | | Provisioning stopped working after a staff change | The token belongs to the admin who created it. If that admin was deactivated or lost the admin role, a current workspace admin needs to generate a new token and re-enter it in Okta. | | Provisioned cards have no template | No default template is set for provisioning. Attach one under **Team Card Provisioning** card settings. A template chosen during a bulk CSV invite doesn't carry over to users Okta provisions afterwards. | | A phone number is wrong, or shows an internal extension | Blinq shows whatever your directory holds in that field, including four-digit internal extensions. Check the value on the user's Okta profile, and map only one phone attribute so two values don't compete. | | A field ignores directory updates | The field is showing a value entered in Blinq, so it's no longer linked to your directory. See [How provisioning works](/identity/how-provisioning-works) for how fields become unlinked and what to check. | | A user unassigned in Okta is still active in Blinq | Check that the deactivation provisioning actions are enabled on the Blinq app in Okta. Okta only sends the deactivation if those actions are switched on. | | Provisioned cards have no profile photo | Photos aren't part of the directory feed. The card owner or a workspace admin adds them in Blinq. | ## What to send support If none of these explain it, email [support@blinq.me](mailto:support@blinq.me) with the user's email address, the field involved, and roughly when the change was made in Okta. That's enough to trace the request on the Blinq side. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # SAML SSO with Microsoft Entra ID (Azure AD) Source: https://docs.blinq.me/identity/sso/entra Add the Blinq enterprise application in Entra ID and exchange SAML details with Blinq. > [!NOTE] > > SSO is available on **Enterprise** plans, with your domains enabled by the Blinq team. Read [How SAML SSO works](/identity/how-sso-works) first — it covers registering your domains, which has to happen before the SAML settings will open. Blinq is listed in the Entra gallery, so you don't need to build a custom application. ## Add the Blinq application **1. Open Enterprise applications** Go to [entra.microsoft.com](https://entra.microsoft.com) or [portal.azure.com](https://portal.azure.com) and open **Enterprise applications → New application**. **2. Add Blinq** Search for **Blinq**, select it, then select **Create**. **3. Choose SAML** Open **Single sign-on** from the Manage menu, then select **SAML**. ## Send Blinq's details to Entra In the Blinq dashboard, go to **Settings → SAML** and keep it open. **1. Edit the basic SAML configuration** In Entra, select **Edit** on the **Basic SAML Configuration** panel. **2. Paste the ACS URL** Copy the **ACS URL** from Blinq — it looks like `auth.blinq.me/authorize/callback/…` — and paste it into both **Reply URL (Assertion Consumer Service URL)** and **Sign on URL**. Save. ## Set the signing option > [!WARNING] > > **This step is the most common cause of SSO failing later.** If the signing option isn't set correctly, sign-in fails with a signature error, and Entra has been known to reset it during tenant changes. Set it deliberately and re-check it if sign-in breaks. **1. Edit the SAML certificate** Select **Edit** on the **SAML Certificates** panel. **2. Choose the signing option** Set **Signing Option** to **Sign SAML response and assertion**, then save. ## Send Entra's details to Blinq **1. Download the certificate** From **SAML Certificates**, download the **Base64** certificate, open it in a text editor, and paste the contents into **Certificate** in Blinq. **2. Copy the sign-on URL** Paste Entra's **Login URL** into **Single Sign-On URL** in Blinq. **3. Copy the identifier** Paste the **Microsoft Entra Identifier** into **Identity Provider Entity ID** in Blinq. **4. Save** With every field filled in, select **Save** in Blinq. > [!TIP] > > **Your configuration is stored.** Test it in a separate browser or private window before you enforce it. ## Enforce SSO Once you've confirmed a test sign-in works, switch on **Enforce SSO for all users** at the bottom of the SAML settings and save. Everyone signing in with an address on your registered domains is now routed through Entra ID. See [How SAML SSO works](/identity/how-sso-works) for exactly what changes. > [!WARNING] > > Don't sign out of Blinq until a test sign-in has succeeded in another window. If enforcement is on and the configuration is wrong, only Blinq support can switch it back off. ## Assigning people Assign users or groups to the Blinq application under **Users and groups**, the same way you would for any enterprise application. If you also want accounts created and deactivated in Blinq automatically, see [SCIM provisioning with Microsoft Entra ID](/identity/entra) — it uses the same application. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # SAML SSO with Google Workspace Source: https://docs.blinq.me/identity/sso/google-workspace Create a custom SAML app in Google Workspace and exchange SAML details with Blinq. > [!NOTE] > > SSO is available on **Enterprise** plans, with your domains enabled by the Blinq team. Read [How SAML SSO works](/identity/how-sso-works) first — it covers registering your domains, which has to happen before the SAML settings will open. Google Workspace has no Blinq app in its catalogue, so you create a custom SAML app. Blinq needs no attribute mappings. > [!NOTE] > > **After email signatures instead?** That's a separate integration — see [Google Workspace email signature sync](/integrations/google-workspace). You can set up either one without the other. ## Create the SAML app **1. Open web and mobile apps** Go to [admin.google.com](https://admin.google.com) and open **Apps → Web and mobile apps**. **2. Add a custom SAML app** Select **Add app → Add custom SAML app**, give it a name and description, then **Continue**. **3. Copy Google's details** On the Google identity provider details screen, take the **SSO URL**, **Entity ID** and **Certificate**. Keep this tab open. ## Send Google's details to Blinq In the Blinq dashboard, go to **Settings → SAML**. | Copy from Google | Paste into Blinq | | - | - | | SSO URL | **Single Sign-On URL** | | Entity ID | **Identity Provider Entity ID** | | Certificate | **Certificate** | Select **Save**. ## Send Blinq's details to Google **1. Copy Blinq's service provider details** From the same SAML settings, copy the **ACS URL** and the **Service provider entity ID**. **2. Paste them into Google** Back in Google, select **Continue**, then paste them into **ACS URL** and **Entity ID**. **3. Set the name ID format** Set **Name ID format** to **EMAIL**. **4. Skip attribute mapping** Blinq needs no attribute mappings. Select **Finish**. ## Turn the app on Open the **User access** section of your new app and turn the service **ON for everyone**, or for the organisational units that should have Blinq. Save. > [!NOTE] > > Google can take a few minutes to apply an access change before a test sign-in will work. ## Test before you enforce Use **Test SAML login** in the Google app, signing in with an address on the domain you registered with Blinq. If it fails, Google's [SAML error messages](https://support.google.com/a/answer/6301076) name the field to correct. Once a test sign-in works, switch on **Enforce SSO for all users** at the bottom of the Blinq SAML settings and save. > [!WARNING] > > Don't sign out of Blinq until a test sign-in has succeeded in another window. If enforcement is on and the configuration is wrong, only Blinq support can switch it back off. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # SAML SSO with Okta Source: https://docs.blinq.me/identity/sso/okta Create a SAML 2.0 app integration in Okta and exchange SAML details with Blinq. > [!NOTE] > > SSO is available on **Enterprise** plans, with your domains enabled by the Blinq team. Read [How SAML SSO works](/identity/how-sso-works) first — it covers registering your domains, which has to happen before the SAML settings will open. There's no Blinq app in the Okta Integration Network, so you build a SAML 2.0 app integration yourself. It takes a few minutes and needs no custom attributes. ## Create the app integration **1. Start a new integration** In the Okta Admin dashboard, open **Applications → Applications**, select **Create App Integration**, choose **SAML 2.0**, then **Next**. **2. Name it** Give the app a name your team will recognise, and add a logo if you like. Select **Next**. ## Send Blinq's details to Okta In the Blinq dashboard, go to **Settings → SAML** and keep it open. **1. Single sign-on URL** Paste the **ACS URL** from Blinq. **2. Audience URI** Paste the **Service provider entity ID** from Blinq into **Audience URI (SP Entity ID)**. **3. Leave RelayState blank** Nothing goes in **Default RelayState**. **4. Set the name ID and username formats** Set **Name ID format** to **EmailAddress**, and **Application username** to **Okta username**. **5. Finish** Blinq needs no attribute statements, so select **Next**, answer the customer question, and select **Finish**. ## Send Okta's details to Blinq Open your new app, select the **Sign On** tab, and expand **More details** in the SAML 2.0 panel. | Copy from Okta | Paste into Blinq | | - | - | | Sign on URL | **Single Sign-On URL** | | Issuer | **Identity Provider Entity ID** | | Signing certificate | **Certificate** | > [!NOTE] > > Paste the certificate exactly as Okta gives it to you, with no reformatting or added line breaks. > [!WARNING] > > **Use the entity ID Okta gives you.** Okta issues an app-scoped identifier that looks like `http://www.okta.com/exk…`. That's correct — don't replace it with an organisation-level value. Select **Save** in Blinq, then test a sign-in in a separate browser or private window before going further. ## Enforce SSO Once a test sign-in works, switch on **Enforce SSO for all users** at the bottom of the SAML settings and save. Everyone signing in with an address on your registered domains is now routed through Okta. See [How SAML SSO works](/identity/how-sso-works) for what changes. > [!WARNING] > > Don't sign out of Blinq until a test sign-in has succeeded in another window. If enforcement is on and the configuration is wrong, only Blinq support can switch it back off. ## Launching Blinq from Okta If you want people to open Blinq from its tile in their Okta dashboard, contact [support@blinq.me](mailto:support@blinq.me) to have it enabled for your workspace. It currently requires enforcement to be switched on as well — see [How SAML SSO works](/identity/how-sso-works). > [!NOTE] > > Provisioning accounts from Okta is a separate setup. See [SCIM provisioning with Okta](/identity/okta-scim). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Troubleshooting SAML SSO Source: https://docs.blinq.me/identity/sso/troubleshooting Sign-in failures, certificate errors, settings you can't reach, and people who can't join. | Symptom | Cause and fix | | - | - | | The SAML settings show an upgrade prompt, but you're on Enterprise | No domain is registered yet. The SAML settings unlock once Blinq adds at least one domain to your workspace. Email [support@blinq.me](mailto:support@blinq.me) with the domains you want covered. | | Sign-in fails with a signature or invalid document error | The identity provider isn't signing the response. In Entra ID, set **Signing Option** to **Sign SAML response and assertion** under SAML Certificates. Entra has been known to reset this, so re-check it if sign-in breaks after working. | | Sign-in fails after working for months | Check the signing option above, and confirm the Blinq application still exists in your identity provider — removing it breaks sign-in for everyone on your domains. | | Sign-in returns a 404 | The identity provider values are in the wrong Blinq fields. The sign-on URL goes in **Single Sign-On URL** and the issuer or identifier goes in **Identity Provider Entity ID** — it's easy to swap these two. | | Launching Blinq from the app tile returns a server error | Starting from the identity provider requires enforcement to be switched on as well. Contact support before enabling it, and see [How SAML SSO works](/identity/how-sso-works). | | Someone still sees password and email code options | Enforcement isn't switched on, or their address isn't on a registered domain. Enforcement is matched on the email domain someone signs in with. | | A team member is told their account is already in use | They first signed in with a different method than the one they're using now. Ask them to sign in the original way, or contact support. | | Someone whose email isn't on your domains can't be added | Invite links, self-claim and card assignment all check the registered domains. There's no self-serve way to add someone outside them — contact support. | | You've locked yourself out after enabling enforcement | Only Blinq support can switch enforcement back off. Email [support@blinq.me](mailto:support@blinq.me) from an address on your domain. | ## Before you enforce Most of the cases above are avoidable. Stay signed in to Blinq in your main browser while you configure SSO, and run every test in a separate browser or a private window. Only switch on enforcement once a test sign-in has actually succeeded. ## What to send support If none of these explain it, email [support@blinq.me](mailto:support@blinq.me) with your workspace name, the identity provider you're using, the email address that failed, and roughly when the attempt was made. That's enough to trace the sign-in on the Blinq side. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq documentation & integrations Source: https://docs.blinq.me/index Technical docs and integration guides for Blinq - connect your CRM, marketing tools, HR platform and more. ## Overview Welcome to the official documentation home for Blinq. Use these technical guides to better understand how Blinq's features work and set up your integrations and workflows. Getting Blinq connected to your tools is great for: * Ensuring every contact you meet syncs to your CRM and marketing tools, mapped to the correct fields, enriched with data to follow up, and carrying the full context of your conversation * Automating user provisioning so Blinq adds, updates, and removes digital business cards automatically, based on the information in your own systems * Building out your event lead capture workflow so it works with all of your existing tools Looking for step-by-step help with the app, your account, or admin settings? Visit the [Blinq Help Center](https://support.blinq.me/en/). ## Documentation categories > **[Blinq features](/features)** > > Digital business cards, event lead capture, contacts with context, and more. > **[Integrations](/integrations)** > > Connect Blinq to your CRM, identity provider, and the thousands of apps your team already uses. # Blinq integrations Source: https://docs.blinq.me/integrations Blinq connects to your CRM, identity provider, and thousands of apps. Every new contact, with notes, tags, and campaign attribution, lands where your team already works. ## CRM integrations > **[HubSpot](/integrations/hubspot)** > > Sync Blinq contacts to HubSpot automatically with notes, tags, and campaign attribution. > **[Salesforce](/integrations/salesforce)** > > Sync Blinq contacts to Salesforce automatically with notes, tags, and campaign attribution. > **[Microsoft Dynamics](/integrations/dynamics)** > > Sync Blinq contacts to Dynamics 365 Sales automatically with notes, tags, and campaign attribution. > **[GoHighLevel](/integrations/gohighlevel)** > > Sync Blinq contacts to GoHighLevel automatically with tags, campaigns, notes, and custom field mapping. > **[Pipedrive](/integrations/pipedrive)** > > Sync Blinq contacts to Pipedrive automatically with tags, campaigns, notes, and custom field mapping. > **[Zoho CRM](/integrations/zoho)** > > Export Blinq contacts to Zoho CRM as Leads or Contacts, automatically or after manual review. > **[monday.com](/integrations/monday)** > > Export Blinq contacts onto a monday.com board as items, with tags, campaigns, notes, and custom column mapping. ## Email and productivity integrations > **[Outlook](/integrations/outlook)** > > Export Blinq contacts into your team's Outlook address books, with notes and tags. > **[Google Workspace](/identity/sso/google-workspace)** > > Sign in to Blinq with Google credentials over SAML. ## Email signatures > **[Google Workspace](/integrations/google-workspace)** > > Push Blinq email signatures straight into your team's Gmail accounts, and keep them updated when they change. > **[Outlook](/integrations/outlook/email-signatures)** > > Add a Blinq signature to Outlook yourself, or deploy the Blinq add-in across your team. ## Marketing automation integrations > **[Marketo](/integrations/marketo)** > > Export Blinq contacts to Adobe Marketo Engage as Lead records, with tag sync and campaign-to-Program mapping. ## Automation integrations > **[Zapier](/integrations/zapier)** > > Push Blinq contacts to Zapier the moment they're created or updated, and connect them to over 9,000 apps. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Microsoft Dynamics integration overview Source: https://docs.blinq.me/integrations/dynamics Connect your Blinq contacts directly to Microsoft Dynamics 365 so captured contacts flow into your CRM automatically. > [!NOTE] > > The Microsoft Dynamics integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our Microsoft Dynamics integration connects your Blinq contacts directly to Microsoft Dynamics 365. Contacts captured in Blinq flow into Dynamics automatically, complete with notes, tags, and campaign attribution. Your team gets clean, contextual data where they already work, without manual exports. The integration is built on Microsoft Entra (Azure AD) sign-in and the Dataverse API, and syncs contacts as **Contact** records, with the option to also create **Lead** records. You can install and configure the Microsoft Dynamics integration from your [Blinq dashboard](/integrations/dynamics/connecting-dynamics). ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to set up and manage the Microsoft Dynamics integration. * You'll need a **Microsoft Dynamics 365 Sales** environment with a **System Administrator** account. * You'll need your Dynamics **environment URL** (for example, `https://your-company.crm.dynamics.com`). * Blinq's Microsoft Dynamics integration is available on **Business** and **Enterprise** plans. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Sync updates to contacts from Blinq to Dynamics automatically | Yes | Toggle on/off | | Sync Blinq contact notes | Yes | Toggle on/off | | Sync Blinq contact tags | Yes | Toggle on/off | | Auto export new Blinq contacts | Yes | Toggle on/off | | Export contacts as Leads or Contacts | Yes | Toggle in integration settings (Contacts by default) | | Assign contact owner in Dynamics | Yes | Matched to Blinq owner | | Account/organization linking | Yes | Contacts linked to their parent account | | Contact de-duplication | Yes | Matched on unique email address | | Campaign sync | Yes | Synced to custom fields | | Custom field mappings | Yes | Toggle in integration settings | ## Documentation for our Microsoft Dynamics integration > **[Connecting Microsoft Dynamics](/integrations/dynamics/connecting-dynamics)** > > Install the Microsoft Dynamics integration from your Blinq dashboard. > **[Configuring Blinq](/integrations/dynamics/configuring-blinq)** > > Control how Blinq syncs contacts, notes, and tags to Dynamics, and how contacts are shared. > **[Configuring Microsoft Dynamics](/integrations/dynamics/configuring-dynamics)** > > Add Blinq's custom fields to the Contact and Lead forms your team uses in Dynamics. > **[Field reference](/integrations/dynamics/field-reference)** > > Contact field mapping, custom fields, and deduplication behavior. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for Microsoft Dynamics Source: https://docs.blinq.me/integrations/dynamics/configuring-blinq Control how Blinq syncs contacts, notes, and tags to Microsoft Dynamics, and how contacts are shared. ## Configuring Blinq Once connected, you can control how Blinq syncs data to Microsoft Dynamics. Toggle any option on or off at any time from **Settings → Integrations → Microsoft Dynamics**. ### Export contacts as Contacts or Leads Choose whether Blinq exports your contacts to Dynamics as **Contacts** or **Leads**. Contacts is the default. You can update this setting at any time in your integration settings. ### Automatically update changes to Blinq contacts in Dynamics When enabled, Blinq automatically updates Dynamics whenever you change a contact's details. Your CRM stays current without manual re-entry. This is on by default. ### Sync contact notes When enabled, Blinq syncs notes from a contact to Dynamics as notes on the associated record. This is on by default. ### Sync contact tags When enabled, Blinq syncs tags from a contact (including contact tags, workspace tags, and campaign tags) to custom fields on the Dynamics record. This is on by default. ### Automatically export new Blinq contacts to Dynamics When enabled, Blinq automatically exports every new contact to Dynamics as a **Contact** record. When disabled, you can still export contacts one at a time from **All company contacts**. This is on by default. ### Allow team members to export When enabled, team members can export their own contacts to Dynamics. When disabled, only admins can export. This is off by default. ## Sharing contacts to Dynamics > [!NOTE] > > Blinq automatically shares contacts captured on a team card with your team. No manual sharing required. Blinq assigns the owner of each Dynamics record based on the contact's Blinq owner. Export contacts to Dynamics from **Blinq → Contacts → All company contacts**. Blinq doesn't export your personal contacts to Dynamics unless you've shared them with your team. If you haven't shared a contact with your organization yet, you can share it from the **Share** menu on the individual contact record, in the dashboard or Blinq app. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Microsoft Dynamics for Blinq Source: https://docs.blinq.me/integrations/dynamics/configuring-dynamics Add Blinq fields to the Contact and Lead forms your team uses in Microsoft Dynamics. ## Add Blinq fields in Dynamics > [!NOTE] > > For help adding these fields in your Dynamics environment, see Microsoft's documentation: [Add, configure, move, or delete columns on a form](https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/add-move-or-delete-fields-on-form) and the [model-driven form designer](https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-and-edit-forms). When you connect Blinq, it automatically creates the following custom fields in your Dynamics environment. They won't appear to your team until you add them to the forms and views you use. * **Blinq Contact Tags:** contact-level tags applied in Blinq. * **Blinq Workspace Tags:** workspace-level tags. * **Blinq Campaign Tags:** campaign tags from linked Blinq campaigns. * **Blinq Campaigns:** names of linked Blinq campaigns. * **Blinq Card Link:** a direct link to the contact's Blinq card. Where you add them depends on how your team has set up Dynamics. For the full field mapping, see the [field reference](/integrations/dynamics/field-reference). ## Blinq Contact Notes in Dynamics Notes from your Blinq contacts sync automatically to Dynamics, with no setup required. They appear in the record's Timeline by default. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Microsoft Dynamics to Blinq Source: https://docs.blinq.me/integrations/dynamics/connecting-dynamics Install the Microsoft Dynamics integration from your Blinq dashboard. **1. Open Settings** * In the Blinq dashboard, navigate to **Settings** in the left-hand menu. * Select the **Integrations** tab. * Click **Connect** on the Microsoft Dynamics integration. **2. Enter your Dynamics environment URL** Enter your Dynamics environment URL when prompted (for example, `https://your-company.crm.dynamics.com`). **3. Sign in to Microsoft** A pop-up window opens. Sign in to Microsoft using an account with **System Administrator** access to your Dynamics environment, and approve the requested permissions. **4. Confirm** Once authorized, close the pop-up window. Your Blinq dashboard opens with the Microsoft Dynamics integration settings visible. > [!TIP] > > **Microsoft Dynamics is now connected to Blinq.** *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Microsoft Dynamics field reference Source: https://docs.blinq.me/integrations/dynamics/field-reference Contact field mapping, custom fields, and deduplication behavior for the Blinq Microsoft Dynamics integration. > [!NOTE] > > Blinq syncs contact data to fields on the Dynamics Contact record, and to the Lead record when you enable Lead creation. Blinq creates the custom fields it needs automatically when you connect the integration. ## Contact field mapping If the following information is present on the Blinq contact, Blinq syncs it to the corresponding Dynamics field. | Blinq contact field | Dynamics field | | - | - | | First name | firstname (required) | | Last name | lastname (required) | | Job title | jobtitle | | Company | companyname (Lead) / Parent account link (Contact) | | Email (first/primary) | emailaddress1 | | Email (secondary) | emailaddress2 | | Email (tertiary) | emailaddress3 | | Phone number | telephone1 | | Mobile phone | mobilephone | | Additional phone numbers | telephone2, telephone3 | | Company website/URL (first) | websiteurl | | Notes | Notes (on the Contact or Lead record) | To customize which fields Blinq syncs and how they map, see [Blinq field mapping](/features/field-mapping). ## Custom fields created by Blinq > [!NOTE] > > You can only map fields that exist on **both** the Contact and Lead entities. Blinq creates the following custom fields in Dynamics when you connect the integration, and uses them to sync tags and campaign attribution. | Field name | Description | | - | - | | Blinq Contact Tags | Contact-level tags applied in Blinq | | Blinq Workspace Tags | Workspace-level tags | | Blinq Campaign Tags | Campaign tags from linked Blinq campaigns | | Blinq Campaigns | Names of linked Blinq campaigns | | Blinq Card Link | A direct link to the contact's Blinq card | ## Deduplication When you export a Blinq contact to Dynamics, Blinq looks for an existing record with the same email address (or phone number if there's no email) across both Contacts and Leads. If Blinq finds a record it already manages, it updates it. If it finds a record created elsewhere, Blinq leaves it untouched to avoid overwriting another source's data. Blinq never merges Leads and Contacts; combining them is a Dynamics action. Your CRM has the final say on every export. Duplicate and matching rules, required fields, and validation rules set up in your CRM can change how a record is matched, allow a duplicate to be created, or block an export entirely. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq GoHighLevel integration overview Source: https://docs.blinq.me/integrations/gohighlevel Export contacts captured in Blinq to GoHighLevel automatically, with tags, campaigns, and notes. > [!NOTE] > > The GoHighLevel integration is available on **Business** plans. [View pricing →](https://blinq.me/pricing) Our GoHighLevel integration connects Blinq to your GoHighLevel account. Contacts your team captures — at events, in meetings, or through lead capture forms — export into GoHighLevel automatically, along with their tags, campaigns, and notes. It's a native integration, so it behaves the same way as our Salesforce, HubSpot, Dynamics, Marketo, Zoho, monday.com, and Pipedrive connections. Sync is one-way. Contacts move from Blinq into GoHighLevel, and changes made in GoHighLevel don't come back to Blinq. > [!NOTE] > > Blinq is a public app on the [GoHighLevel marketplace](https://marketplace.gohighlevel.com/integration/6a751c6325660c8aaec446c0), so any GoHighLevel account can install it and there's no cap on how many people can use it. ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to connect GoHighLevel and change its settings. * You'll need admin access to the GoHighLevel account you're connecting. * You'll need at least one company contact in your Blinq workspace. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Export contacts to GoHighLevel | Yes | — | | Auto export new Blinq contacts | Yes | On by default | | Sync Blinq notes | Yes | Included with the contact | | Sync Blinq contact, workspace, and campaign tags | Yes | Included with the contact | | Campaign sync | Yes | Included with the contact | | Custom field mapping | Yes | Field mapper, including hidden fields | | Choose which team members sync | Yes | Manual triage | | Connect more than one GoHighLevel account | No | One account per Blinq workspace | > [!NOTE] > > **Nothing for your team to set up.** An admin connects GoHighLevel once for the workspace and chooses who syncs. Members configure nothing, and contacts they capture on iOS or Android flow through automatically. GoHighLevel can run alongside Salesforce, HubSpot, Dynamics, or any other connected integration. A captured contact exports to every platform you've connected. ## Documentation for our GoHighLevel integration > **[Connecting GoHighLevel](/integrations/gohighlevel/connecting-gohighlevel)** > > Install the Blinq app from the GoHighLevel marketplace and connect your account. > **[Configuring Blinq](/integrations/gohighlevel/configuring-blinq)** > > Map your fields and choose which team members sync to GoHighLevel. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for GoHighLevel Source: https://docs.blinq.me/integrations/gohighlevel/configuring-blinq 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. > [!NOTE] > > 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. ## 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. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting GoHighLevel to Blinq Source: https://docs.blinq.me/integrations/gohighlevel/connecting-gohighlevel Install the Blinq app from the GoHighLevel marketplace and connect it to your Blinq workspace. Connecting GoHighLevel takes one pass through the GoHighLevel marketplace. There are no API keys or tokens to copy. ## Connect GoHighLevel in Blinq **1. Open your integrations** In the Blinq [dashboard](https://dash.blinq.me), go to **Settings**, then the **Integrations** tab. **2. Start the connection** Under **Export contacts**, find **GoHighLevel** and select **Connect**. This takes you to the Blinq listing on the GoHighLevel marketplace. **3. Choose your GoHighLevel workspace** Select the GoHighLevel workspace you want to connect, then confirm the install. **4. Return to Blinq** Come back to the Blinq tab to set up your sync settings and map your fields. > [!TIP] > > **GoHighLevel is connected.** Next, [map your fields and choose who syncs](/integrations/gohighlevel/configuring-blinq). > [!WARNING] > > **One GoHighLevel account per Blinq workspace.** You can't connect two GoHighLevel instances to the same Blinq workspace. If you run more than one GoHighLevel account and need contacts in both, talk to [support@blinq.me](mailto:support@blinq.me) before you set this up. ## Who connects it An admin or owner connects and disconnects GoHighLevel at the workspace level. Nobody else on your team needs to do anything — reps don't install anything or sign in to GoHighLevel, and contacts they capture on the mobile apps sync through automatically once the connection is live. > [!NOTE] > > Don't see GoHighLevel under **Export contacts**? Check your plan first, then contact [support@blinq.me](mailto:support@blinq.me). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Google Workspace email signature sync Source: https://docs.blinq.me/integrations/google-workspace Push Blinq email signatures straight into your team's Gmail accounts, and keep them updated when they change. > [!NOTE] > > Email signature sync is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Blinq writes your team's email signatures directly into their Gmail accounts. An admin creates a signature in Blinq, and it appears in Gmail without anyone having to copy or paste anything. Sync is one way. Signatures move from Blinq into Gmail, and changes made in Gmail don't come back to Blinq. > [!NOTE] > > **Looking for single sign-on?** That's a separate integration with its own setup — see [SAML SSO with Google Workspace](/identity/sso/google-workspace), filed under Identity. The two are independent, and you can use either without the other. ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace, on a Business or Enterprise plan. * You'll need **Google Workspace Super Admin** access, or someone who has it and can complete their part of the setup. * Your domain must be verified in Google Workspace. A Workspace subscription alone isn't enough. * Each person's Blinq signature email must match a Gmail account in your Google Workspace. ## What sync does and doesn't do | Behavior | Detail | | - | - | | Direction | One way, Blinq to Gmail | | Which Gmail field | The default signature for **new emails** only. The reply and forward signature isn't set. | | Changes made in Gmail | Overwritten the next time Blinq syncs that signature | | Signatures per person | One. Google allows a single signature per address, so someone assigned two templates can only receive one. | | Google Workspace tenants | One per Blinq workspace. Organisations running more than one tenant can't cover them all. | | Signature and card | Not linked. Editing someone's card later doesn't change a signature already created from it — edit the signature itself. | | Mobile | Image signatures don't render in the Gmail mobile app. | > [!WARNING] > > **Install the Blinq app for your whole organisation, not for selected groups.** Scoping the Google Marketplace install to specific groups or organisational units is the most common reason signatures fail to sync, and the error it produces reads only **Sync failed** — nothing points at the scope. If you must limit it, make sure every person who'll receive a Blinq signature is inside the groups you select. ## Signatures aren't created for you Adding someone to your workspace doesn't generate a signature for them. An admin creates each signature in Blinq first, and the sync then matches it to a Gmail account by email address. See [Creating a team email signature](https://support.blinq.me/en/articles/76202-creating-a-team-email-signature) for that step. > [!NOTE] > > **HTML signatures are switched on by request.** By default a Blinq signature is a single image linking to the person's card. If you want an HTML signature instead, email [support@blinq.me](mailto:support@blinq.me) to have it enabled for your workspace. ## Documentation for Google Workspace signature sync > **[Connecting Google Workspace](/integrations/google-workspace/connecting-google-workspace)** > > Authorise Blinq, choose your domains, and install the app from Google Marketplace. > **[Syncing signatures to Gmail](/integrations/google-workspace/email-signatures)** > > Turn on the sync, push existing signatures, and read the sync statuses. > **[Troubleshooting](/integrations/google-workspace/troubleshooting)** > > Signatures that won't sync, misleading error text, and signatures that don't appear in Gmail. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Google Workspace to Blinq Source: https://docs.blinq.me/integrations/google-workspace/connecting-google-workspace Authorise Blinq, choose the domains you want covered, and install the Blinq app from Google Marketplace. Connecting takes two parts: authorising Blinq from your Blinq dashboard, and installing the Blinq app in Google Workspace. Both need Google Workspace Super Admin access. > [!NOTE] > > **Not the Super Admin?** Start the connection anyway. When Blinq asks whether you're the Google Workspace admin, select **No, I'm not** and you'll get a link to send to whoever is. Once they tell you it's done, carry on at [Email signatures](/integrations/google-workspace/email-signatures). ## Where to start You can start from either place in the Blinq [dashboard](https://dash.blinq.me) — both open the same setup: * **Email Signatures**, then **Sync to Google** at the top of the page. * **Settings → Integrations**, then **Connect** under **Google** in the Email signatures section. ## Authorise Blinq **1. Start the connection** Select **Sync to Google** or **Connect**, depending on where you started. A panel explains what the sync does — select **Setup sync** to continue. **2. Confirm you're the administrator** When asked **Are you the Google Workspace Admin?**, select **Yes, I'm the super admin**. A new tab opens asking you to sign in to Google Workspace — choose your Super Admin account. **3. Approve the permissions Blinq needs** Review and approve the permissions on the Google consent screen. **4. Select your domains** Check every domain whose signatures you want synced, then select **Continue**. Only Blinq accounts on the domains you select here will sync. **5. Confirm** A confirmation appears. Select **Next**. > [!WARNING] > > **Add every domain you use now.** A domain that comes into use after you connect isn't picked up on its own, and signatures on it fail with an error reading **Domain not in Google Workspace** — even when the domain is perfectly fine in Google. Adding one later needs Blinq support, so it's much easier to select them all up front. ## Install the app in Google Workspace **1. Open Google Marketplace** Select **Install App**. Google Marketplace opens in a new tab. **2. Check which Google account you're using** Hover over the profile icon in the top right and confirm you're signed in as your Google administrator account. Installing under a personal or secondary profile is a common mistake and the install won't apply to your organisation. **3. Install for your whole organisation** Follow Google's prompts and choose to install for the whole organisation. Selecting specific groups or organisational units is the most frequent cause of signatures failing later. **4. Return to Blinq** Go back to the Blinq tab. You'll see the app installing. You can close the setup window at any point — Google emails you when the install is complete. > [!TIP] > > **Google Workspace is connected.** Next, [turn on the sync](/integrations/google-workspace/email-signatures). > [!NOTE] > > Installation is usually quick, but Google allows up to 24 hours. If it's still installing after that, email [support@blinq.me](mailto:support@blinq.me) rather than waiting longer — support can check whether the install actually completed and finish it from their side. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Syncing signatures to Gmail Source: https://docs.blinq.me/integrations/google-workspace/email-signatures Turn on the sync, push the signatures you already have, and read what each sync status means. Once Google confirms the app is installed, turn the sync on from Blinq. ## Turn on the sync **1. Open your Google Workspace sync settings** In the Blinq [dashboard](https://dash.blinq.me), open **Email Signatures** and select **Sync to Google**. You can also reach the same settings from **Settings → Integrations**, under **Google** in the Email signatures section. **2. Turn on Sync New Email Signatures** Every signature created from now on syncs to its matching Gmail account automatically, and later edits to it sync too. **3. Push the signatures you already have** Select **Sync**. This applies to every active signature in your workspace. > [!TIP] > > **Sync is on.** Return to the Email Signatures list to watch the status of each signature. > [!WARNING] > > **Leave Sync New Email Signatures switched on.** A signature created while it's off may not be pushable individually afterwards. Keeping it on means every signature gets a live link to its Gmail account from the moment it's created. ## Sync statuses Each signature shows its own status in the Email Signatures list. | Status | Meaning | | - | - | | **Synced** | A matching Gmail account was found and the signature was written to it. | | **Syncing** | Blinq is currently pushing the signature to Gmail. | | **Out of sync** | The signature was synced, then edited in Blinq. The edit hasn't reached Gmail yet. | | **Can't be synced** | The signature didn't reach Gmail. See [Troubleshooting](/integrations/google-workspace/troubleshooting) — the reason shown is often not the real cause. | > [!NOTE] > > **Synced doesn't mean it's visible yet.** Blinq marks a signature **Synced** as soon as Google accepts it. Google then applies it to the mailbox, and that isn't immediate. If someone reports their signature missing straight after you sync, ask them to check again a little later before treating it as a failure. ## What happens after a signature syncs * Editing the signature in Blinq pushes the change to Gmail automatically. * If someone changes their signature in Gmail by hand, Blinq overwrites it the next time it syncs. * Only the default signature for **new emails** is set. Anyone who wants it on replies and forwards can select it themselves in Gmail's settings. * Removing someone from Google Workspace stops them appearing in the sync status list. > [!WARNING] > > **Editing someone's card doesn't update their signature.** A signature created from a card isn't linked back to it, so later changes to the card — a new job title, a new phone number — don't flow through. Edit the signature itself, and the change syncs from there. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Troubleshooting Google Workspace signature sync Source: https://docs.blinq.me/integrations/google-workspace/troubleshooting Signatures that won't sync, error text that points at the wrong thing, and signatures that don't appear in Gmail. > [!WARNING] > > **The error text is often misleading.** Several different problems all show as **Can't be synced** with the message **Sync failed**, and one of them names Google when the cause is on the Blinq side. Work through the table below rather than taking the message at face value. | Symptom | Cause and fix | | - | - | | Most of your team fails, a handful work | The Marketplace app was installed for selected groups or organisational units, and the people who work are the ones inside them. Reinstall for the whole organisation, or widen the assignment to cover everyone with a Blinq signature. | | **Domain not in Google Workspace**, but the domain is fine in Google | The domain isn't registered on the Blinq side. This check runs before Blinq ever contacts Google, so the message points at the wrong system. It usually means the domain came into use after you connected. Email [support@blinq.me](mailto:support@blinq.me) to have it added — there's no self-serve screen for this. | | **User not found** | No Gmail account in your Google Workspace matches the email on the signature. Check for a typo, and check the person hasn't been suspended or had their address changed. | | **Sync failed** with no further detail | Either the integration is no longer active, or the Marketplace app was removed or had its access revoked in Google Workspace. Check the app is still installed and assigned, then sync again. | | Everything says **Synced** but nothing appears in Gmail | Give it time before treating it as broken. Blinq marks a signature synced as soon as Google accepts it, and Google applies it to the mailbox some time afterwards. | | A signature won't push, and it was created before you turned sync on | Signatures created while **Sync New Email Signatures** was off may not be pushable individually. Contact [support@blinq.me](mailto:support@blinq.me). | | The install never finishes | Google allows up to 24 hours. Past that, email support rather than waiting — they can check whether the install completed and finish it from their side. | | A signature is out of date after a card was updated | Signatures aren't linked to cards. Edit the signature itself and the change syncs from there. | | Someone needs two different signatures | Google allows one signature per email address, so this isn't possible. | | Your organisation has more than one Google Workspace tenant | Blinq connects to one tenant per workspace. Contact support to talk through the options. | ## What to send support If none of these explain it, email [support@blinq.me](mailto:support@blinq.me) with the affected email addresses, the status and message shown against each one, and whether the Marketplace app was installed for your whole organisation or for selected groups. That's enough to trace the sync on the Blinq side. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq HubSpot integration overview Source: https://docs.blinq.me/integrations/hubspot Connect your Blinq contacts directly to HubSpot so captured contacts flow into your CRM automatically. > [!NOTE] > > The HubSpot integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our HubSpot integration connects your Blinq contacts directly to HubSpot. Contacts captured in Blinq flow into your CRM automatically, complete with notes, tags, and campaign attribution. Your team gets clean, contextual data where they already work, without manual exports. You can install and configure the HubSpot integration from your [Blinq dashboard](/integrations/hubspot/connecting-hubspot#integrating-with-hubspot-from-the-blinq-dashboard), or install our app directly through the [HubSpot Marketplace](/integrations/hubspot/connecting-hubspot#integrating-with-blinq-from-the-hubspot-marketplace-app). ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to set up and manage the HubSpot integration. * You'll need admin access (or permission to install HubSpot Marketplace apps) to the HubSpot account you want to integrate with. * Blinq's HubSpot integration is available on **Business** and **Enterprise** plans. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Sync updates to contacts from Blinq to HubSpot automatically | Yes | Toggle on/off | | Sync Blinq contact notes | Yes | Toggle on/off | | Sync Blinq contact tags | Yes | Toggle on/off | | Auto export new Blinq contacts | Yes | Toggle on/off | | Assign Contact Owner in HubSpot | Yes | Matched to Blinq owner | | De-duplication | Yes | Matched on unique email address | ## Documentation for our HubSpot integration > **[Connecting HubSpot](/integrations/hubspot/connecting-hubspot)** > > Install the HubSpot integration from your Blinq dashboard or from the HubSpot Marketplace. > **[Configuring Blinq](/integrations/hubspot/configuring-blinq)** > > Control how Blinq syncs contacts, notes, and tags to HubSpot, and how contacts are shared. > **[Configuring HubSpot](/integrations/hubspot/configuring-hubspot)** > > Customize how Blinq data appears in HubSpot. > **[Field and property reference](/integrations/hubspot/field-reference)** > > Standard contact fields, custom properties, and meeting records Blinq syncs to HubSpot. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for HubSpot Source: https://docs.blinq.me/integrations/hubspot/configuring-blinq Control how Blinq syncs contacts, notes, and tags to HubSpot, and how contacts are shared. ## Configuring Blinq Once connected, you can control how Blinq syncs data to HubSpot. All options can be toggled on or off at any time from **Settings → Integrations → HubSpot**. ### Automatically update changes to Blinq contacts in HubSpot When enabled, Blinq automatically updates HubSpot whenever you change a contact's details. Your CRM stays current without manual re-entry. ### Sync contact tags and notes When enabled, Blinq syncs notes and tags from a contact straight to HubSpot. Relationship context travels with the contact: conversation notes, tags, and campaign labels. ### Automatically export new Blinq contacts to HubSpot When enabled, Blinq automatically exports every new contact to HubSpot as a new contact record. When disabled, you can still export contacts manually, one at a time, from **All company contacts**. ## Sharing contacts to HubSpot > [!NOTE] > > Blinq automatically shares contacts captured on a team card with your team. No manual sharing required. Export contacts to HubSpot from **Blinq → Contacts → All company contacts**. Blinq doesn't export your personal contacts to HubSpot unless you share them with your team. If you haven't shared a contact with your organization yet, you can share it from the **Share** menu on the individual contact record, in the dashboard or Blinq app. You can configure the HubSpot integration to automatically sync updates to existing contacts and automatically export any new ones. If you don't want automatic export or syncing, or you need to push a manual update, you can trigger an export or sync from the Blinq dashboard. **Sync all contacts:** in **Settings → Integrations**, click the HubSpot integration's **Settings**. At the bottom of the menu, click **Sync contacts**. **Export all contacts:** from the **All company contacts** view on the **Contacts** page, click **Export contacts** at the top of the page. When the integration is active, you'll see a **to HubSpot** option. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring HubSpot for Blinq Source: https://docs.blinq.me/integrations/hubspot/configuring-hubspot Customize how Blinq data appears in HubSpot. ## Configuring HubSpot When you connect Blinq, it automatically creates the following custom properties in your HubSpot account. They won't appear in your views until you add them. * **Blinq Tags:** contact-level tags assigned in Blinq. * **Blinq Workspace Tags:** workspace-level tags. * **Blinq Campaign Tags:** tags from campaigns the contact is part of. * **Blinq Campaigns:** names of campaigns the contact belongs to. * **Blinq Card:** a direct link to the contact's Blinq card. * **Blinq ID:** a unique Blinq identifier used for deduplication. You can configure how data from your Blinq Contacts appears in HubSpot based on your needs and use cases. ## Enabling Blinq contacts as HubSpot Marketing Contacts HubSpot only sends workflow-triggered emails to contacts marked as Marketing Contacts. To make new Blinq contacts eligible: 1. In HubSpot, click **Settings** in the top navigation. 2. Open the **Integrations** dropdown in the left menu. 3. Click **Marketing Contacts**. 4. Scroll down to **Blinq** and toggle it on. Once enabled, new contacts synced from Blinq are automatically set as Marketing Contacts, so they can be enrolled in your existing HubSpot workflows. Here are some example configurations to help you get the most out of your integration. ## CRM: Contacts view In your Contacts CRM view, you can customize the columns shown to include Blinq-specific fields. Navigate to your Contacts page in HubSpot (**CRM → Contacts**) and click **Edit columns**, found to the right of the search bar. In the column editor, search for Blinq and select which information you'd like to include in your default view. When you're done, click **Apply**. ## Contact page view > [!NOTE] > > For more on customizing the record page, see HubSpot's documentation: [Customize records](https://knowledge.hubspot.com/object-settings/customize-records). In your Object settings for Contacts, you can edit the page view for each contact record, allowing you to highlight the Blinq contact information you need. To edit the Contact page, navigate to your HubSpot **Settings → Data Management → Objects**, then select **Contacts → Record Customization**. Alternatively, open a contact record and click **Customize** in the top bar. Here, you can edit the existing Contact page view or create a new page view. In the page view editor's left-hand column, add a new card and select **Property List**. Here, you can name the card, and add specific property fields to the view. In the **Add Properties** section, you can search for Blinq to show all Blinq contact fields. ## Blinq Contact Notes in HubSpot Notes from your Blinq contacts sync automatically to HubSpot's native Notes, with no setup required. They appear on the contact record under **Activities → Notes** by default. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting HubSpot to Blinq Source: https://docs.blinq.me/integrations/hubspot/connecting-hubspot Install the HubSpot integration from your Blinq dashboard or from the HubSpot Marketplace. > [!NOTE] > > The HubSpot integration is available on Blinq **Business** and **Enterprise** plans. For larger organization setups, [talk to sales](https://dash.blinq.me/onboarding/contact-sales). ## Integrating with HubSpot from the Blinq dashboard **1. Open Settings** * In the Blinq dashboard, navigate to **Settings** in the left-hand menu. * Select the **Integrations** tab. * Click **Connect** on the HubSpot integration. **2. Log in to HubSpot** A pop-up window opens. Log in to your HubSpot account, or create one if you don't have one yet. **3. Select your HubSpot account** If you have access to multiple HubSpot accounts, select the account you'd like to connect to Blinq. **4. Confirm** Once authorized, Blinq returns you to your dashboard with the HubSpot integration settings visible. > [!TIP] > > **HubSpot is now connected to Blinq.** ## Integrating with Blinq from the HubSpot Marketplace app **1. Find Blinq in the Marketplace** In HubSpot, navigate to the Marketplace and search for the Blinq app, or you can visit our listing directly here: [Blinq app on HubSpot Marketplace](https://app-ap1.hubspot.com/marketplace/442747578/listing/blinq). ![The Blinq app listing on the HubSpot Marketplace, with the Install button](https://mintcdn.com/blinq/S3hWaqJ3vIinbZ4e/images/integrations/hubspot/marketplace-listing.png?fit=max\&auto=format\&n=S3hWaqJ3vIinbZ4e\&q=85\&s=aecc818a35b6f80fadf3cbd2ddbbdc9b) **2. Review requirements** Review the requirements to see what features are available on your HubSpot plan, and confirm you have a Blinq **Business** or **Enterprise** subscription. **3. Install and authenticate** Click **Install** to launch a window where you can authenticate with your Blinq account. If you're not already logged in, log in to your Blinq account, or [get Blinq Business](https://blinq.me/business), which includes the HubSpot integration. ![The Connecting Blinq to HubSpot step, showing the Blinq account being connected](https://mintcdn.com/blinq/S3hWaqJ3vIinbZ4e/images/integrations/hubspot/marketplace-connect-blinq.png?fit=max\&auto=format\&n=S3hWaqJ3vIinbZ4e\&q=85\&s=1ea83c875baf88cff3bd09de26c8b5a0) **4. Connect the app** Once you've authenticated with your Blinq account, finish the HubSpot install by reviewing what Blinq can access in your HubSpot account, accepting the third-party app notice, and confirming **Connect app**. ![The required access Blinq needs in your HubSpot account](https://mintcdn.com/blinq/S3hWaqJ3vIinbZ4e/images/integrations/hubspot/marketplace-scopes.png?fit=max\&auto=format\&n=S3hWaqJ3vIinbZ4e\&q=85\&s=1acc7e17673db040e93cb8909e9847a5) > [!TIP] > > **Blinq is now connected to HubSpot.** ![The Blinq installed confirmation screen in HubSpot](https://mintcdn.com/blinq/S3hWaqJ3vIinbZ4e/images/integrations/hubspot/marketplace-success.png?fit=max\&auto=format\&n=S3hWaqJ3vIinbZ4e\&q=85\&s=b0243bfcf7e2059f6d5209701f3f00f8) *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Disconnecting HubSpot from Blinq Source: https://docs.blinq.me/integrations/hubspot/disconnecting-hubspot Disconnect the HubSpot integration from your Blinq dashboard or uninstall the Blinq app from the HubSpot Marketplace. There are two ways to disconnect the HubSpot integration, depending on how it was installed: * **From the Blinq dashboard**, in your integration settings. * **From HubSpot**, by uninstalling the Blinq app in your connected apps (if you installed it via the HubSpot Marketplace). ## How disconnecting affects your HubSpot account and data Both methods have the same effect: as soon as you disconnect, Blinq stops sending contact details to your HubSpot account. * **New contacts are no longer exported.** Contacts you capture in Blinq stay in Blinq. * **Contact updates stop syncing.** Changes to contacts, notes, and tags in Blinq are no longer sent to HubSpot. * **CRM insights stop flowing back.** Blinq no longer receives HubSpot data about your contacts, so CRM insights from HubSpot won't appear in Blinq. > [!NOTE] > > Nothing already in HubSpot is removed — contacts and data Blinq has synced remain in your HubSpot account. ## Disconnecting from the Blinq dashboard **1. Open Settings** * In the Blinq dashboard, navigate to **Settings** in the left-hand menu. * Select the **Integrations** tab. **2. Disconnect HubSpot** Find the HubSpot integration and click **Disconnect**. **3. Confirm** Confirm you want to disconnect when prompted. > [!TIP] > > **HubSpot is now disconnected from Blinq.** ## Uninstalling the Blinq app from HubSpot If you installed the integration through the HubSpot Marketplace, you can also disconnect it by uninstalling the Blinq app from within HubSpot. Follow HubSpot's own guide: [Uninstall an app](https://knowledge.hubspot.com/marketplace/install-apps-in-the-hubspot-marketplace#uninstall-an-app). To reconnect at any time, follow the steps in [Connecting HubSpot](/integrations/hubspot/connecting-hubspot). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq HubSpot field and property reference Source: https://docs.blinq.me/integrations/hubspot/field-reference Standard contact fields, custom properties, and meeting interaction records Blinq syncs to HubSpot. > [!NOTE] > > Every data point Blinq syncs to HubSpot: standard contact fields, custom properties, and meeting interaction records. ## Custom properties created by the Blinq integration > [!WARNING] > > **Don't delete or rename these properties in HubSpot.** Blinq uses Blinq ID for contact deduplication. Removing it creates duplicate contact records on re-export. Blinq automatically creates the following custom properties in your HubSpot account when you connect. You don't need to set anything up manually. | Property name | What it contains | Populated when | | - | - | - | | Blinq Tags | Contact-level tags assigned in Blinq | On contact export (if tags enabled) | | Blinq Workspace Tags | Workspace-level tags | On contact export (if tags enabled) | | Blinq Campaign Tags | Tags from campaigns the contact is part of | On contact export from a campaign | | Blinq Campaigns | Names of campaigns the contact belongs to | On contact export from a campaign | | Blinq Card | Direct link to the contact's Blinq card | On every contact export | | Blinq ID | Unique Blinq identifier used for deduplication | On connect (bootstrapped), on every export | ## Contact fields When you export contacts, Blinq applies the standard field mapping below. | Blinq field | HubSpot field | | - | - | | First name | First name | | Last name | Last name | | Email (first/primary) | Email | | Phone number | Phone and/or Mobile | | Company | Company name | | Job title | Job title | | Website | Website | | Address | Address | | Blinq ID | Blinq ID | | HubSpot Owner (matched from Blinq contact owner) | Contact Owner | To customize which fields Blinq syncs and how they map, see [Blinq field mapping](/features/field-mapping). ## Meeting and interaction records When you export contacts, Blinq also pushes their associated interactions to HubSpot as **Meeting** objects, linked to the contact record. | Data point | HubSpot field | Value | | - | - | - | | Timestamp | Meeting date | When the interaction occurred | | Title | Meeting title | "Interaction from Blinq" | | Body | Meeting description | "Interacted with `{contact name}`" | | Location | Location | Where the interaction took place | | Duration | Start / end time | Interaction time + 15 min default duration | ## Deduplication HubSpot uses email address as the unique identifier for contacts. When you export a Blinq contact, HubSpot matches it to any existing contact with the same email and updates that record instead of creating a duplicate. If a matching contact is already managed by another source, Blinq leaves it unchanged rather than overwriting it. Your CRM has the final say on every export. Duplicate and matching rules, required fields, and validation rules set up in your CRM can change how a record is matched, allow a duplicate to be created, or block an export entirely. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Marketo integration overview Source: https://docs.blinq.me/integrations/marketo Export contacts captured in Blinq to Adobe Marketo Engage as Lead records, with tag sync, campaign-to-Program mapping, and automatic deduplication. > [!NOTE] > > The Marketo integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our Marketo integration connects Blinq to Adobe Marketo Engage. Contacts your team captures — at events, in meetings, or through lead capture forms — export into your Marketo database as Lead records. Once connected, Blinq keeps those records up to date, syncs your Blinq tags as Marketo fields, and adds leads captured during a Blinq campaign to a Marketo Program automatically. Unlike Salesforce and HubSpot, Marketo doesn't offer a sign-in-and-authorize flow. A Marketo admin [creates API credentials in Marketo](/integrations/marketo/configuring-marketo) and [enters them into Blinq](/integrations/marketo/connecting-marketo) once. ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to set up and manage the Marketo integration. * You'll need a Marketo account with admin access to the **Users & Roles** and **LaunchPoint** sections. No Marketo developer account is required. * You'll need at least one company contact in your Blinq workspace. * Blinq's Marketo integration is available on **Business** and **Enterprise** plans. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Export contacts as Marketo Lead records | Yes | — | | Sync updates to contacts from Blinq to Marketo automatically | Yes | Toggle on/off | | Sync Blinq contact, workspace, and campaign tags | Yes | Toggle on/off | | Auto export new Blinq contacts | Yes | Toggle on/off | | Campaign sync | Yes | Link a Blinq campaign to a Marketo Program | | Contact deduplication | Yes | Always on — matched on exact email address | | Sync Blinq notes and AI Notetaker summaries | No | Marketo has no equivalent object | Sync is one-way, from Blinq to Marketo. Changes made in Marketo don't flow back to Blinq. Marketo can run alongside Salesforce, HubSpot, Dynamics, or any other connected integration. A captured contact syncs to every platform you've connected. ## Documentation for our Marketo integration > **[Configuring Marketo](/integrations/marketo/configuring-marketo)** > > Create the API-only user and LaunchPoint service that Blinq uses to connect. > **[Connecting Marketo](/integrations/marketo/connecting-marketo)** > > Enter your Marketo API credentials in your Blinq dashboard. > **[Configuring Blinq](/integrations/marketo/configuring-blinq)** > > Control how Blinq syncs contacts, tags, and campaigns to Marketo, and how contacts are shared. > **[Field reference](/integrations/marketo/field-reference)** > > Contact field mapping, custom fields, and deduplication behavior. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for Marketo Source: https://docs.blinq.me/integrations/marketo/configuring-blinq Control how Blinq syncs contacts, tags, and campaigns to Marketo, and how contacts are shared. ## Configuring Blinq Once connected, you can control how Blinq syncs data to Marketo. Toggle any option on or off at any time from **Settings → Integrations → Marketo**. | Setting | Behavior | | - | - | | Automatically update contacts in Marketo | When a contact is edited in Blinq, the matching Lead record is updated. | | Sync contact tags | Contact, workspace, and campaign tags are written to custom fields on the Lead record. | | Auto export new contacts | On: every new Blinq contact is exported automatically. Off: export manually from **All company contacts**. | | Campaign sync | Link a Blinq campaign to a Marketo Program. Leads captured during the campaign window are added to the Program automatically. | ### Controlling who can export Team member exporting is a per-integration setting. When it's turned off, only admins can export contacts to Marketo. ## Sharing contacts to Marketo > [!NOTE] > > Blinq automatically shares contacts captured on a team card with your team. No manual sharing required. Export contacts to Marketo from **Blinq → Contacts → All company contacts**. Blinq doesn't export your personal contacts to Marketo unless you've shared them with your team. If you haven't shared a contact with your organization yet, you can share it from the **Share** menu on the individual contact record, in the dashboard or Blinq app. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Marketo for Blinq Source: https://docs.blinq.me/integrations/marketo/configuring-marketo Create the API-only user and LaunchPoint service that Blinq uses to connect to Marketo. > [!NOTE] > > Complete these steps before you [connect Marketo in your Blinq dashboard](/integrations/marketo/connecting-marketo). You'll finish with three values to paste into Blinq: a **Client ID**, a **Client Secret**, and an **Identity URL**. Marketo doesn't offer a sign-in-and-authorize flow. Instead, a Marketo admin creates a set of API credentials in Marketo and enters them into Blinq once. **1. Create a role with API access** * In Marketo, go to **Admin → Users & Roles**. * Open the **Roles** tab and create a role with API access permissions. * If you already have a role set up for API access, you can reuse it. **2. Create an API-only user** * Open the **Users** tab. * Create a new API-only user and assign it the role from the previous step. **3. Create a LaunchPoint service** * Go to **Admin → Integration → LaunchPoint**. * Select **New → New Service**. * Set the service type to **Custom** and give it a name, for example `Blinq`. * Attach the API-only user you created. **4. Copy the Client ID and Client Secret** Select your new service and click **View Details** to reveal the **Client ID** and **Client Secret**. **5. Copy the Identity URL** Go to **Admin → Integration → Web Services** and copy the **Identity URL** shown under the REST API section. > [!TIP] > > **You now have the three credentials Blinq needs.** Next, [enter them in your Blinq dashboard](/integrations/marketo/connecting-marketo). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Marketo to Blinq Source: https://docs.blinq.me/integrations/marketo/connecting-marketo Enter your Marketo API credentials in your Blinq dashboard. > [!NOTE] > > Before you start, you'll need a **Client ID**, **Client Secret**, and **Identity URL** from Marketo. See [Configuring Marketo](/integrations/marketo/configuring-marketo). **1. Open Settings** * In the Blinq dashboard, navigate to **Settings** in the left-hand menu. * Select the **Integrations** tab. * Click **Connect** on the Marketo integration. **2. Enter your credentials** Paste your **Client ID**, **Client Secret**, and **Identity URL** into the fields shown. **3. Save** Click **Save**. Blinq validates the credentials immediately by performing a test authentication, so if any detail is wrong you'll see an error before anything is saved. > [!TIP] > > **Marketo is now connected to Blinq.** Your Blinq dashboard opens with the Marketo integration settings visible, ready to [configure](/integrations/marketo/configuring-blinq). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Marketo field reference Source: https://docs.blinq.me/integrations/marketo/field-reference Contact field mapping, custom fields, and deduplication behavior for the Blinq Marketo integration. > [!NOTE] > > Blinq syncs contact data to standard fields on the Marketo Lead record. Tags and custom lead form responses map to custom Marketo fields. ## Contact field mapping If the following information is present on the Blinq contact, Blinq syncs it to the corresponding Marketo Lead field. | Blinq contact field | Marketo Lead field | | - | - | | Email | `email` | | First name | `firstName` | | Last name | `lastName` | | Job title | `title` | | Company | `company` | | Phone | `phone` | | Mobile phone | `mobilePhone` | | Website | `website` | Tags and custom lead form responses map to custom Marketo fields through the field mapper. To customize which fields Blinq syncs and how they map, see [Blinq field mapping](/features/field-mapping). ## Custom fields When tag sync is enabled, Blinq writes contact tags, workspace tags, and campaign tags to custom fields on the Lead record. Campaign membership is handled separately: a Blinq campaign links to a Marketo Program, and leads captured during the campaign window are added to that Program. ## Deduplication Contact deduplication is always on. When an exported contact matches an existing Lead, matched on exact email address, Blinq updates that record rather than creating a duplicate. A contact without an email address won't export. Your Marketo instance has the final say on every export. Duplicate rules, required fields, and validation configured in Marketo can change how a record is matched or block an export entirely. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq monday.com integration overview Source: https://docs.blinq.me/integrations/monday Export contacts captured in Blinq onto a monday.com board automatically, with tags, campaigns, and notes. > [!NOTE] > > The monday.com integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our monday.com integration connects Blinq to your monday.com account. Contacts your team captures — at events, in meetings, or through lead capture forms — export into monday.com automatically as items on a board you choose, along with their tags, campaigns, and notes. It's a native integration, so it behaves the same way as our Salesforce, HubSpot, Dynamics, GoHighLevel, Marketo, Zoho, and Pipedrive connections. monday.com isn't a traditional CRM — everything lives on a board — so Blinq writes into whichever board your team already runs its pipeline on, rather than a fixed contacts object. Sync is one-way. Contacts move from Blinq into monday.com, and changes made in monday.com don't come back to Blinq. > [!NOTE] > > Blinq installs its monday.com app for you during the connection flow, so there's nothing to install from the monday.com marketplace first. ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to connect monday.com and change its settings. * You'll need to be an account admin in the monday.com account you're connecting. Installing an app is an account-admin action in monday.com. * You'll need at least one company contact in your Blinq workspace. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Export contacts to monday.com | Yes | Items on the board you choose | | Auto export new Blinq contacts | Yes | Toggle in integration settings | | Sync Blinq notes | Yes | Toggle on/off. AI Notetaker summaries aren't included | | Sync Blinq contact, workspace, and campaign tags | Yes | Toggle on/off | | Campaign attribution | Yes | Arrives as a label in the Blinq Campaigns column | | Blinq card link | Yes | Included with the contact | | Custom field mapping | Yes | Field mapper, including custom board columns | | Deduplication | Yes | Matches on email, re-exports update the same item | | Connect more than one monday.com account | No | One account and one board per Blinq workspace | > [!NOTE] > > **Nothing for your team to set up.** An admin connects monday.com once for the workspace. Members configure nothing, and contacts they capture on iOS or Android flow through automatically once auto export is on. monday.com can run alongside Salesforce, HubSpot, Dynamics, or any other connected integration. A captured contact exports to every platform you've connected. ## Things to know * **One board per workspace.** Changing the board clears your existing field mapping. Blinq warns you before the change is applied. * **Tag names lose their spaces.** monday.com strips spaces from tag names, so "Trade Show" arrives as "TradeShow". * **Some column types can't be mapped.** People, board relation, formula, mirror, and tags columns aren't available in the field mapper. * **Items are created by the connecting admin.** Every item is added as the monday.com user who connected the integration, so owner columns aren't filled in. * **Free and Standard monday.com plans cap API usage** at 1,000 calls a day, so a very large bulk export may rate-limit and retry. * **App review notice.** Until Blinq is listed on the monday.com marketplace, monday.com shows a notice that the app hasn't been reviewed or approved by monday.com. The connection still works normally. ## Documentation for our monday.com integration > **[Connecting monday.com](/integrations/monday/connecting-monday)** > > Connect your monday.com account and pick the board your contacts land on. > **[Configuring Blinq](/integrations/monday/configuring-blinq)** > > Choose your board and group, map your columns, and control what syncs. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for monday.com Source: https://docs.blinq.me/integrations/monday/configuring-blinq Choose the board and group your contacts land on, map your monday.com columns, and control what syncs. Open **Settings → Integrations → monday.com** to control where contacts land and what reaches them. These settings apply to your whole workspace, so a change here affects every rep's exports. ## Choosing your board and group **Board** decides which monday.com board receives your contacts. Each contact arrives as an item on that board. **Group** is the section within that board the items are added to — "New Leads", for example. Blinq picks a board and group for you when you connect, so you only change these if you want a different destination. > [!WARNING] > > **Changing the board clears your field mapping.** Columns differ from board to board, so Blinq can't carry your mapping across. You'll be warned before the change is applied, and you'll need to map your columns again afterwards. ## Mapping your columns The [field mapper](/features/field-mapping) decides where each Blinq field lands on your board. It pulls that board's live column list, including any custom columns you've set up in monday.com. Email, phone, job title, and company are mapped for you by default. To change a mapping, pick a different monday.com column on that row. To add one, select **Add mapping**, then choose the Blinq field and the monday.com column to pair. > [!NOTE] > > Map your columns 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 items in monday.com afterwards. Some monday.com column types can't be mapped. People, board relation, formula, mirror, and tags columns aren't available in the field mapper. ## What reaches monday.com Each exported contact carries across their contact details, along with the notes recorded against them in Blinq, their tags, the campaign they were captured in, and a link to their Blinq card. Two monday.com behaviours are worth knowing about. Tag names lose their spaces, so "Trade Show" arrives as "TradeShow". And because monday.com has no campaigns object, the campaign a contact was captured in arrives as a label in the Blinq Campaigns column rather than a linked record. ## How new contacts sync Turn **Auto export** on to send each new contact to monday.com as it's captured. Leave it off if you'd rather review contacts first and push them across yourself. Select **Sync contacts** to push your existing contacts on demand. You can also export a single contact, or select several and export them together, from your contacts list. ## Deduplication Blinq matches on email address. If a contact is exported again, Blinq updates the existing item on your board rather than creating a second one. ## Saving your settings Select **Save** to apply your changes. ## If contacts aren't arriving Check these in order: 1. **Is the board still there?** If the board has been deleted or archived in monday.com, the integration shows **Select a board** and exports fail. Pick a new board, then select **Sync contacts** to re-export the ones that failed. 2. **Has the connection expired?** A **Reconnect** prompt on the Integrations page means the token has expired. Reconnect and exports resume. 3. **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. 4. **Was it a large bulk export?** Free and Standard monday.com plans cap at 1,000 API calls a day, so a very large export may rate-limit and retry. A failed export shows **Last failed** against the contact. If none of the checks above explain it, email [support@blinq.me](mailto:support@blinq.me) with the affected email addresses and roughly when the contacts were captured. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting monday.com to Blinq Source: https://docs.blinq.me/integrations/monday/connecting-monday Connect your monday.com account from the Blinq dashboard and choose the board your contacts land on. Connecting monday.com takes one pass through a monday.com pop-up. There are no API keys or tokens to copy, and you don't need to install anything from the monday.com marketplace first. ## Connect monday.com in Blinq **1. Open your integrations** In the Blinq [dashboard](https://dash.blinq.me), go to **Settings**, then the **Integrations** tab. **2. Start the connection** Under **Export contacts**, find **monday.com** and select **Connect**. A monday.com pop-up opens. **3. Install and authorise** Sign in to monday.com if you aren't already. Blinq installs its monday.com app in the same pop-up, then shows the consent screen. Review the access Blinq needs and confirm. **4. Pick your board** The pop-up closes and your monday.com settings open in Blinq, with a board already selected — usually your Leads or Contacts board. Choose a different board or group if you'd rather, then select **Save**. > [!TIP] > > **monday.com is connected.** Next, [choose your board and map your columns](/integrations/monday/configuring-blinq). > [!NOTE] > > To check everything works, capture or create a test contact and watch it appear on your monday.com board. > [!WARNING] > > **You need to be a monday.com account admin.** Installing an app is an account-admin action in monday.com, not something Blinq controls. If you aren't an admin there, the pop-up returns "App is not installed" — ask a monday.com admin to run the connection. > [!WARNING] > > **One monday.com account per Blinq workspace.** You can't connect two monday.com accounts to the same Blinq workspace. If you run more than one and need contacts in both, talk to [support@blinq.me](mailto:support@blinq.me) before you set this up. > [!NOTE] > > **"This app hasn't been reviewed or approved by monday.com."** You'll see this notice on the consent screen until Blinq is listed on the monday.com marketplace. The connection works normally, and the notice disappears once our listing is live. ## Who connects it An admin or owner connects and disconnects monday.com at the workspace level. Nobody else on your team needs to do anything — reps don't install anything or sign in to monday.com, and contacts they capture on the mobile apps sync through automatically once the connection is live. ## Reconnecting monday.com refresh tokens expire after three months without use, so a workspace that has been idle sees a **Reconnect** prompt on the Integrations page. Reconnect once and your exports pick up where they left off. > [!NOTE] > > Don't see monday.com under **Export contacts**? Check your plan first, then contact [support@blinq.me](mailto:support@blinq.me). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Outlook integration overview Source: https://docs.blinq.me/integrations/outlook Export contacts captured in Blinq into your team's Outlook address books, with notes and tags. > [!NOTE] > > The Outlook integration is available on **Business** plans. [View pricing →](https://blinq.me/pricing) Our Outlook integration connects Blinq to your organisation's Microsoft 365 environment. Contacts your team captures — at events, in meetings, or through lead capture forms — export into Outlook as contacts, along with the notes and tags recorded against them in Blinq. Sync is one-way. Contacts move from Blinq into Outlook, and changes made in Outlook don't come back to Blinq. ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to connect Outlook and change its settings. * You'll need an account with **administrator access to your Microsoft 365 tenant** to authorise the connection. * Each team member's Blinq profile email must exactly match their Microsoft 365 mailbox address, or their contacts won't sync. * You'll need at least one company contact in your Blinq workspace. ## Where contacts land Contacts sync into the Outlook address book of the person who captured them, not into a shared company-wide list. Someone who captures a contact at an event finds it in their own Outlook contacts; their colleagues don't. > [!WARNING] > > **Microsoft doesn't allow any third-party app to write to the Global Address List.** A single shared company record in the GAL isn't possible through Blinq, or through any other tool. What Blinq can do is write into individual mailboxes. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Export contacts to Outlook | Yes | — | | Auto export new Blinq contacts | Yes | **Automatically export new contacts** | | Sync updates to contacts from Blinq to Outlook | Yes | **Automatically sync contact updates** | | Export contacts on demand | Yes | **Export Contacts → To Outlook** on the Contacts page | | Sync Blinq notes and AI Notetaker summaries | Yes | Arrive in the Outlook contact's notes field | | Sync Blinq contact, workspace, and campaign tags | Yes | Arrive as Outlook categories | | Custom field mapping | No | Blinq sends a standard set of contact details | | Write to the Global Address List | No | Not possible for any third-party app | > [!NOTE] > > **Already-exported contacts are updated, not duplicated.** Exporting the same contact again refreshes the existing Outlook record. ## Contacts that never export A contact only exports if it's a **company contact**, and it only becomes one if the person who captured it was using a team card. Someone with no card, or using a personal card, has their captures saved as personal contacts — which never reach Outlook, and never produce an error to say so. If a team member's contacts aren't arriving, check they have a team card assigned before checking anything else. Outlook can run alongside Salesforce, HubSpot, Dynamics, or any other connected integration. A captured contact exports to every platform you've connected. ## Documentation for our Outlook integration > **[Connecting Outlook](/integrations/outlook/connecting-outlook)** > > Authorise Blinq against your Microsoft 365 tenant. > **[Configuring Blinq](/integrations/outlook/configuring-blinq)** > > Control when contacts export and how to export on demand. > **[Email signatures](/integrations/outlook/email-signatures)** > > Add a Blinq email signature to Outlook, on your own or across your team. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for Outlook Source: https://docs.blinq.me/integrations/outlook/configuring-blinq Control when contacts export to Outlook, keep existing records updated, and export on demand. Open **Settings → Integrations → Outlook** to control how contacts export. These settings apply to your whole workspace. ## Export settings | Setting | Behavior | | - | - | | **Automatically export new contacts** | New Blinq contacts sync to Outlook as they're captured. | | **Automatically sync contact updates** | Changes made to a contact in Blinq are pushed to the matching Outlook record. | Turn the options on or off, then select **Save**. ## Exporting on demand You can export at any time without waiting for new captures: **1. Open your contacts** Go to the **Contacts** page in the Blinq dashboard. **2. Choose Outlook** Select the **Export Contacts** dropdown, then **To Outlook**. **3. Start the export** Select **Export contacts**. > [!NOTE] > > Contacts that have already been exported are updated rather than duplicated, so it's safe to run this more than once. ## What reaches Outlook Each exported contact carries across their name, email address, phone number, job title and company, along with any notes recorded in Blinq — including AI Notetaker summaries — and their Blinq tags, which arrive as Outlook categories. > [!WARNING] > > **Notes arrive as plain text.** Outlook's notes field doesn't accept formatting, so anything styled in Blinq is flattened when it exports. ## If a team member's contacts aren't arriving Check these in order: 1. **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. 2. **Does their Blinq profile email match their Microsoft 365 mailbox exactly?** Contacts sync into the mailbox of the person who captured them, matched on that address. 3. **Is anyone listed against the contact in the Created by column?** Contacts with no creator aren't exported. If all three check out, email [support@blinq.me](mailto:support@blinq.me) with the affected email addresses and roughly when the contacts were captured. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Outlook to Blinq Source: https://docs.blinq.me/integrations/outlook/connecting-outlook Authorise Blinq against your Microsoft 365 tenant and choose whether to export your existing contacts. Connecting Outlook is a single authorisation from your Blinq dashboard, done by someone with administrator access to your Microsoft 365 tenant. ## Connect Outlook in Blinq **1. Open your integrations** In the Blinq [dashboard](https://dash.blinq.me), go to **Settings**, then the **Integrations** tab. **2. Start the connection** Under **Export contacts**, find **Outlook** and select **Connect**. **3. Sign in to Microsoft** Sign in with an account that has administrator access to your Microsoft 365 tenant. **4. Grant consent** Review what Blinq is asking for and approve it for your organisation. **5. Choose whether to export now** Decide whether to export the contacts already in your workspace straight away. > [!TIP] > > **Outlook is connected.** It now shows a **Settings** button in your integrations list. Next, [choose when contacts export](/integrations/outlook/configuring-blinq). > [!WARNING] > > **Being an Exchange administrator often isn't enough.** The consent step covers your whole tenant, and in practice it usually needs a **Global Administrator**. If the sign-in works but consent fails, that's the reason — ask a Global Administrator to complete this step rather than retrying. ## Using a service account Because the connection belongs to the account that authorised it, it's worth using an account that will outlast any one person. A Microsoft administrator service account added to your Blinq workspace as an admin works well here. It doesn't need a card, and it doesn't change your billing. ## What Blinq asks for The consent screen covers reading and writing contacts across mailboxes in your tenant, because Microsoft doesn't offer a way to scope the permission to a subset of mailboxes. This comes up in security reviews — if your IT team needs the exact permissions in writing before approving, email [support@blinq.me](mailto:support@blinq.me) and support can supply them. > [!NOTE] > > Don't see Outlook under **Export contacts**? Check your plan first, then contact [support@blinq.me](mailto:support@blinq.me). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq email signatures in Outlook Source: https://docs.blinq.me/integrations/outlook/email-signatures Add a Blinq signature to Outlook yourself, or deploy the Blinq add-in across your team from the Microsoft 365 admin center. There are two ways to get a Blinq email signature into Outlook: each person adds it themselves, or your IT team deploys the Blinq add-in so everyone can pick up the signature assigned to them. Unlike [Google Workspace](/integrations/google-workspace), Blinq can't write signatures into Outlook mailboxes on its own. Someone installs the add-in, or someone pastes the signature — even when IT does the deployment, each person still opens the add-in once to collect theirs. ## Adding a signature yourself **1. Copy your signature from Blinq** In the Blinq [dashboard](https://dash.blinq.me), open **Email Signatures** and copy the signature assigned to you. **2. Open Outlook's signature settings** In Outlook on the web, open **Settings**, then **Mail**, then **Compose and reply**. **3. Paste it in** Paste your signature into the signature box, name it, and save. **4. Set it as your default** Choose it for new messages, and for replies and forwards if you want it there too. ## Deploying the Blinq add-in across your team The Blinq add-in is on the Microsoft marketplace. Your Microsoft 365 administrator can push it to everyone at once rather than asking each person to install it. **1. Create the signatures in Blinq first** An admin creates each team member's signature in Blinq and assigns it to them. Nothing appears in the add-in until a signature has been assigned. **2. Open the add-in listing** In the Blinq [dashboard](https://dash.blinq.me), go to **Settings → Integrations** and select **Connect** under **Outlook** in the Email signatures section. This opens the Blinq listing on the Microsoft marketplace. **3. Deploy the add-in** In the Microsoft 365 admin center, go to **Settings → Integrated apps** and deploy the Blinq add-in to your organisation. **4. Wait for it to reach everyone** Deployment can take up to 24 hours to propagate, and people may need to restart Outlook before the add-in appears. **5. Each person collects their signature** Team members open the Blinq add-in in Outlook, sign in to their Blinq account, and select the signature assigned to them. > [!WARNING] > > **This isn't a silent push.** Deploying the add-in makes it available to everyone, but each person still opens it once and signs in to apply their signature. If you need signatures applied without anyone touching them, that's only possible with Google Workspace today. ## Things worth knowing * **HTML signatures are switched on by request.** By default a Blinq signature is a single image linking to your card. Email [support@blinq.me](mailto:support@blinq.me) to have HTML signatures enabled for your workspace. * **Mobile doesn't render them.** The Outlook mobile app only supports plain text signatures. Apple Mail on iPhone is currently the only mobile client that displays a Blinq signature. * **Signatures aren't linked to cards.** Updating someone's card later doesn't change a signature already created from it — edit the signature itself. * **Signing in on Outlook mobile takes an extra step.** Outlook add-ins don't support single sign-on on mobile, so the add-in asks you to sign in even when Outlook already knows who you are. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Pipedrive integration overview Source: https://docs.blinq.me/integrations/pipedrive Export contacts captured in Blinq to Pipedrive automatically, with tags, campaigns, and notes. > [!NOTE] > > The Pipedrive integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our Pipedrive integration connects Blinq to your Pipedrive account. Contacts your team captures — at events, in meetings, or through lead capture forms — export into Pipedrive as Persons, along with their tags, campaigns, and notes, including AI Notetaker summaries. You can also have Blinq create a linked Lead in your Leads Inbox for each one. It's a native integration, so it behaves the same way as our Salesforce, HubSpot, Dynamics, GoHighLevel, Marketo, Zoho, and monday.com connections. Sync is one-way. Contacts move from Blinq into Pipedrive, and changes made in Pipedrive don't come back to Blinq. > [!NOTE] > > **Connected Pipedrive before with a subdomain and API token?** That's the older Pipedrive connection, which only sent name, email, and phone. You'll see a warning and an **Upgrade** button on the Pipedrive card on your workspace's **Settings → Integrations** page. See [Upgrading an existing connection](/integrations/pipedrive/connecting-pipedrive#upgrading-an-existing-connection). ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to connect Pipedrive and change its settings. * You'll need to sign in to the Pipedrive account you're connecting and approve Blinq's access. * You'll need at least one company contact in your Blinq workspace. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Export contacts to Pipedrive | Yes | Created as Persons, or updates the existing Person | | Create a linked Lead in the Leads Inbox | Yes | Turn on **Export to Leads/Contacts** | | Auto export new Blinq contacts | Yes | Automatic, or hold for manual review | | Choose who can review held contacts | Yes | Admins only, or all members | | Sync Blinq notes and AI Notetaker summaries | Yes | Toggle on/off | | Sync Blinq contact, workspace, and campaign tags | Yes | Toggle on/off. Arrive in the **Blinq Tags** field | | Campaign attribution | Yes | Arrives in the **Blinq Campaigns** field on the Person | | Custom field mapping | Yes | Field Mapper, including custom Person and Lead fields | | Deduplication | Yes | Matches the stored Pipedrive record, then the primary email | | Contact owner | Yes | Matched to a Pipedrive user by email | | Connect more than one Pipedrive account | No | One Pipedrive connection per Blinq workspace | > [!NOTE] > > **Nothing for your team to set up.** An admin connects Pipedrive once for the workspace. Members configure nothing, and contacts they capture on iOS or Android flow through automatically once automatic export is on. Pipedrive can run alongside Salesforce, HubSpot, Dynamics, or any other connected integration. A captured contact exports to every platform you've connected. ## Things to know * **Company becomes an Organization.** Pipedrive Persons don't have a free-text company field, so Blinq links each contact to an Organization with exactly the same name, and creates one if there isn't one. * **Campaigns arrive as a field, not a record.** Pipedrive has no campaigns object, so the campaign name lands in the **Blinq Campaigns** field on the Person. There's no campaign picker. * **Website isn't mapped by default.** Pipedrive Persons don't have a standard website field. Map it to a custom field in Field Mapper if you need it. * **Large bulk exports can slow down.** Pipedrive limits how many API requests an account can make each day, based on its plan and number of seats, so a very large export on a smaller Pipedrive plan may pause and retry. ## Documentation for our Pipedrive integration > **[Connecting Pipedrive](/integrations/pipedrive/connecting-pipedrive)** > > Sign in to Pipedrive, approve access, or upgrade an older connection. > **[Configuring Blinq](/integrations/pipedrive/configuring-blinq)** > > Choose how contacts sync, map your fields, and control what reaches Pipedrive. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for Pipedrive Source: https://docs.blinq.me/integrations/pipedrive/configuring-blinq Choose how contacts sync to Pipedrive, map your Pipedrive fields, and control what reaches each Person. Open **Settings → Integrations → Pipedrive → Settings** to control how contacts export. These settings apply to your whole workspace, so a change here affects every rep's exports. ## How new contacts sync | Setting | Behavior | | - | - | | Automatic | New contacts export to Pipedrive as they're captured. | | Manual review | New contacts are held in Blinq until someone approves them. | Manual review is worth using while you're getting started, or when your team captures contacts somewhere the quality varies — a busy trade show stand, for example. Nothing reaches Pipedrive until a person has looked at it. ## Who can review held contacts When you choose **Manual review**, a second setting appears for who can review those contacts and send them to Pipedrive: **admins only**, or **all members**. ## Creating Leads Blinq always creates or updates a Person in Pipedrive. Turn on **Export to Leads/Contacts** to also create a linked Lead in your Leads Inbox for each contact. ## Syncing tags and notes Turn **Sync tags** on to send each contact's contact, workspace, and campaign tags to the **Blinq Tags** field on the Person. Turn **Sync notes** on to send the notes recorded against a contact in Blinq, including AI Notetaker summaries. ## Mapping your fields Open the **Field Mapper** tab to decide where each Blinq field lands in Pipedrive. The [field mapper](/features/field-mapping) pulls in your Pipedrive Person and Lead fields, including any custom fields you've set up. To change a mapping, pick a different Pipedrive field on that row. To add one, select **Add mapping**, then choose the Blinq field and the Pipedrive field to pair. > [!NOTE] > > Website isn't mapped by default, because Pipedrive Persons don't have a standard website field. If your team needs it, create a custom field in Pipedrive and map website to it. Map your fields before you export in bulk, so contacts arrive in Pipedrive the way your team expects. ## What reaches Pipedrive * **Contact details.** Each contact becomes a Person, or updates the existing one, using your field mapping. * **Leads.** With **Export to Leads/Contacts** on, a linked Lead is also created in the Leads Inbox. * **Company.** Pipedrive Persons don't have a free-text company field, so Blinq links the contact to an Organization. It looks for an Organization with exactly the same name and creates one if there isn't one. If several share that name, the first is used. If an Organization can't be created, the contact still exports without one. * **Tags.** Contact, workspace, and campaign tags go to the **Blinq Tags** field on the Person. * **Campaigns.** Pipedrive has no campaigns object, so the name of the campaign a contact was captured in goes to the **Blinq Campaigns** field on the Person. There's no campaign picker. If you unlink a campaign in Blinq, new contacts stop being labelled with it, but contacts you've already exported keep the label. * **Notes.** Notes, including AI Notetaker summaries, are added to the Person. * **Owner.** Blinq matches the contact's owner in Blinq to a Pipedrive user by email. If there's no match, the record is assigned to the person who connected Pipedrive. ## Exporting contacts With **Automatic** on, each new contact exports as it's captured. You can also export a single contact, or select several and export them together, from your contacts list. ## Deduplication Blinq looks for an existing Person before creating a new one. It checks the Pipedrive record a contact was previously exported to first, then looks for an exact match on the contact's primary email. It doesn't match on name or phone. If a match is found, Blinq updates that Person rather than creating a second one. ## Saving your settings Select **Save** to apply your changes. ## If contacts aren't arriving Check these in order: 1. **Is the workspace still on the older connection?** A warning and an **Upgrade** button on the Pipedrive card mean your workspace still uses the subdomain and API token connection. [Upgrade it](/integrations/pipedrive/connecting-pipedrive#upgrading-an-existing-connection) to get tags, campaigns, notes, and field mapping. 2. **Is the contact held for review?** With **Manual review** on, new contacts wait in Blinq until someone sends them to Pipedrive. 3. **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. 4. **Was it a large bulk export?** Pipedrive caps daily API usage based on your Pipedrive plan and seats, so a very large export may pause and retry. If none of these explain it, email [support@blinq.me](mailto:support@blinq.me) with the affected email addresses and roughly when the contacts were captured. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Pipedrive to Blinq Source: https://docs.blinq.me/integrations/pipedrive/connecting-pipedrive Sign in to Pipedrive from your Blinq dashboard and approve access, or upgrade an older Pipedrive connection. Connecting Pipedrive takes one pass through a Pipedrive pop-up. There's no subdomain or API token to copy, and nothing to install from the Pipedrive Marketplace first. ## Connect Pipedrive in Blinq **1. Open your integrations** In the Blinq [dashboard](https://dash.blinq.me), go to **Settings**, then the **Integrations** tab. **2. Start the connection** Under **Export contacts**, find **Pipedrive** and select **Connect**. A Pipedrive pop-up opens. **3. Sign in and approve access** Sign in to Pipedrive if you aren't already, review the access Blinq needs, and approve it. **4. Check the connection** The pop-up closes and Pipedrive shows as connected in your integrations list. > [!TIP] > > **Pipedrive is connected.** Next, [choose your sync settings and map your fields](/integrations/pipedrive/configuring-blinq). > [!NOTE] > > To check everything works, turn on automatic export, then capture or create a test contact and watch it appear as a Person in Pipedrive. > [!WARNING] > > **One Pipedrive connection per Blinq workspace.** You can't connect two Pipedrive accounts to the same Blinq workspace. If you run more than one and need contacts in both, talk to [support@blinq.me](mailto:support@blinq.me) before you set this up. ## Upgrading an existing connection If your workspace connected Pipedrive with the older method, using a Pipedrive subdomain and API token, you'll see a warning on the Pipedrive card in your integrations list. That connection only sends name, email, and phone. Upgrading moves you to the native integration, so tags, campaigns, notes, and field mapping come across too. **1. Open your integrations** In the Blinq [dashboard](https://dash.blinq.me), go to **Settings**, then the **Integrations** tab. **2. Select Upgrade** On the Pipedrive card, select **Upgrade**. A Pipedrive pop-up opens. **3. Sign in to the same Pipedrive account** Sign in to the Pipedrive account you were already exporting to, and approve access. Your settings, export history, and notes carry over, and contacts you've already exported are updated in Pipedrive rather than duplicated. A workspace can't run the older connection and the native one at the same time. ## Who connects it An admin or owner connects and disconnects Pipedrive at the workspace level. Nobody else on your team needs to do anything — reps don't install anything or sign in to Pipedrive, and contacts they capture on the mobile apps sync through automatically once automatic export is on. ## Disconnecting An admin or owner can disconnect Pipedrive from the same **Integrations** tab. Disconnecting also removes Blinq's access on the Pipedrive side, so the Blinq app shows as uninstalled in Pipedrive. > [!NOTE] > > Don't see Pipedrive under **Export contacts**? Check your plan first, then contact [support@blinq.me](mailto:support@blinq.me). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Salesforce integration overview Source: https://docs.blinq.me/integrations/salesforce Connect your Blinq contacts directly to Salesforce so captured contacts flow into your CRM automatically. > [!NOTE] > > The Salesforce integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our Salesforce integration connects your Blinq contacts directly to Salesforce. Contacts captured in Blinq flow into your CRM automatically, complete with notes, tags, and campaign attribution. Your team gets clean, contextual data where they already work, without manual exports. You can install and configure the Salesforce integration from your [Blinq dashboard](/integrations/salesforce/connecting-salesforce). ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to set up and manage the Salesforce integration. * You'll need a Salesforce account with **System Administrator** permissions, or a custom profile with **API Enabled**, **Author Apex**, and **Manage Connected Apps** permissions. * Blinq's Salesforce integration is available on **Business** and **Enterprise** plans. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Sync updates to contacts from Blinq to Salesforce automatically | Yes | Toggle on/off | | Sync Blinq contact notes | Yes | Toggle on/off | | Sync Blinq contact tags | Yes | Toggle on/off | | Auto export new Blinq contacts | Yes | Toggle on/off | | Export contacts as Leads or Contacts | Yes | Toggle in integration settings (Contacts by default) | | Assign contact owner in Salesforce | Yes | Matched to Blinq owner | | Contact de-duplication | Yes | Matched on unique email address | | Campaign sync | Yes | Link Blinq campaign to a Salesforce campaign | | Custom field mappings | Yes | Toggle in integration settings | | Sync AI Notetaker summaries | Yes | Toggle in integration settings | ## Documentation for our Salesforce integration > **[Connecting Salesforce](/integrations/salesforce/connecting-salesforce)** > > Install the Salesforce integration from your Blinq dashboard. > **[Configuring Blinq](/integrations/salesforce/configuring-blinq)** > > Control how Blinq syncs contacts, notes, and tags to Salesforce, and how contacts are shared. > **[Configuring Salesforce](/integrations/salesforce/configuring-salesforce)** > > Enable Notes and add Blinq fields to your Contact and Lead page layouts. > **[Field reference](/integrations/salesforce/field-reference)** > > Contact field mapping, custom fields, and deduplication behavior. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for Salesforce Source: https://docs.blinq.me/integrations/salesforce/configuring-blinq Control how Blinq syncs contacts, notes, and tags to Salesforce, and how contacts are shared. ## Configuring Blinq > [!NOTE] > > Once you export a Blinq contact to Salesforce, it keeps its original type. A Lead stays a Lead and a Contact stays a Contact. Once connected, you can control how Blinq syncs data to Salesforce. Toggle any option on or off at any time from **Settings → Integrations → Salesforce**. ### Export contacts as Contacts or Leads Choose whether Blinq exports your contacts to Salesforce as **Contacts** or **Leads**. You can update this setting at any time in your integration settings. ### Automatically update changes to Blinq contacts in Salesforce When enabled, Blinq automatically updates Salesforce whenever you change a contact's details. Your CRM stays current without manual re-entry. ### Sync contact notes When enabled, Blinq syncs notes from a contact to Salesforce as Notes on the associated Contact or Lead record. ### Sync contact tags When enabled, Blinq syncs tags from a contact (including contact tags, workspace tags, and campaign tags) to custom fields on the Salesforce record. ### Automatically export new Blinq contacts to Salesforce When enabled, Blinq automatically exports every new contact to Salesforce. When disabled, you can still export contacts one at a time from **All company contacts**. ## Sharing contacts to Salesforce > [!NOTE] > > Blinq automatically shares contacts captured on a team card with your team. No manual sharing required. Export contacts to Salesforce from **Blinq → Contacts → All company contacts**. Blinq doesn't export your personal contacts to Salesforce unless you've shared them with your team. If you haven't shared a contact with your organization yet, you can share it from the **Share** menu on the individual contact record, in the dashboard or Blinq app. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Salesforce for Blinq Source: https://docs.blinq.me/integrations/salesforce/configuring-salesforce Enable Notes and add Blinq fields to your Contact and Lead page layouts. Once you connect Blinq, there are two things to set up on the Salesforce side: enabling Notes so Blinq can sync them, and adding Blinq's custom fields to your Contact or Lead page layout so they're visible in Salesforce. Access both from the **Setup** menu in Salesforce. ## Enable Notes in Salesforce Blinq syncs contact notes to Salesforce as Notes on the associated record. You need to enable Notes in your Salesforce account; without it, note sync won't work. **1. Open Setup** In Salesforce, click the **Setup** gear icon in the top right. **2. Find Notes Settings** In the Setup search bar, type **Notes Settings**. **3. Enable Notes** Check **Enable Notes** and save your changes. ## Add Blinq fields to your page layout > [!NOTE] > > For additional guidance on editing page layouts, see the [Salesforce Help Center](https://help.salesforce.com). When you connect Blinq, it automatically creates the following custom fields in your Salesforce account. They won't appear in your Contact or Lead views until you add them to your page layout. Blinq creates the following fields automatically in Salesforce: * **Blinq Contact Tags:** contact-level tags applied in Blinq. * **Blinq Workspace Tags:** workspace-level tags. * **Blinq Campaign Tags:** campaign tags from linked Blinq campaigns. * **Blinq Campaigns:** campaign names. * **Blinq Card Link:** a direct link to the contact's Blinq card. You'll also want to add **Notes** to your page layout. Blinq contact notes sync directly into the native Notes feature in Salesforce, but Notes may not appear on Contact or Lead records by default. To add Blinq fields to your page layout: **1. Open Setup** In Salesforce, click the **Setup** gear icon in the top right. **2. Open Object Manager** In the Quick Find search box, type **Object Manager**. **3. Select your object** Select **Lead** or **Contact** depending on how you'd like to sync your Blinq contacts to Salesforce. **4. Open Page Layouts** Click **Page Layouts** in the left sidebar, then select the layout you want to update. **5. Add Blinq fields** In the layout editor, find the **Fields** section in the palette on the left. Search for **Blinq** to filter the custom fields. Drag each Blinq field from the palette onto the layout where you'd like it to appear. **6. Add Notes** To add Notes, scroll to the **Related Lists** section of the palette and drag **Notes & Attachments** onto the layout. **7. Click Save and you're done.** *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Salesforce to Blinq Source: https://docs.blinq.me/integrations/salesforce/connecting-salesforce Install the Salesforce integration from your Blinq dashboard. **1. Open Settings** * In the Blinq dashboard, navigate to **Settings** in the left-hand menu. * Select the **Integrations** tab. * Click **Connect** on the Salesforce integration. **2. Sign in to Salesforce** A pop-up window opens. Sign in to your Salesforce account using administrator credentials. **3. Select your Salesforce account** If you have access to multiple Salesforce accounts, select the account you'd like to connect to Blinq. **4. Confirm** Once authorized, close the pop-up window. Your Blinq dashboard opens with the Salesforce integration settings visible. > [!TIP] > > **Salesforce is now connected to Blinq.** *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Salesforce field reference Source: https://docs.blinq.me/integrations/salesforce/field-reference Contact field mapping, custom fields, and deduplication behavior for the Blinq Salesforce integration. > [!NOTE] > > Blinq syncs contact data to Salesforce fields on the Contact or Lead record, depending on your export type setting. Blinq creates these custom fields automatically when you connect the integration. ## Contact field mapping If the following information is present on the Blinq contact, Blinq syncs it to the corresponding Salesforce field. | Blinq contact field | Salesforce field | | - | - | | Name | Name | | Job title | Title | | Company | Company (Lead) / Account Name (Contact) | | Email (first/primary) | Email | | Phone number | Phone / Mobile | | Address | Address | | Company website/URL (first) | Website | | Blinq Card URL | Blinq Card Link (custom field) | | Contact tags | Blinq Contact Tags (custom field) | | Workspace tags | Blinq Workspace Tags (custom field) | | Campaign tags | Blinq Campaign Tags (custom field) | | Campaigns | Blinq Campaigns (custom field) | | Notes | Notes (on Contact or Lead record) | To customize which fields Blinq syncs and how they map, see [Blinq field mapping](/features/field-mapping). ## Custom fields created by Blinq Blinq creates the following custom fields in Salesforce when you connect the integration. These fields appear on both Contact and Lead records. | Field name | Description | | - | - | | Blinq Card Link | A direct link to the contact's Blinq card | | Blinq Contact Tags | Contact-level tags applied in Blinq | | Blinq Workspace Tags | Workspace-level tags | | Blinq Campaign Tags | Campaign tags from linked Blinq campaigns | | Blinq Campaigns | Names of linked Blinq campaigns | ## Deduplication When you export a Blinq contact to Salesforce, Blinq looks for an existing record with the same email address, and falls back to phone number if there's no email. If Blinq finds a record it already manages, it updates that record. Blinq never merges Leads and Contacts; combining them is a Salesforce action. If a matching record is already managed by another source, Blinq leaves it unchanged rather than overwriting it. Your CRM has the final say on every export. Duplicate and matching rules, required fields, and validation rules set up in your CRM can change how a record is matched, allow a duplicate to be created, or block an export entirely. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Zapier integration overview Source: https://docs.blinq.me/integrations/zapier Push Blinq contacts to Zapier the moment they're created or updated, and connect them to over 9,000 apps and tools. > [!NOTE] > > The Zapier integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our Zapier integration connects your Blinq contacts directly to Zapier. Blinq pushes your contacts to Zapier the moment they're created or updated, complete with notes and tags. From there you can structure them exactly as you need, across over 9,000 compatible apps and tools. You can install and configure the Zapier integration from your [Blinq dashboard](/integrations/zapier/connecting-zapier). ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to set up and manage the Zapier integration. * You'll need a Zapier account. Blinq is a free app on Zapier, so you don't need a paid Zapier plan to connect the two. The availability and usage limits of other integrations may still depend on your Zapier plan. * Blinq's Zapier integration is available on **Business** and **Enterprise** plans. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Trigger when a Blinq contact is created | Yes | New Contact trigger | | Trigger when a Blinq contact is updated | Yes | Updated Contact trigger | | Send Blinq contact notes | Yes | Mapped as fields in your Zap | | Send Blinq contact tags | Yes | Mapped as fields in your Zap | | Send campaign attribution | Yes | Mapped as fields in your Zap | | Enhanced field mapping | Yes | Toggle in Zapier | | Connect to over 9,000 other apps | Yes | Through your Zap's actions | ## Documentation for our Zapier integration > **[Connecting Zapier](/integrations/zapier/connecting-zapier)** > > Generate your Blinq authentication token and connect the Blinq app in Zapier. > **[Creating a trigger](/integrations/zapier/creating-a-trigger)** > > Configure a Blinq trigger so your Zap runs whenever a contact is created or updated. > **[Example configuration](/integrations/zapier/example-configuration)** > > A worked example using the New Contact trigger to build a row in Zapier Tables. > **[Output and field reference](/integrations/zapier/field-reference)** > > Every field Blinq sends to Zapier and how it appears in the Zap editor. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Zapier to Blinq Source: https://docs.blinq.me/integrations/zapier/connecting-zapier Generate your Blinq authentication token and connect the Blinq app in Zapier. **1. Open Settings** * In the Blinq dashboard, navigate to **Settings** in the left-hand menu. * Select the **Integrations** tab. * Click **Connect** on the Zapier integration. **2. Generate your authentication details** * Blinq displays your ID, with the option to generate or regenerate a token. * You need both credentials to connect the Blinq app in Zapier. **3. Add Blinq in Zapier** * Find and add the Blinq app in Zapier by searching for Blinq, or visit our app page directly: [zapier.com/apps/blinq/integrations](https://zapier.com/apps/blinq/integrations). * Once the app is installed, press **Add connection**. * A pop-up window opens. Authenticate and connect Blinq by pasting the ID and token from the previous step, then press **Connect**. * You should see a green circle and **Connected** under **Status** for the Blinq application in Zapier. **4. Test your connection** * You can test this connection at any time from your [Zapier connections](https://zapier.com/app/assets/connections/blinq) by clicking the three dots and selecting **Test connection**. > [!TIP] > > **Blinq is now connected to Zapier.** *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Creating a trigger in Zapier Source: https://docs.blinq.me/integrations/zapier/creating-a-trigger Configure a Blinq trigger so your Zap runs whenever a contact is created or updated. ## Configuring Zapier To start configuring Zapier with Blinq contacts, select **New Zap** from the Zapier dashboard, or manually navigate to **Home → Create → Zaps**. This opens the New Zap editor, where you can build a Zap workflow with AI or create each step manually. ## Creating a trigger **1. Create a Blinq trigger** * Click the **Trigger** event which is step 1 in a Zap workflow. * Select Blinq as the trigger. You can find it in the **Apps** menu, or search for Blinq in the top bar. **2. Select the trigger event** The integration has two options for trigger events: * **New Contact:** Triggers when a contact is created. * **Updated Contact:** Triggers when a contact is updated. **3. Confirm your account is connected** * If you've already connected your account, you can go straight to testing. Click **Continue** at the bottom of the Trigger configuration panel. * If you haven't connected your Blinq account yet, see [Connecting Zapier](/integrations/zapier/connecting-zapier). **4. Test your trigger** * After setup, Zapier prompts you to test your trigger. Click **Test Trigger** at the bottom of the Trigger configuration panel on the Test screen. * Select a contact record to test, or search to test a specific record. If you don't see a record, click the **Find new records** prompt. * Once selected, click **Continue with selected record** at the bottom of the panel. **5. Blinq is now configured within your Zap workflow** * At this point, you've connected and authenticated Blinq, selected your trigger, and passed testing. * Now, you can move on to configuring Actions in your Zap workflow. These actions are where you control what the workflow does once triggered by your Blinq trigger. * For an example and steps, see our [example configuration](/integrations/zapier/example-configuration). *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Create a Zap: example configuration Source: https://docs.blinq.me/integrations/zapier/example-configuration A worked example using the New Contact trigger to build a row in Zapier Tables. ## Create a Zap: example configuration Our previous page, [Creating a trigger](/integrations/zapier/creating-a-trigger), covered configuring Blinq triggers. If you haven't set one up yet, start there before you continue. Here's an example of configuring actions with the New Contact trigger. It walks you through generating output in a Zap workflow whenever a new Blinq contact is added. With your Blinq Trigger for New Contact configured, follow the steps below: **1. Create an action** * Click the **Action** event which is step 2 in your Zap workflow, directly after your trigger event. * For this example, we're going to configure output to Zapier's Tables, which is a native feature within Zapier, meaning no additional accounts or set up required. * Select **Tables** from the Products list, or search Tables in the top bar. **2. Select the action event** * Once Zapier Tables is selected as the Action App, select an Action event from the dropdown below. * For this example we're going to use **Create Record**. You can search the action list at the top. * Once your Action event is selected, click **Continue** at the bottom of the Action configuration panel. **3. Configure the action** * If you don't have any Zapier Tables created, you can click **Create Table** under the Table ID selector. * Configure the Text Field option that appears. You can type text in here, but more importantly you can select Blinq specific fields by using `/` or the Plus icon. * With the field mapping menu open and **Blinq → New Contact** as the trigger, you will see specific options to build the data output you want from a Blinq contact. **4. Build the data output** * To keep this example simple and understand the basics, let's construct a simple new row from the Blinq contact field mapping. The field mapping will show data from your test contact where available. * You can search the field mappings in the top bar of the pop-out menu. * Select First Name as the first field mapping attribute. * Select Last Name as the second field mapping attribute. * Select Business Name as the third field mapping attribute. * Select Primary Email as the fourth field mapping attribute. * This should give us a clear output of `{First Name}{Last Name}{Business Name}{Primary Email}`. * Now, let's add some manual formatting to shape the output into something more usable. We can add manual formatting by typing directly in the text field between the Blinq mappings. * For this example I've built the following, typing the spaces and the words `from` and `Contact:` by hand between the field mappings: `{First Name} {Last Name} from {Business Name}. Contact: {Primary Email}` **5. Test and publish the action** * Once you've finished step 4, press **Continue** at the bottom of the Action configuration panel. Zapier prompts you to test the action. * Once tested, you can review the results. * Finish and activate your Zap workflow by clicking **Publish**. Once you publish, your Zap is live and runs automatically whenever it's triggered. **6. See your output live** * For the Zapier Table we just configured, you can view your results in the table we created. * In your Zapier dashboard, go to **Assets → Tables**. * When you open the table you created, or the one used in the action, you'll see your Blinq contact data as a row, with the text field populated as you configured it. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Zapier output and field reference Source: https://docs.blinq.me/integrations/zapier/field-reference Every field Blinq sends to Zapier when a trigger fires and how it appears in the Zap editor. > [!NOTE] > > When a Blinq trigger fires, Blinq sends the full contact record to Zapier as a set of fields you can map into any action. This reference lists the fields Blinq sends and how they appear in the Zap editor. ## Enhanced field mappings (optional) > [!NOTE] > > Zapier's enhanced field mapping makes structured data easier to work with. [Learn more in Zapier's documentation →](https://help.zapier.com/hc/en-us/articles/46001908703757-Enhanced-field-mapping-makes-structured-data-easier-to-work-with) If you want granular control over how you map Blinq attributes in Zapier, turn on enhanced field mappings. It adds more options, where applicable, for things like: * Seeing the structure of each data field as a tree. * Mapping single items from lists, e.g. extracting a single tag instead of all tags. * Specific control of what is mapped. ## Core fields (quick reference) The most commonly used fields. See the complete reference below for every field Blinq sends. | Field (in Zapier) | Payload key | What it contains | | - | - | - | | First Name | `first_name` | Contact's first name | | Last Name | `last_name` | Contact's last name | | Business Name | `business_name` | Company or organization name | | Job Title | `job_title` | Contact's role or position | | Primary Email | `primary_email` | The first email on the contact record | | Primary Phone | `primary_phone` | The first phone number on the contact record | | Primary Business URL | `primary_business_url` | Main company website | | Contact Tags (text) | `blinq_contact_tags_text` | Contact's tags, comma-separated | | Notes (text) | `blinq_notes_text` | All notes on the contact, as plain text | | Blinq Contact ID | `contact_id` | Unique identifier for the contact in Blinq | ### Event details | Field (in Zapier) | Payload key | What it contains | | - | - | - | | Blinq Contact ID | `contact_id` | Unique identifier for the contact in Blinq | | Event Type | `event_type` | `contact.created` for New Contact, `contact.updated` for Updated Contact | | Event ID | `event_id` | Unique identifier for this trigger event | | Updated (ms) | `updated_ms` | When the contact was last updated, in milliseconds; sent on Updated Contact only | Blinq uses these identifiers so Zapier doesn't process the same event twice. ## Complete field reference ### Contact details | Field (in Zapier) | Payload key | What it contains | | - | - | - | | First Name | `first_name` | Contact's first name | | Middle Name | `middle_name` | Contact's middle name | | Last Name | `last_name` | Contact's last name | | Preferred Name | `preferred_name` | Name the contact prefers to go by | | Maiden Name | `maiden_name` | Contact's maiden name | | Honorific Prefix | `honorific_prefix` | Title before the name (e.g. Dr, Ms) | | Honorific Suffix | `honorific_suffix` | Title after the name (e.g. PhD) | | Pronouns | `pronouns` | Contact's pronouns | | Job Title | `job_title` | Contact's role or position | | Department | `department` | Department within the company | | Business Name | `business_name` | Company or organization name | | Profile Picture URL | `profile_picture_url` | Link to the contact's profile photo | | Company Logo URL | `company_logo_url` | Link to the company logo | ### Contact methods | Field (in Zapier) | Payload key | What it contains | | - | - | - | | Primary Email | `primary_email` | The first email on the contact record | | Primary Email Label | `primary_email_label` | Label for the primary email (e.g. Work) | | Secondary Email | `secondary_email` | The second email on the contact record | | Secondary Email Label | `secondary_email_label` | Label for the secondary email | | Primary Phone | `primary_phone` | The first phone number on the contact record | | Primary Phone Label | `primary_phone_label` | Label for the primary phone (e.g. Mobile) | | Secondary Phone | `secondary_phone` | The second phone number on the contact record | | Secondary Phone Label | `secondary_phone_label` | Label for the secondary phone | | Primary Address | `primary_address` | Main address | | Primary Address Label | `primary_address_label` | Label for the primary address | | Secondary Address | `secondary_address` | Second address | | Secondary Address Label | `secondary_address_label` | Label for the secondary address | ### Links and social profiles Blinq sends a field for each link on the contact's card. | Field (in Zapier) | Payload key | What it contains | | - | - | - | | Primary Business URL | `primary_business_url` | Main company website | | Secondary Business URL | `secondary_business_url` | Additional company website | | LinkedIn | `linkedin_url` | LinkedIn profile URL | | X (Twitter) | `twitter_url` | X / Twitter profile URL | | Instagram | `instagram_url` | Instagram profile URL | | Facebook | `facebook_url` | Facebook profile URL | | YouTube | `youtube_url` | YouTube channel URL | | TikTok | `tiktok_url` | TikTok profile URL | | Snapchat | `snapchat_url` | Snapchat profile URL | | WhatsApp | `whatsapp_url` | WhatsApp link | | Telegram | `telegram_url` | Telegram link | | Signal | `signal_url` | Signal link | | WeChat | `wechat_url` | WeChat link | | Skype | `skype_url` | Skype link | | Discord | `discord_url` | Discord link | | Twitch | `twitch_url` | Twitch channel URL | | GitHub | `github_url` | GitHub profile URL | | Calendly | `calendly_url` | Calendly scheduling link | | PayPal | `paypal_url` | PayPal link | | Venmo | `venmo_url` | Venmo link | | Cash App | `cashapp_url` | Cash App link | | Yelp | `yelp_url` | Yelp listing URL | | Promo | `promo_url` | Promotional link | Blinq sends any other link type on the card using the same pattern, `_url`. ### Tags, campaigns, and notes Blinq sends each of these both as a list and as a combined text value. | Field (in Zapier) | Payload key | What it contains | | - | - | - | | Contact Tags | `blinq_contact_tags` | Contact's tags, as a list | | Contact Tags (text) | `blinq_contact_tags_text` | Contact's tags, comma-separated | | Workspace Tags | `blinq_workspace_tags` | Workspace tags applied to the contact, as a list | | Workspace Tags (text) | `blinq_workspace_tags_text` | Workspace tags, comma-separated | | Campaigns | `blinq_campaigns` | Campaigns the contact is a lead on, as a list | | Campaigns (text) | `blinq_campaigns_text` | Campaigns, comma-separated | | Campaign Tags | `blinq_campaign_tags` | Tags from those campaigns, as a list | | Campaign Tags (text) | `blinq_campaign_tags_text` | Campaign tags, comma-separated | | Notes | `blinq_notes` | Manual notes, each with note text and date | | Notes (text) | `blinq_notes_text` | All manual notes, as plain text | | AI Notetaker Notes | `blinq_ai_notetaker_notes` | AI Notetaker notes, each with note text and date | | AI Notetaker Notes (text) | `blinq_ai_notetaker_notes_text` | All AI Notetaker notes, as plain text | ### Custom Lead Capture Form fields If your workspace uses a Lead Capture Form, Blinq also sends each form question as its own field, named after the question, so you can map it directly. Blinq provides a combined summary too. | Field (in Zapier) | Payload key | What it contains | | - | - | - | | Custom Fields (text) | `blinq_custom_fields_text` | All Lead Capture Form answers, one `Question: answer` per line | | (one per form question) | `blinq_custom_field_` | The answer to that form question | *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Zoho CRM integration overview Source: https://docs.blinq.me/integrations/zoho Connect your Blinq contacts directly to Zoho CRM so captured contacts flow into your CRM automatically. > [!NOTE] > > The Zoho CRM integration is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing) Our Zoho CRM integration connects your Blinq contacts directly to Zoho CRM. Contacts captured in Blinq flow into Zoho automatically, complete with notes, tags, and campaign attribution. Your team gets clean, contextual data where they already work, without manual exports. You can install and configure the Zoho CRM integration from your [Blinq dashboard](/integrations/zoho/connecting-zoho). > [!NOTE] > > **Already connected to Zoho through Merge?** New connections through Merge are no longer available. If your workspace is still on the Merge-based Zoho connection, you'll see an **Upgrade** button (with a warning icon) instead of **Connect** next to Zoho on your workspace's **Settings → Integrations** page. Click it to move to the native integration, or [contact support](mailto:support@blinq.me) if you have questions. ## Prerequisites * You must be an **Admin** or **Owner** in your Blinq workspace to set up and manage the Zoho CRM integration. * You'll need Zoho credentials with permission to authorize a connected app. Admin credentials are recommended. * You'll need to know which Zoho data centre hosts your account. * Blinq's Zoho CRM integration is available on **Business** and **Enterprise** plans. ## Feature overview | Feature | Supported | Configuration | | - | - | - | | Export contacts as Zoho Leads or Contacts | Yes | Chosen when you connect, changeable in integration settings | | Sync updates to contacts from Blinq to Zoho automatically | Yes | Toggle on/off | | Sync Blinq contact, workspace, and campaign tags | Yes | Toggle on/off | | Sync Blinq notes | Yes | Toggle on/off | | Auto export new Blinq contacts | Yes | Automatic, or hold for manual review | | Export contacts on demand | Yes | **Sync contacts** in your Zoho settings | | Campaign sync | Yes | Link a Blinq campaign to a Zoho campaign | | Custom field mapping | Yes | Map Zoho fields, including custom ones, in the Field Mapper | | Contact de-duplication | Yes | Matched on unique email address | Zoho can run alongside Salesforce, HubSpot, Dynamics, or any other connected integration. A captured contact exports to every platform you've connected. ## Documentation for our Zoho CRM integration > **[Connecting Zoho CRM](/integrations/zoho/connecting-zoho)** > > Choose your data centre, authorize Blinq, and connect Zoho from your dashboard. > **[Configuring Blinq](/integrations/zoho/configuring-blinq)** > > Control how Blinq syncs contacts, notes, and tags to Zoho, and how contacts are shared. > **[Configuring Zoho CRM](/integrations/zoho/configuring-zoho)** > > Add Blinq's custom fields to the Leads and Contacts views your team uses in Zoho. > **[Field reference](/integrations/zoho/field-reference)** > > Contact field mapping, custom fields, and deduplication behavior. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Blinq for Zoho CRM Source: https://docs.blinq.me/integrations/zoho/configuring-blinq Control how Blinq syncs contacts, tags, and notes to Zoho, choose Leads or Contacts, and sync on demand. ## Configuring Blinq Once connected, you can control how Blinq syncs data to Zoho. All options can be toggled on or off at any time from **Settings → Integrations → Zoho CRM**. ### Leads or Contacts **Export Blinq contacts as** decides which Zoho module receives your records: **Leads** or **Contacts**. You chose one when you connected Zoho, and can change it here at any time. Pick the one that matches how your team works. If people you meet at events are unqualified until someone follows up, Leads keeps them out of your contact database until they're worth having there. If your team treats every capture as a real relationship from the start, Contacts saves a conversion step. > [!NOTE] > > This applies to your whole workspace — every exported contact goes to the module you choose. Changing it later affects new exports, not records already in Zoho. ### Automatically update changes to Blinq contacts in Zoho When enabled, Blinq automatically updates Zoho whenever you change a contact's details. Your CRM stays current without manual re-entry. ### Sync contact tags and notes When enabled, Blinq syncs tags (contact, workspace, and campaign tags) and notes from a contact straight to Zoho. ## How new contacts sync | Setting | Behavior | | - | - | | Automatic | New contacts export to Zoho as they're captured. | | Manual review | New contacts are held in Blinq until someone approves them. | Manual review is worth using while you're getting started, or when your team captures contacts somewhere the quality varies — a busy trade show stand, for example. Nothing reaches Zoho until a person has looked at it. ## Exporting on demand Select **Sync contacts** in your Zoho settings to push your existing Blinq contacts across without waiting for new captures. Use it after you first connect, so the contacts you already have in Blinq reach Zoho. ## Sharing contacts to Zoho > [!NOTE] > > Blinq automatically shares contacts captured on a team card with your team. No manual sharing required. Export contacts to Zoho from **Blinq → Contacts → All company contacts**. Blinq doesn't export your personal contacts to Zoho unless you share them with your team. If you haven't shared a contact with your organization yet, you can share it from the **Share** menu on the individual contact record, in the dashboard or Blinq app. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Configuring Zoho CRM for Blinq Source: https://docs.blinq.me/integrations/zoho/configuring-zoho Add Blinq's custom fields to the Leads and Contacts views your team uses in Zoho. ## Add Blinq fields in Zoho When you connect Blinq, it automatically creates the following custom fields in your Zoho account. They won't appear in your list or detail views until you add them. * **Blinq Contact Tags:** contact-level tags applied in Blinq. * **Blinq Workspace Tags:** workspace-level tags. * **Blinq Campaign Tags:** campaign tags from linked Blinq campaigns. * **Blinq Campaigns:** names of linked Blinq campaigns. * **Blinq Card Link:** a direct link to the contact's Blinq card. > [!NOTE] > > For help adding fields to your layouts and views in Zoho, see Zoho's documentation: [Customizing layouts](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/layouts-fields/articles/customize-page-layout). To add a Blinq field to a Leads or Contacts view: **1. Open Setup** In Zoho CRM, click the gear icon and select **Setup**. **2. Open the module you sync to** Under **Customization → Modules and Fields**, select **Leads** or **Contacts**, matching what you chose when you connected Blinq. **3. Open the layout** Select the layout your team uses, then open the layout editor. **4. Add the Blinq fields** Drag each Blinq field from the field palette onto the layout where you'd like it to appear, then save. To show a Blinq field as a column in a list view, open the view, select the column settings icon, and add the field from there. ## Field mapping Zoho fields — including any custom fields specific to your account — are available in Blinq's [field mapper](/features/field-mapping), so you can map any Blinq contact or custom form field to the Zoho field of your choice. ## Notes Blinq syncs contact notes to the associated Zoho Lead or Contact record. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Connecting Zoho CRM to Blinq Source: https://docs.blinq.me/integrations/zoho/connecting-zoho Choose your Zoho data centre, authorize Blinq, and choose Leads or Contacts. Zoho connects through a sign-in and authorize flow, so there are no API keys to copy. The one thing to get right is your data centre. ## Check your Zoho data centre Zoho hosts accounts in several data centres, and each has its own domain. The one you pick during setup has to match the one your account lives in — if it doesn't, the connection won't find your account. The quickest way to check is to look at the domain you use to sign in to Zoho. | Sign-in domain | Data centre | | - | - | | `zoho.com` | United States | | `zoho.com.au` | Australia | | `zoho.eu` | Europe | | `zoho.in` | India | | `zoho.jp` | Japan | | `zohocloud.ca` | Canada | | `zoho.sa` | Saudi Arabia | | `zoho.com.cn` | China | > [!NOTE] > > Zoho hosts accounts in other regions too. If yours isn't listed here, pick the entry that matches your sign-in domain, or contact [support@blinq.me](mailto:support@blinq.me). ## Connect Zoho in Blinq **1. Open your integrations** In the Blinq [dashboard](https://dash.blinq.me), go to **Settings**, then the **Integrations** tab. **2. Start the connection** Under **Export contacts**, find **Zoho CRM** and select **Connect**. **3. Choose which credentials to use** Select **Use my admin credentials** or **Use my non-admin credentials**. Admin credentials are recommended, and avoid permission problems later. **4. Review the access Blinq needs** Read what the integration will do, then select **Next**. **5. Select your account data centre** Choose the data centre matching your Zoho account, then select **Open window**. **6. Sign in and authorize** Sign in to Zoho in the window that opens, and approve the access Blinq requests. **7. Choose Leads or Contacts** Pick the Zoho module new contacts should sync into. You can change this later in your integration settings. **8. Map your fields** Review the default field mapping in the Field Mapper tab, or add your own. See [Blinq field mapping](/features/field-mapping) for how this works. **9. Wait for setup to finish** Blinq sets up the connection, which can take a few minutes. When you see **You're connected**, select **Finish**. > [!TIP] > > **Zoho CRM is connected.** It now shows a **Settings** button in your integrations list. Next, [control how contacts sync and export on demand](/integrations/zoho/configuring-blinq). > [!WARNING] > > The connection is authorized by the Zoho user who signs in. If that person leaves or loses access in Zoho, exports stop and an admin needs to reconnect. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me). # Blinq Zoho CRM field reference Source: https://docs.blinq.me/integrations/zoho/field-reference Contact field mapping, custom fields, and deduplication behavior for the Blinq Zoho CRM integration. > [!NOTE] > > Blinq syncs contact data to fields on the Zoho Lead or Contact record, depending on your export type setting. Blinq creates these custom fields automatically when you connect the integration. ## Contact field mapping If the following information is present on the Blinq contact, Blinq syncs it to the corresponding Zoho field. | Blinq contact field | Zoho field | | - | - | | First name | First Name | | Last name | Last Name | | Company | Company (Lead) / Account Name (Contact) | | Job title | Title | | Email (first/primary) | Email | | Phone number | Phone / Mobile | | Website | Website | | Address | Address | | Blinq Card URL | Blinq Card Link (custom field) | | Contact tags | Blinq Contact Tags (custom field) | | Workspace tags | Blinq Workspace Tags (custom field) | | Campaign tags | Blinq Campaign Tags (custom field) | | Campaigns | Blinq Campaigns (custom field) | | Notes | Notes (on the associated Zoho Lead or Contact record) | To customize which fields Blinq syncs and how they map, see [Blinq field mapping](/features/field-mapping). ## Custom fields created by Blinq Blinq creates the following custom fields in Zoho when you connect the integration. | Field name | Description | | - | - | | Blinq Card Link | A direct link to the contact's Blinq card | | Blinq Contact Tags | Contact-level tags applied in Blinq | | Blinq Workspace Tags | Workspace-level tags | | Blinq Campaign Tags | Campaign tags from linked Blinq campaigns | | Blinq Campaigns | Names of linked Blinq campaigns | ## Deduplication When you export a Blinq contact to Zoho, Blinq looks for an existing record with the same email address. If Blinq finds a record it already manages, it updates that record. If a matching record is already managed by another source, Blinq leaves it unchanged rather than overwriting it. Your CRM has the final say on every export. Duplicate and matching rules, required fields, and validation rules set up in your CRM can change how a record is matched, allow a duplicate to be created, or block an export entirely. *** ### Need help? For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me).