> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slant.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Zapier
> Connect Slant to thousands of apps with Zapier to automate your workflows.
Zapier lets you connect Slant to thousands of other apps so you can automate repetitive work. When something happens in Slant — like a new client being created — Zapier can automatically take action in another app, and vice versa.
With the Slant Zapier integration, you can:
* **React to changes in Slant** — Trigger automations when [clients](/records/clients/overview), [prospects](/records/prospects), [other contacts](/records/other-contacts), or [people](/records/people) are created or updated, or when a tag is added.
* **Create and update records from other apps** — Add new clients, prospects, other contacts, [people](/records/people), notes, [tasks](/activity/tasks/overview), and [opportunities](/activity/opportunities/overview) in Slant when something happens in another app.
* **Look up existing records** — Search for clients and prospects by name, email, or phone number to use their data in subsequent Zap steps.
* **Manage contact details** — Add or update email addresses, phone numbers, addresses, and employment records on [people](/records/people) in Slant.
* **Manage tags** — Add or remove tags from clients, prospects, and other contacts.
## Connect to Zapier
Go to **Settings** → **API connections**, then select the **Zapier** tab.
Click **Connect to Zapier**. You'll be redirected to Zapier to accept a shared app invite. Sign in to your Zapier account (or create one) and accept the invite.
When you create your first Zap with Slant, Zapier asks you to authorize access to your Slant account. Sign in and grant permission.
Once authorized, Slant appears as an available app when building Zaps.
## Triggers
Triggers fire when something happens in Slant, starting your Zap automatically.
### Record created
| Trigger | Fires when |
| -------------------- | --------------------------------------------------------- |
| **Client created** | A new [client](/records/clients/overview) is created |
| **Prospect created** | A new [prospect](/records/prospects) is created |
| **Contact created** | A new [other contact](/records/other-contacts) is created |
Created triggers include the record's ID, name, status, assigned user, and the head of household's (or contact's) name, email, and phone number.
### Record updated
| Trigger | Fires when |
| -------------------- | ------------------------------------------------------------- |
| **Client updated** | A [client](/records/clients/overview) record is changed |
| **Prospect updated** | A [prospect](/records/prospects) record is changed |
| **Contact updated** | An [other contact](/records/other-contacts) record is changed |
| **Person updated** | Any [person](/records/people) record is changed |
Updated triggers include the full record data plus a list of which fields changed, so you can build Zaps that only act on specific changes.
Update triggers are slightly delayed (about 60 seconds) to batch rapid consecutive edits into a single event.
### Tag added
| Trigger | Fires when |
| ------------- | -------------------------------------- |
| **Tag added** | A tag is added to a client or prospect |
Includes the household's name, email, phone number, type (client or prospect), and the tag name.
## Actions
Actions let Zapier create or modify records in Slant.
### Create records
| Action | What it creates |
| --------------------------- | -------------------------------------------------------------------------- |
| **Create client** | A new [client](/records/clients/overview) with a head of household |
| **Create prospect** | A new [prospect](/records/prospects) with a head of household |
| **Create contact** | A new [other contact](/records/other-contacts) |
| **Add person to household** | A new [person](/records/people) on an existing client or prospect |
| **Create note** | A note on a client or prospect |
| **Create task** | A [task](/activity/tasks/overview) in a book |
| **Create opportunity** | An [opportunity](/activity/opportunities/overview) on a client or prospect |
#### Client and prospect fields
When creating a client or prospect, you can set:
* **Household details** — Household name, tags
* **Head of household** — First name (required), middle name, last name, preferred name, email, phone, salutation, suffix, gender, designations, date of birth, job title
* **Address** — Street address, apartment/suite, city, state (two-letter code), ZIP, country code, address type (home, work, mailing, or other)
* **Employment** — Business name, role, start date, end date, actively employed
* **Custom fields** — Any custom fields configured for your book
Clients also support **tier**, **became client at** date, **SSN**, and **driver's license number**.
At least one of email or phone is required when creating a client, prospect, or other contact.
#### Add person to household fields
When adding a [person](/records/people) to an existing client or prospect, you can set first name (required), middle name, last name, preferred name, email, phone, salutation, suffix, gender, designations, date of birth, job title, SSN, driver's license number, household role (head of household, spouse, partner, dependent child, other adult, other dependent, deceased, or unknown), an address, employment, and custom fields.
#### Other contact fields
When creating an other contact, you can set first name (required), last name, preferred name, email, phone, salutation, suffix, gender, designations, tags, and an address.
#### Note fields
* **Client or prospect ID** (required) — The record to attach the note to
* **Content** (required) — Markdown or plain text
#### Task fields
* **Title** (required)
* **Description**, **deadline**, **all day**, **status** (to-do or done), **priority** (low, medium, high, or urgent)
* **Client or prospect ID** or **contact ID** — Associate the task with a record
* **Assigned to user** or **assigned to team** — Assign the task (you can set one but not both)
#### Opportunity fields
* **Client or prospect ID** (required)
* **Opportunity name** (required)
* **Value**, **probability** (0–100), **target close date**
### Update records
| Action | What it updates |
| ---------------------- | ------------------------------------------------------------------------------------------------ |
| **Update client** | Household name, tier, became client at, and custom fields |
| **Update prospect** | Household name and custom fields |
| **Update person** | Name, contact details, role, date of birth, job title, SSN, driver's license, and custom fields |
| **Update opportunity** | Name, value, probability, target close date, household, pipeline stage, owner, and custom fields |
Update actions only change the fields you provide — empty inputs are ignored so they can't overwrite existing values.
Moving an opportunity between pipelines isn't supported. The pipeline stage dropdown is scoped to the opportunity's current pipeline.
### Manage contact details on a person
| Action | What it adds |
| ---------------------------- | ------------------------------------------------------------------------------- |
| **Add email to person** | Email address with type (personal, business, school, or other) and primary flag |
| **Add phone to person** | Phone number with type (mobile, work, home, fax, or other) and primary flag |
| **Add address to person** | Address with street, city, state, ZIP, country, type, and primary flag |
| **Add employment to person** | Employment record with business name, role, dates, and active status |
| Action | What it updates |
| ------------------------------- | ------------------------------------------------------------------------------------------- |
| **Update email on person** | Any field on an existing email — address, type, or primary flag |
| **Update phone on person** | Any field on an existing phone — number, type, or primary flag |
| **Update address on person** | Any field on an existing address — street, city, state, ZIP, country, type, or primary flag |
| **Update employment on person** | Any field on an existing employment — business name, role, dates, or active status |
Update actions require the person ID and the specific record ID. Only the fields you provide are changed.
### Manage tags
| Action | What it does |
| --------------- | ------------------------------------------------------------------ |
| **Add tags** | Adds one or more tags to a client, prospect, or other contact |
| **Remove tags** | Removes one or more tags from a client, prospect, or other contact |
Both actions require you to select the record type (client, prospect, or other contact) and the specific record.
## Searches
Searches let you look up existing Slant records to use in subsequent Zap steps.
| Search | How it finds records |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Find client by email or phone** | Matches a [client](/records/clients/overview) by email address or phone number (at least one required) |
| **Find prospect by email or phone** | Matches a [prospect](/records/prospects) by email address or phone number (at least one required) |
| **Find client by name** | Matches a [client](/records/clients/overview) by first name, last name, or full name |
| **Find prospect by name** | Matches a [prospect](/records/prospects) by first name, last name, or full name |
All searches require you to select a book. Results include the record's ID, name, and book — client searches also return the tier and became client at date.
Use a search step before an update action to find the record ID you need. For example, search for a client by email, then use the returned ID to update their tier.
## FAQ
Yes. When creating or updating clients, prospects, or people, any custom fields configured in your book appear as additional fields in the Zapier action. Custom fields are not available for other contacts.
Slant automatically prevents duplicate records from repeated Zapier requests. Each action includes an idempotency key, so retries create or update the same record rather than creating duplicates.
Created triggers (client created, prospect created, contact created, tag added) fire immediately. Updated triggers (client updated, prospect updated, contact updated, person updated) are batched with a 60-second delay to consolidate rapid edits.
Not currently. Searches are available for clients and prospects only. You can search by name, email, or phone number.
## Next steps
Build automations directly in Slant without Zapier
Connect email, calendar, phone, and file storage