Zapier Connector Documentation Zapier Connector


Zapier to Hull Mapping

Zapier Object Captured in Hull as Description
Zap Action
Action
User

Create or update a Hull User from a Zap

Zap Action
Action
Account

Create or update a Hull Account from a Zap

Zap Action
Action
User Event

Create a User Event in Hull from a Zap

Retrieve User
Step
User

Retrieve a Hull user from its identifiers and pass to the next action

Retrieve Account
Step
Account

Retrieve a Hull account from its identifiers and pass to the next action


Hull to Zapier Mapping

Hull Object Sent to Zapier as Description
User trigger
New User Trigger

Trigger a Zap when a User is created in Hull

User trigger
User Updated Trigger

Trigger a Zap when a User is updated in Hull

Account trigger
New Account Trigger

Trigger a Zap when an Account is created in Hull

Event trigger
New User Event

Trigger a Zap when a new Event is created in Hull

User trigger
User Attribute Updated

Trigger a Zap when a User attribute was updated

Account trigger
Account Attribute Updated

Trigger a Zap when an Account attribute was updated

User trigger
User Entered Segment

Trigger a Zap when a User enters a segment

User trigger
User Left Segment

Trigger a Zap when a User leaves a segment

Account trigger
Account Entered Segment

Trigger a Zap when an Account enters a segment

Account trigger
Account Left Segment

Trigger a Zap when an Account leaves a segment


Hull Zapier Connector

The Zapier Connector enables more automated workflows that leverage Hull’s central source of information to seamlessly communicate with other applications and data sources.

Getting Started

In Hull, install the Zapier Connector and copy the generated authentication token. In Zapier, install the Zapier app ‘Hull’. After creating a Hull zap and choosing a trigger, paste the authentication token when prompted.

Zap Triggers

There are 9 triggers that can be configured:

  1. User Enters Segment

- User enters one or more of the whitelisted user segments

  1. User Leaves Segment

- User leaves one or more of the whitelisted user segments

  1. User Attribute Updated

- User is in one or more of the whitelisted user segments

- Account on the user is in one or more of the whitelisted account segments

- A whitelisted user attribute was updated or a whitelisted account (on the user) attribute was updated. If both user attributes and account attributes are defined, the trigger will only be activated if both changes are made in the same message.

  1. User Event Created

- User is in one or more of the whitelisted user segments

- Account on the user is in one or more of the whitelisted account segments

- Event name matches an event on the user

  1. Account Enters Segment

- Account enters one or more of the whitelisted account segments

  1. Account Leaves Segment

- Account leaves one or more of the whitelisted account segments

  1. Account Attribute Update

- Account is in one or more of the whitelisted account segments

- A whitelisted account attribute was updated

  1. User is created

- A newly created user is in one or more of the whitelisted user segments

  1. Account is created

- A newly created account is in one or more of the whitelisted account segments

For all segment fields, we provide the option to select ‘all_segments’. When selected, the entity can be in any or no segments at all. For entity segment changes, the entity can enter or leave any segment, but must have at least one segment change.

If a payload matches any of the configured triggers, the full object will be sent to the Zap(s)


{
  "changes": {
    "is_new": false,
    "account": {},
    "user": {
      "clearbit/employment_role": ["", "ceo"]
    },
    "account_segments": {},
    "segments": {
      "left": [
        {
          "id": "user_segment_3",
          "name": "UserSegment3"
        }
      ],
      "entered": [
        {
          "id": "user_segment_1",
          "name": "UserSegment1"
        }
      ]
    }
  },
  "user": {
     "email": "foo@bar.com",
    ...
    "clearbit/employment_role": "ceo"
  },
  "account": {
    "domain": "bar.com",
    "clearbit/name": "The Bar Company"
  },
  "event": {
    "event": "Viewed a page"
  },
  "segments": [
    {
      "id": "user_segment_1",
      "name": "UserSegment1"
    }
  ],
  "account_segments": [...]
}

Zap Actions

There are 4 Actions that can be taken:

  1. Create/Update User
  • Provide the external id and/or the email
  1. Create/Update Account
  • Provide the external id and/or the domain
  1. Search User
  • Provide the external id and/or the email
  1. Search Account
  • Provide the external id and/or the domain

To install:

  • In Hull, click the “Connect to Zapier” button on the Dashboard page,
  • In Zapier, authorize with the access token from the Connector Settings page.

Get a customized demo

Book a personalized demo with a product expert to see how Hull can help you unify data across your entire stack.


or