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

# Blinq Zapier output and field reference

> Every field Blinq sends to Zapier when a trigger fires and how it appears in the Zap editor.

<Info>
  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.
</Info>

## Enhanced field mappings (optional)

<Info>
  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)
</Info>

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, `<type>_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_<question>` | The answer to that form question                               |

<hr />

### Need help?

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