# Integrate with Asana
Source: https://docs.inflection.io/agents/asana

Tag an Asana task and the Inflection agent reads the brief, builds an Inflection email, and posts the result back to the task.

The Inflection agent in **Asana** meets content ops where briefs already live. **Tag a task** and the agent reads the brief, builds an Inflection email, and posts the result back to the task — no copy-pasting between your project tracker and the platform. It's a focused, workflow-triggered surface centered on email creation.

## Why use Asana

**Briefs become assets automatically.** The task you were going to write up anyway becomes a drafted email.

**Content ops stays in one place.** Writers and PMs work in Asana; the email shows up on the task.

**Trigger-based, hands-off.** No new tool to learn — a tag, assignment, or section change kicks off the build.

<video />

## What you can do here

### Build an email from a tagged task

The agent reads the task's brief and generates an Inflection email asset, posting a link/preview back as a task comment for review.

**Why it matters:** the brief-to-email handoff that used to be manual now happens the moment a task is ready.

<Info>
  **How it runs**

  * Write the email brief in the Asana task description.
  * Trigger the agent: assign the task, add a tag (e.g. "AI: build email"), or move the task to a new section.
  * The agent replies on the task with the generated email.
</Info>

### Build from a design (tenant skill)

Where enabled, a companion skill builds an Inflection email from a **Figma** design (`inflection-email-from-figma`) — useful when design hands off comps rather than copy.

<Info>
  **Availability:** the Asana → email flow is delivered as a connected-agent / skill and may be enabled per tenant — check with your CS team.
</Info>

## Step 1 — Create a Personal Access Token in Asana

<Warning>
  Please note that the actions done by Inflection Agent in Asana (comment in the ticket) will reflect as coming from the user account that made the PAT. It is advisable to create a new user in Asana (like "Inflection Bot") and use that account to create the PAT. This way all actions on tickets will be made by "Inflection Bot".
</Warning>

<iframe title="Loom video player" />

[Watch the Personal Access Token walkthrough on Loom](https://www.loom.com/share/4c1441067b2043a39ee0a135f416f703)

1. Navigate to [https://app.asana.com/0/my-apps](https://app.asana.com/0/my-apps)
2. Create a new Personal Access Token
3. Give it a relevant name
4. Copy the token — keep it safe, you won't be able to see it again

## Step 2 — Connect Asana in Inflection

<iframe title="Loom video player" />

[Watch the connection walkthrough on Loom](https://www.loom.com/share/3263c280b40940dd88a5ec86af50fd10)

1. Go to the Connections tab: [https://app.inflection.io/connections](https://app.inflection.io/connections)

2. Click **+ Add new connection**

3. Select **Asana** → enter a name for the connection → paste the PAT you copied from Asana

4. In the AI Agent triggers, add your Asana project ID where the Campaign Ops Agent will work on tasks

   <Tip>
     Your project ID is the string of numbers in your project's URL — it looks like `https://app.asana.com/0/projectID/list`
   </Tip>

5. Set the trigger condition — choose when you want the agent to pick up tasks:
   1. When the task is assigned to someone
   2. When a tag is added
   3. When a section is changed

You're good to go! Whenever a trigger condition is met, the agent picks up the task, builds emails, and comments back on the Asana ticket.

## Use cases & inspiration

**Editorial calendar → emails.** Each content task, once briefed and tagged (or assigned), comes back with a drafted email ready for review.

**Design-led campaigns.** Hand off a Figma comp and get a matching Inflection email to refine.

## Good to know (limitations)

**Email-focused.** The Asana surface centers on building emails from a brief — audiences, segments, and journeys live in the in-app chat / MCP.

**Tenant-scoped today.** Delivered as a connected agent / skill; availability and exact trigger behavior vary by tenant.

**Drafts for review.** The generated email is a starting point you refine and approve before sending.

## Prompting best practices

**Write the brief like you mean it.** Audience, goal, key message, and CTA in the task description produce a better first draft.

**One task, one email.** Keep each task scoped to a single email for a clean result.

## Report unexpected outcomes

Share issues in your Inflection Slack channel with the task link, your goal, and screenshots of the brief and the generated output.

## Share your use cases

Tell us how Asana fits your content workflow — what triggers and outputs would help most.


# Inflection Connected Apps using oAuth 2.1
Source: https://docs.inflection.io/agents/connected-apps-oauth

Connect to Inflection's MCP server.

This guide explains how to set up OAuth 2.1 authentication for general-purpose MCP access to the Inflection platform.

## About This Guide

### Scope of This Documentation

This guide covers **general-purpose OAuth 2.1 authentication** for:

* Custom integrations and applications
* Third-party automation tools (n8n, Zapier, Make, etc.)
* API testing tools (Postman, Insomnia, etc.)
* Custom scripts and internal tooling
* Calling the [Inflection Developer API](/api-reference/introduction)

### MCP Authentication (Claude, ChatGPT, etc.)

If you're looking to connect Inflection with **AI assistants via MCP (Model Context Protocol)**, such as:

* Claude (Anthropic)
* ChatGPT (OpenAI)

Please refer to the specific **MCP Integration Guide** for ChatGPT and Claude

## Overview

Inflection uses **OAuth 2.1 with PKCE** (Proof Key for Code Exchange) for secure API authentication. This modern authentication standard provides enhanced security for both web and native applications.

### Key Features

| Feature | Description |
| - | - |
| OAuth 2.1 | Latest OAuth standard with security best practices |
| PKCE Required | Protects against authorization code interception attacks |
| Refresh Tokens | Automatically renew access without re-authentication |
| Secure Access | Token-based authentication for all API calls |

### When to Use This Authentication Method

| Use Case | Authentication Method |
| - | - |
| Custom app integrations | ✅ OAuth 2.1 (this guide) |
| Automation platforms (n8n, Zapier) | ✅ OAuth 2.1 (this guide) |
| API testing (Postman) | ✅ OAuth 2.1 (this guide) |
| Internal scripts and tools | ✅ OAuth 2.1 (this guide) |
| Inflection Developer API calls | ✅ OAuth 2.1 (this guide) — or a [PAT](/api-reference/authentication) |
| Claude AI assistant | ❌ Use MCP with DCR |
| ChatGPT integration | ❌ Use MCP with DCR |
| Other MCP DCR compatible AI | ❌ Use MCP with DCR |

## Prerequisites

Before you begin, ensure you have:

* Access to the Inflection Settings panel
* A redirect URL for your application (can be localhost for testing)

<AccordionGroup>
  <Accordion title="Step 1: Create a Connected App">
    1. Log in to your Inflection account
    2. Navigate to **Settings** → **Connected Apps**
    3. Click **Create App Credentials**
    4. Fill in the required fields:

    | Field | Description | Example |
    | - | - | - |
    | App Name | A descriptive name for your application | "My Integration App" |
    | Redirect URL(s) | The URL where users will be redirected after authentication | `https://your-app.com/callback` or `http://localhost:3000/callback` |
    | Description | Optional description of your app's purpose | "Integration for marketing automation" |

    5. Click **Connect** to create the app

    #### Important: Save Your Credentials

    After creating the app, you will receive:

    * **Client ID** - A public identifier for your app
    * **Client Secret** - A confidential key (keep this secure!)

    <Warning>
      **Store these credentials securely. The Client Secret will not be shown again.**
    </Warning>
  </Accordion>

  <Accordion title="Step 2: OAuth 2.1 Endpoints">
    Use these endpoints for authentication (you can also discover these via the [well-known endpoint](https://auth-v2.inflection.io/.well-known/oauth-authorization-server)):

    | Endpoint | URL |
    | - | - |
    | Authorization | `https://auth-v2.inflection.io/oauth2/authorize` |
    | Token | `https://auth-v2.inflection.io/oauth2/token` |
  </Accordion>

  <Accordion title="Step 3: Authorization Code Flow with PKCE">
    OAuth 2.1 requires PKCE for enhanced security. Here's how the flow works:

    #### 3.1 Generate PKCE Parameters

    Before starting the flow, generate these values:

    1. **Code Verifier**: A cryptographically random string (43-128 characters)
    2. **Code Challenge**: Base64-URL encoded SHA256 hash of the code verifier

    Example (JavaScript):

    ```javascript theme={null}
    // Generate code verifier
    function generateCodeVerifier() {
      const array = new Uint8Array(32);
      crypto.getRandomValues(array);
      return btoa(String.fromCharCode(...array))
        .replace(/\+/g, '-')
        .replace(/\//g, '_')
        .replace(/=/g, '');
    }

    // Generate code challenge
    async function generateCodeChallenge(verifier) {
      const encoder = new TextEncoder();
      const data = encoder.encode(verifier);
      const digest = await crypto.subtle.digest('SHA-256', data);
      return btoa(String.fromCharCode(...new Uint8Array(digest)))
        .replace(/\+/g, '-')
        .replace(/\//g, '_')
        .replace(/=/g, '');
    }
    ```

    #### 3.2 Request Authorization

    Direct the user to the authorization URL:

    ```
    https://auth-v2.inflection.io/oauth2/authorize
      ?response_type=code
      &client_id=YOUR_CLIENT_ID
      &redirect_uri=YOUR_REDIRECT_URI
      &code_challenge=YOUR_CODE_CHALLENGE
      &code_challenge_method=S256
      &scope=inflection_app
    ```

    | Parameter | Required | Description |
    | - | - | - |
    | response\_type | Yes | Must be `code` |
    | client\_id | Yes | Your app's Client ID |
    | redirect\_uri | Yes | Must match the registered redirect URL |
    | code\_challenge | Yes | The PKCE code challenge |
    | code\_challenge\_method | Yes | Must be `S256` |
    | scope | Yes | Must be `inflection_app` |

    #### 3.3 Handle the Callback

    After the user authorizes your app, they will be redirected to your redirect URL with an authorization code:

    ```
    YOUR_REDIRECT_URI?code=AUTHORIZATION_CODE
    ```

    #### 3.4 Exchange Code for Tokens

    Make a POST request to exchange the authorization code for tokens:

    ```bash theme={null}
    curl -X POST https://auth-v2.inflection.io/oauth2/token \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=authorization_code" \
      -d "client_id=YOUR_CLIENT_ID" \
      -d "client_secret=YOUR_CLIENT_SECRET" \
      -d "redirect_uri=YOUR_REDIRECT_URI" \
      -d "code=AUTHORIZATION_CODE" \
      -d "code_verifier=YOUR_CODE_VERIFIER"
    ```

    #### 3.5 Token Response

    A successful response returns:

    ```json theme={null}
    {
      "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOi...",
      "refresh_token": "dGhpcyBpcyBhIHJlZnJlc2ggdG9rZW4...",
      "token_type": "Bearer",
      "expires_in": 3600
    }
    ```

    | Field | Description |
    | - | - |
    | access\_token | Use this to authenticate API requests |
    | refresh\_token | Use this to get new access tokens |
    | token\_type | Always "Bearer" |
    | expires\_in | Token lifetime in seconds |
  </Accordion>

  <Accordion title="Step 4: Using the Access Token">
    Include the access token in the Authorization header for all API requests:

    ```bash theme={null}
    curl -X POST https://campaign.inflection.io/api/v1/campaigns/campaign.list \
      -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
      -H "Content-Type: application/json" \
      -d '{"page_size": 30, "page_number": 1}'
    ```

    The same token works on the [Developer API](/api-reference/introduction), and it acts as the user who authorized the app (see [Authentication](/api-reference/authentication)):

    ```bash theme={null}
    curl https://api.inflection.io/v2/contacts/by-email/jane%40acme.com \
      -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
    ```
  </Accordion>

  <Accordion title="Step 5: Refreshing Tokens">
    When your access token expires, use the refresh token to get a new one:

    ```bash theme={null}
    curl -X POST https://auth-v2.inflection.io/oauth2/token \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=refresh_token" \
      -d "client_id=YOUR_CLIENT_ID" \
      -d "client_secret=YOUR_CLIENT_SECRET" \
      -d "refresh_token=YOUR_REFRESH_TOKEN"
    ```
  </Accordion>

  <Accordion title="Integration Examples">
    <AccordionGroup>
      <Accordion title="Postman Setup">
        1. Create a new request in Postman
        2. Go to the **Authorization** tab
        3. Select **OAuth 2.0** as the type
        4. Configure with these settings:

        | Setting | Value |
        | - | - |
        | Grant Type | Authorization Code (With PKCE) |
        | Callback URL | `https://oauth.pstmn.io/v1/browser-callback` |
        | Auth URL | `https://auth-v2.inflection.io/oauth2/authorize` |
        | Access Token URL | `https://auth-v2.inflection.io/oauth2/token` |
        | Client ID | Your Client ID |
        | Client Secret | Your Client Secret |
        | Code Challenge Method | SHA256 |

        5. Click **Get New Access Token**
        6. Complete the login in your browser
        7. Use the token to make API requests

        **Note:** Ensure the Callback URL (`https://oauth.pstmn.io/v1/browser-callback`) is added as a Redirect URL in your Connected App settings.
      </Accordion>

      <Accordion title="n8n Setup">
        **Prerequisite:** Make sure you have created an app in inflection for n8n (shared above)

        <img alt="n8n HTTP request node configuration" />

        1. Use the MCP Client (If you want to use the MCP) or create and HTTP Request (If you want to use an API)

        2. Set **Authentication** to **MCP OAUTH2** or **Generic Credential Type  (OAuth2)**

           <img alt="Selecting the OAuth2 authentication credential type in n8n" />

        3. Configure a new OAuth2 credential:

        | Setting | Value |
        | - | - |
        | Grant Type | PKCE |
        | Authorization URL | `https://auth-v2.inflection.io/oauth2/authorize` |
        | Access Token URL | `https://auth-v2.inflection.io/oauth2/token` |
        | Client ID | Your Client ID |
        | Client Secret | Your Client Secret |
        | Scope | `inflection_app` |

        <img alt="n8n OAuth2 credential configuration fields" />

        4. Click **Connect** to authorize

           <img alt="Connect button to authorize the n8n OAuth2 credential" />

        5. n8n will automatically handle token refresh
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Security Best Practices">
    1. **Never expose your Client Secret** in client-side code or public repositories
    2. **Use HTTPS** for all redirect URLs in production
    3. **Store tokens securely** - use encrypted storage or secure vaults
    4. **Implement token refresh** before expiration to ensure uninterrupted access
    5. **Use short-lived access tokens** and rely on refresh tokens for extended sessions
    6. **Validate redirect URIs** match exactly what's registered in your app
  </Accordion>
</AccordionGroup>

### Tips

* Authorization codes are valid for 5 minutes and are single-use, exchange them promptly, as reusing a code invalidates the entire session
* If using Postman, ensure the callback URL in your Connected App matches Postman's callback URL
* For local development, `http://localhost` redirect URLs are acceptable


# In-App Chat
Source: https://docs.inflection.io/agents/in-app-chat

Use Inflection's in-app agent to ideate journeys, build segments, and more.

The Inflection in-app chat lets you build marketing assets by describing what you want in plain language. Describe an audience, email, or journey — the agent plans the work, builds it, and shows you the result inline, ready to review.

## Getting Started

Open **AI chat** inside Inflection. There is nothing to install. On your first message, the agent loads your business context (industry, ICP, common segments) so what it builds fits your account. The same agents are also available over the MCP connector for users working from Claude or ChatGPT.

<Info>
  **Try this in your first 10 minutes:** Type *"How many contacts opened an email in the last 30 days?"* to see the agent ground in your data, then *"Draft a re-engagement email for the ones who didn't."* You'll have a previewable email and a sense of the flow within minutes.
</Info>

## What You Can Do Here

### Overview

| Function | Ideate | Create | Edit | Outcome |
| - | - | - | - | - |
| **Audiences** | ✅ | ✅ | ✅ | A saved, auto-refreshing dynamic list — reusable across journeys |
| **Segments** | ✅ | ✅ | via UI | A mutually-exclusive category for lifecycle/tier messaging |
| **Email** | ✅ | ✅ | ✅ | An on-brand, previewable email saved to your library |
| **Tokens** | ✅ | ✅ | ✅ | Verified personalization — including computed scores |
| **Journeys** | ✅ | ✅ | ✅ | A multi-step draft, ready for your review and activation |
| **Analytics** | ✅ | — | — | Dashboard-accurate performance, rendered inline |

### Build Audiences

Describe who you want to reach. The agent grounds in your real field values and saves a reusable dynamic list.

Consistent, reusable targeting without learning the filter UI.

<Info>
  **Example prompts:**

  * "Build a list of enterprise accounts in California who haven't logged in for 30 days."
  * "How big is that audience?" · "Save it as 'Enterprise – dormant'."
</Info>

### Create and Edit Email

Draft from a brief, restyle elements in plain language, or edit a saved template **by name** — then preview before anything sends.

Review a thumbnail preview before you ship.

<Info>
  **Example prompts:**

  * "Create a welcome email with a 20% offer and one clear CTA."
  * "Edit the 'Trial Welcome' email — make the CTA green and tighten the hero copy."
</Info>

### Build Segments and Tokens

Create ordered, mutually-exclusive segment categories (lifecycle, tier, engagement) and verified personalization tokens — including arithmetic scores such as a weighted engagement metric.

<Info>
  **Example prompts:**

  * "Create lifecycle segments: New, Active, At Risk, Churned."
  * "Build a score = 3×demo\_requests + 1×email\_opens over 90 days."
</Info>

### Build Journeys

Describe a multi-step flow — emails, delays, branches, Salesforce sync, webhooks — and the agent assembles a **draft** you review and activate in the app.

<Info>
  **Example prompt:**

  * "Draft a 3-step onboarding journey: welcome email, 2-day delay, branch on opened."
</Info>

### Ask About Performance

Pull campaign and journey results in the same chat — dashboard-accurate numbers, rendered as a clean artifact.

<Info>
  **Example prompt:**

  * "How did the Q1 newsletter perform — delivered, opens, clicks?"
</Info>

### The Chat Experience

* **Live plan** — the agent shows its plan as a checklist and ticks items off as it works.
* **Streaming activity** — see which specialist and which tool is running, live.
* **Parallel-agent tree** — fan-out work (for example, several emails) renders as a tree, not a wall of text.
* **Inline artifacts and previews** — emails show a thumbnail; journeys render as a Mermaid diagram.
* **File uploads** — drop in a brief or asset and the agent works from it.

## Use Cases

**Brief to reviewable journey, in one sitting.** Paste a campaign brief; the agent sizes the audience, drafts the emails, and assembles the journey draft — review and activate when ready. Lifecycle teams run their whole program this way — onboarding, activation, re-engagement, win-back — even with a small team.

**The weekly newsletter, faster.** Draft and restyle the email, confirm the audience, drop it into the send journey.

**Live audience sizing on a working call.** Ask counts and compositions to pressure-test an idea before you build it — useful for demos and planning sessions.

## Limitations

**Drafts, not auto-activation.** You decide when a journey or send goes live.

**Segment sizes settle after save.** A new category populates within approximately 10 minutes; previews before then can overlap.

**Custom CSS lives in the editor.** Plain-language style edits cover common cases; bespoke `@media`/`<style>` rules go in the BEE editor.

**One build per request.** Ask for one email or audience at a time for clean, reviewable steps.

### What the Agent Can Access

Your data schema and business context, your existing assets (journeys, emails, segments, tokens), filter types and token functions, and analytics rollups — enough to build things that fit your account.

### What It Cannot Access

Individual PII beyond a contact lookup you request, other users' chats, or anything outside your Inflection workspace.

## Prompting Best Practices

**Lead with the goal, not the mechanics.** "Re-engage trial users who stalled after signup" works better than a list of filters.

**Let it ground first.** The agent checks your real values before composing — give it the business term.

**Iterate in conversation.** Start rough, refine over follow-ups.

**Say "save" when you mean it.** Nothing is committed until you ask.

## Report Unexpected Outcomes

If the agent is not delivering after following these tips, tell your CS team in Slack: include a link to the conversation, your goal, and screenshots of the prompt and the output.

## Share Your Use Cases

We tune the agents on how you use them — tell us what worked, where it struggled, and what would make it more useful.


# Inflection Agents
Source: https://docs.inflection.io/agents/inflection-agents

These are the agents that work across multiple surfaces (in-app, Claude, Slack, Asana, etc.).

## Meet the Agents

| **Agent** | **What it does** | **Example prompt** |
| - | - | - |
| **Audience** | Turns a description into a saved, auto-refreshing dynamic list | "Enterprise accounts in California, active in 30 days." |
| **Content (email)** | Drafts and edits emails — from a brief or by editing a template by name | "Write a welcome email with a 20% offer." |
| **Segment** | Builds ordered, mutually-exclusive segment categories | "Lifecycle segments: New, Active, At Risk, Churned." |
| **Token** | Creates and verifies personalization tokens, including computed scores | "A token for first name with a fallback of 'there'." |
| **Journey building** | Assembles multi-step journey drafts (emails, delays, branches) | "Draft a 3-step onboarding journey." |

## Audience Agent

Describe who you want to reach and the agent builds a reusable dynamic list, grounded in your real field values. Use this to target contacts without manually configuring the filter UI.

## Content Agent

Drafts on-brand emails from a brief, restyles elements in plain language, and edits saved templates by name — with a preview before anything sends.

## Segment Agent

Creates first-match-wins segment categories for lifecycle stages, tiers, and engagement levels.

## Token Agent

Builds and verifies personalization — from simple field references to arithmetic PQL scores — and shows a previewed result before you save.

## Journey Building

There is no separate journey agent. Build journey drafts by describing the flow directly; review and activate in the app.

## Where to Use the Agents

All agents work across multiple surfaces. Each surface has its own setup guide.

| **Surface** | **Best for** |
| - | - |
| **In-app chat** | The full visual experience — live plan, inline previews, file uploads |
| **Claude** | Power use from your AI client; chain steps in one thread |
| **ChatGPT** | Same agents in ChatGPT (coming soon) |
| **Slack** | Kick off a campaign from your team channel, with approval gates |
| **Asana** | Turn a tagged task brief into a built email |

## What the Agents Can and Cannot Do

**They build, you activate.** Agents draft and save assets; you decide when journeys and sends go live.

**They ground in your data.** Agents read your schema, fields, and business context, and do not expose individual contact data.

**They do not replace the UI for everything.** Some edits and all activation happen in the Inflection app.

## Get the Best Results

**Lead with the goal.** "Re-engage trial users who stalled" works better than a list of filters.

**Give business terms, not field names.** The agent maps your terminology to your real data values.

**Work one task at a time, and say "save" when ready.**

## Report a Problem

If an agent is not delivering the expected result, contact your customer success team in Slack with a link to the conversation, your goal, and screenshots.

<Info>
  **Pick your surface:** Overview and setup guides for each surface:

  1. [In-App Chat](/agents/in-app-chat)
  2. [Integrate with Claude](/agents/integrate-with-claude)
  3. [Integrate with ChatGPT](/agents/integrate-with-chatgpt)
  4. [Integrate with Slack (COA)](/agents/integrate-with-slack)
</Info>


# Inflection MCP
Source: https://docs.inflection.io/agents/inflection-mcp

Understand the tools available via Inflection's MCP server.

The **Inflection MCP** connects any MCP-compatible AI client to your Inflection workspace. Use it to build audiences, emails, tokens, segments, and journeys, pull analytics, and look up contacts — all by conversation.

For client setup, see the [Integrate with Claude](/agents/integrate-with-claude) guide or [Integrate with ChatGPT](/agents/integrate-with-chatgpt).

## Specialist Agents

**`ask_agent`** starts and polls the Inflection specialist agents. It works in two modes: pass `agent_type` and `prompt` to start a run, or pass `run_id` to poll an existing one. The server long-polls for approximately 12 seconds. Use `ask_agent` for domain Q\&A as well (for example, "what's the syntax for…").

| `agent_type` | What it builds |
| - | - |
| `audience` | Dynamic-list filters from natural language → saved audience |
| `content` | Emails (HTML + BEE) → saved email |
| `segment` | Ordered, first-match segment categories → saved category |
| `token` | Personalization tokens (create, edit, verify, preview) |

Journeys have no specialist agent. Drive them directly with `create_platform_asset(asset_type='journey')` and `update_platform_asset` for incremental edits.

## Platform CRUD

* **`list_platform_assets`** — list or search any asset type: `journey`, `email`, `audience`, `segment`, `static_list`, `email_token`, `webhook`, `inbound_webhook`, `form`, `account`, `conversion`, `salesforce_opportunity` (plus Salesforce campaign variants). Supports `keyword`, paging, and type-specific filters.
* **`get_platform_asset`** — fetch one asset by ID. Supported types: `journey`, `email`, `segment`, `email_token`, `static_list`, `account`, `webhook`, `inbound_webhook`, `form`, `conversion`, `salesforce_opportunity`.
* **`create_platform_asset`** — create: `journey`, `email` (including clone via `clone_from`), `email_token`, `tag`, `folder`, `static_list`.
* **`update_platform_asset`** — patch: `email`, `email_content`, `journey`, `email_token`, `business_context`, `tag_asset`, `move_asset`, `folder`, `static_list` (rename). Segment edits go through **`ask_agent(agent_type='segment')`**.

## Discovery

* **`get_schema`** — returns schema for: `person`, `product_activity`, `product_events`, `marketing_events`, `event_properties`, `filter_types`, `filters_meta`, `operators`, `email_token_columns`, `token_functions`.
* **`get_platform_context`** — returns: `business_context`, `email_settings`, `folders`, `tags`, `settings`.
* **`data_dictionary`** — browse your real data: entities (`contact`, `account`, `product_user`, `organisation`, `puom`), fields, distributions, and distinct values (5 query types). Call this before composing a filter whose value was described vaguely.

## Artifacts

* **`list_artifacts`** / **`get_artifacts`** — retrieve asset drafts produced by a run in the current thread. Supported types: `DYNAMIC_LIST`, `EMAIL_TEMPLATE`, `SEGMENT_CATEGORY`, `JOURNEY`, and others.

## Analytics

* **`get_analytics_report`** — aggregate and rollup metrics: `campaign_stats`, `campaign_aggregate`, `journey_rollup`, `journey_conversions`, `active_sends`. Delivery and engagement variants include a `display` block that matches the dashboard layout.
* **`get_analytics_breakdown`** — per-entity detail (paginated): `top_links`, `top_email_client_opens`, `top_email_client_clicks`, `recipient_engagement` (8 event types), `campaign_runs`, `form_submissions`, `inbound_webhook_submissions`.

## Contacts

* **`get_contact_info`** — supports three query types: `lookup` (by email → composite profile), `activity_log`, `sf_opportunities`, `sf_campaigns`.

## Knowledge

* **`get_knowledge`** — access the skill tree, cross-knowledge search, and Help Center search. Also surfaces published skills such as `grade-html-email`.

## Personalized Email Versions

* **`set_email_version`** / **`list_email_versions`** / **`delete_email_version`** — manage per-contact versions on a [Personalized Email Asset](/agents/personalized-email): set a contact's subject, preheader, and HTML; list existing versions; or delete one. Versions are validated on arrival (known contact, unsubscribe link present, no other tokens, 500 KB cap); contacts without a version get the asset's default email.

## Asset Types — Read / Write Support

| **Asset** | **Read** | **Create** | **Update** | **Notes** |
| - | - | - | - | - |
| `journey` (campaign) | ✅ | ✅ | ✅ | Driven directly; no agent |
| `email` (template) | ✅ | ✅ | ✅ | Clone via `clone_from`; build via content agent |
| `email_token` | ✅ | ✅ | ✅ | Via token agent |
| personalized email (versions) | ✅ | ✅ | ✅ | `set_email_version` / `list_email_versions` / `delete_email_version`; the asset itself is created in the dashboard |
| `audience` (dynamic list) | ✅ | Via agent | Via agent | Audience agent |
| `segment` category | ✅ | Via agent | Via agent | Segment agent only |
| `static_list` | ✅ | ✅ | Rename | Member operations in dashboard |
| `folder` / `tag` | ✅ | ✅ | Move / rename | Organize assets |
| `contact` | ✅ | — | — | By email via `get_contact_info` |
| `account` | ✅ | — | — | Read-only |
| `form` | ✅ | — | — | Authoring in dashboard |
| `webhook` / `inbound_webhook` | ✅ | — | — | Writes deferred |
| `conversion` | ✅ | — | — | Writes deferred |
| `salesforce_opportunity` | ✅ | — | — | Read-only; pipeline filters |

## Not Available via MCP Today

The following operations are not yet available via MCP and must be performed in the Inflection dashboard:

* Form authoring
* Static-list member operations
* Webhook and conversion writes
* Account writes
* Segment edits via direct tool (use the segment agent instead)

## Limits and Constraints

* **Drafts, not activation** — journeys and sends are activated in the app, not via MCP.
* **Segment sizing is post-save** — categories populate approximately 10 minutes after creation; per-segment previews overlap.
* **No custom CSS in emails** — use standard style fields only. `@media` and `<style>` blocks belong in the BEE editor.
* **One build per request** — create one email or audience at a time.

## Prompting Best Practices

Lead with your goal. Let the agent ground in your data first. Do one thing at a time. Say "save" when the result is ready to commit.

## Report an Issue

If a tool is not behaving as expected, contact your customer success team in Slack with a link to the conversation, your goal, and screenshots. Include which tools you rely on and what is missing.

<Info>
  **Additional reading:**

  1. [Integrate with Claude](/agents/integrate-with-claude)
  2. [Integrate with ChatGPT](/agents/integrate-with-chatgpt)
</Info>


# Integrate with ChatGPT
Source: https://docs.inflection.io/agents/integrate-with-chatgpt

Ideate and create segments and content with ChatGPT.

## Overview

Inflection integrates with ChatGPT through **MCP (Model Context Protocol)** using **Dynamic Client Registration (DCR)** for secure, streamlined authentication. Once connected, use Inflection's specialist agents directly from ChatGPT to build audiences, emails, tokens, segments, and journeys, and pull performance data — all through natural language.

## Prerequisites

* An active Inflection account
* A ChatGPT Plus, Team, or Enterprise subscription
* Workspace admin permissions in ChatGPT (for initial setup)

## For Workspace Admins: Add the Inflection MCP Server

Before users can connect, a workspace admin must enable Developer mode, create the app, and publish it to the workspace.

### Step 1: Enable Developer mode and create the app

1. Log in to [ChatGPT](https://chatgpt.com).
2. Click your profile icon, then click **Settings**.
3. Select **Apps** in the left sidebar.
4. Scroll to the bottom and click **Advanced settings**.
   <img alt="Advanced settings link in ChatGPT Apps settings" />
5. Toggle **Developer mode** on.
   <img alt="Developer mode toggle in ChatGPT settings" />
6. Click **Create app** and fill in the details:
   * **Name:** `Inflection MCP`
   * **Description:** (optional) `Connect to Inflection MAP`
   * **MCP Server URL:** `https://mcp.inflection.io/`
   * **Authentication:** Select `OAuth`
   * Leave **OAuth Client ID** and **OAuth Client Secret** blank — DCR handles this automatically.
     <img alt="Create app dialog with name, description, MCP server URL, and OAuth authentication fields" />
7. Select the acknowledgment checkbox: **"I understand and want to continue"**.
8. Click **Create**.

If successful, ChatGPT displays the list of tools the MCP server advertises.

### Step 2: Test the app

1. Open a new chat in ChatGPT.
2. Click the **+** button near the message composer, then click **More**.
3. Select **Inflection MCP** from the list of available tools.
4. Enter: `Show me my campaigns in Inflection`
5. Complete the OAuth authorization flow when prompted.
6. Verify the tools work — ChatGPT displays tool-call payloads for confirmation.
   <img alt="ChatGPT displaying a tool-call payload for confirmation" />

### Step 3: Publish for your workspace

1. Go to **Settings** → **Apps**.
2. Find your app under **Drafts**.
3. Click **Publish**.
4. Review the safety warnings (especially for write actions).
5. Confirm publishing.

Once published, the app appears in your workspace's approved apps list with a **custom** label.

### OpenAI documentation

[Connect ChatGPT to external apps — OpenAI developer docs](https://developers.openai.com/apps-sdk/deploy/connect-chatgpt)

## For Users: Connect Inflection to ChatGPT

### Step 1: Access settings

1. Log in to ChatGPT.
2. Click your profile icon.
3. Go to **Settings** → **Connectors**.

### Step 2: Find Inflection and connect

1. Find **Inflection MCP server** in the list of available connectors.
   <img alt="Inflection MCP server listed in ChatGPT connectors" />
2. Click **Connect**.

### Step 3: Authenticate

1. A browser window opens automatically.
2. Log in with your Inflection credentials if prompted.
3. Review the consent screen, which shows:
   * The app name (ChatGPT)
   * The redirect URL
   * The permissions being requested
4. Click **Authorize** to grant access.
   <img alt="Consent screen showing the Authorize button" />

### Step 4: Confirmation

Once authenticated:

* The browser displays "Authentication complete".
* Close the browser tab.
* Return to ChatGPT — your connection status changes to **Connected**.

## Using Inflection in ChatGPT

Once connected, use natural language to interact with Inflection.

### What you can do

| Function | Description |
| - | - |
| **Audiences** | Build and save dynamic lists from a description |
| **Email** | Draft, restyle, edit by name, and save emails |
| **Segments / Tokens** | Create segment categories; create and verify tokens |
| **Journeys** | Draft multi-step journeys for review |
| **Analytics** | Pull dashboard-accurate performance data |

### Example commands

**Campaigns:**

* `Show me my recent campaigns in Inflection`
* `What's the performance of my last email campaign?`
* `List all active campaigns`

**Segments:**

* `Create a new segment for users who signed up last month`
* `Show me the segment for enterprise customers`

**Templates:**

* `List my email templates`
* `Show me the details of the welcome email template`

**Analytics:**

* `What's the open rate for my newsletter campaign?`
* `Show me campaign analytics for the last 30 days`

## Troubleshooting

| Issue | Cause | Solution |
| - | - | - |
| Connection fails | Browser blocked popup | Allow popups for `chat.openai.com` |
| 400 error | Session/cookie issue | Don't copy-paste the auth URL — let it open naturally |
| Can't find connector | Admin hasn't added it | Ask your workspace admin to add the MCP server |
| Tools not working | Connection expired | Disconnect and reconnect |

<Info>
  **Do not copy the authentication URL.** The auth flow sets cookies in your browser. Copying the URL breaks the session.
</Info>

<Info>
  **Use the same browser.** Complete the entire auth flow in the browser that ChatGPT opens automatically.
</Info>

<Info>
  **Tool calls may not all display.** ChatGPT sometimes doesn't show all tool calls in the UI, but they are still executing.
</Info>

## Additional resources

1. [Inflection Agents](/agents/inflection-agents) — what each specialist agent does
2. [Inflection MCP](/agents/inflection-mcp) — the complete tool reference
3. [Integrate with Claude](/agents/integrate-with-claude)


# Integrate with Claude
Source: https://docs.inflection.io/agents/integrate-with-claude

Ideate and create segments and content with Claude.

Connect Inflection to Claude to build audiences, emails, tokens, segments, and journeys, pull performance data, and look up contacts — all by chatting in Claude Desktop or [Claude.ai](http://Claude.ai). Inflection is available as a **Community connector** in Claude's connector directory, so you can add it in a few clicks — no server URL to paste. The integration uses the Model Context Protocol (MCP) with Dynamic Client Registration (DCR) for secure, streamlined authentication.

## Prerequisites

Before you begin, confirm you have:

* An active Inflection account
* Access to Claude Desktop or [Claude.ai](http://Claude.ai)
* On Claude Team or Enterprise plans: an Owner or Primary Owner to add the connector to your organization (one-time setup)

## Add Inflection to Your Workspace

<Info>
  This section applies to Claude **Team** and **Enterprise** plans. Members can only connect to connectors an Owner or Primary Owner has added to the organization. On Pro and Max plans, skip ahead to [Connect Inflection to Claude](#connect-inflection-to-claude).
</Info>

An Owner or Primary Owner adds Inflection from Claude's connector directory once. No server URL is needed.

1. Log in to [claude.ai](http://claude.ai).
2. Click your profile icon in the bottom-left corner, then click **Organization settings**.
3. Click **Connectors**.
4. Click **Browse connectors** at the bottom of the page.
5. Search for `inflection` and select **Inflection.io** — it's listed as a **Community** connector by Inflection.io.
   <img alt="Inflection.io shown as a Community connector in the Claude connector directory" />
6. On the connector's directory page, click **Add to your team**.

Once added, the connector page shows **Connected**, and the **⋮** menu offers **Remove from your team** if you ever need to roll it back.

Adding the connector makes it available to everyone in the organization, but it doesn't connect anyone automatically. Each member still authenticates with their own Inflection credentials in the next section.

<Tip>
  The **Tools** tab on the connector page lets admins set **tool permission restrictions** — a ceiling (Always allow, Ask, or Block) for each Inflection tool across your organization. Members can always choose a stricter setting for themselves.
</Tip>

## Connect Inflection to Claude

Each user completes these steps once in their own Claude account.

### Step 1: Open Connectors

1. Open Claude Desktop or go to [claude.ai](http://claude.ai).
2. Click your profile icon in the bottom-left corner.
3. Click **Settings**.
4. Click **Connectors**.
   <img alt="Connectors item in the Claude settings sidebar" />

### Step 2: Find Inflection and Connect

1. Find **Inflection.io** in your connectors list.
   * On Team and Enterprise plans it's already listed once your admin has added it.
   * On Pro and Max plans, click **Browse connectors**, search for `inflection`, and select **Inflection.io** (the **Community** connector by Inflection.io).
2. Click **Connect**.

### Step 3: Authenticate

1. A browser window opens automatically.
2. Log in with your Inflection credentials if prompted.
   <img alt="Inflection login prompt in the browser authentication window" />
3. Review the consent screen, which shows the app name (Claude), the redirect URL, and the permissions being requested.
4. Click **Authorize** to grant access.
   <img alt="Consent screen showing the Authorize button" />

### Step 4: Confirm the Connection

Once authenticated, the browser shows "Authentication complete" — close that tab. Back in Claude, the **Inflection.io** connector status changes to **Connected**.

<Info>
  On the first message of each new thread, the agent loads your business context so everything it builds fits your account.
</Info>

## Use Inflection in Claude

The table below shows what you can do and example phrases to get started.

| **Capability** | **What you can do** | **Try saying** |
| - | - | - |
| **Audiences** | Build and save dynamic lists | "Build a list of enterprise accounts in California." |
| **Email** | Draft, restyle, edit by name, save | "Edit the 'Welcome' email — make the CTA green." |
| **Segments** | Create and edit categories | "Lifecycle segments: New, Active, At Risk, Churned." |
| **Tokens** | Create, verify, and compute scores | "Score = 3×demo\_requests + 1×opens over 90 days." |
| **Journeys** | Draft multi-step flows | "Draft a 3-step onboarding journey." |
| **Analytics** | Pull dashboard-accurate results | "How did the Q1 newsletter perform?" |

Chain tasks in one thread — size an audience, draft the emails, assemble the journey — because the agent keeps context across turns.

### Example commands

**Campaigns:**

* "Show me my recent campaigns."
* "What's the performance of my last email campaign?"
* "List all active campaigns."

**Segments:**

* "Create a new segment for users who signed up last month."
* "Show me the segment for enterprise customers."

**Templates:**

* "List my email templates."
* "Show me the details of the welcome email template."

**Analytics:**

* "What's the open rate for my newsletter campaign?"
* "Show me campaign analytics for the last 30 days."

<Info>
  **A good first session**

  * "How many contacts opened an email in the last 30 days?"
  * "Draft a re-engagement email for the ones who didn't, and save it."
  * "Build an audience of those contacts and save it as 'Dormant – 30d'."
</Info>

## Tips

**Set tools to Always allow** to avoid repeated permission prompts.

**Refresh the tool list** after new tools ship — go to **Settings** > **Connectors** > **Inflection.io** > **Refresh tool list**.

**One build per request.** Say "save" when you're ready to commit a draft.

## Good to know

* **Drafts, not activation** — activate journeys and sends in the Inflection app.
* **No custom CSS** in emails via chat (use the BEE editor in-app); style fields are supported.
* **Some assets are read-only** here — forms, webhooks, conversions, and accounts.

## Additional resources

1. [Inflection Agents](/agents/inflection-agents) — what each specialist agent does
2. [Inflection MCP](/agents/inflection-mcp) — the complete tool reference
3. [Integrate with ChatGPT](/agents/integrate-with-chatgpt)

If the agent isn't delivering the expected results, share a conversation link with your customer success team in Slack, including your goal and screenshots of the prompt and output.


# Integrate with Slack (COA)
Source: https://docs.inflection.io/agents/integrate-with-slack

Use Inflection's Slack agent to ideate journeys, build segments, and more.

The Inflection Slack agent builds simple campaigns through natural conversation, from Slack. The agent specializes in each aspect of your marketing workflow, working to help you segment audiences, create content, and build journeys.

Non-Inflection users can interact with the Inflection Slack agent directly in Slack.

## Connect the Slack Agent

<Info>
  **Prerequisite**: The Slack Agent (Campaign Operations Agent) must be enabled for your org. Verify the feature is enabled: In Inflection, navigate to **Settings** and confirm the **Campaign Operations Agent** tab is visible. If it is not, talk with your customer success team to enable this feature.
</Info>

1. **Connect to Slack**: In Inflection, navigate to **Settings** > **Campaign Operations Agent**. Click **Connect to Slack**. This opens the Slack authorization page where you can install the app into your workspace.
2. **Add Inflection to your channel**: In the Slack channel you want to use for building campaigns, send a message mentioning Inflection (@Inflection). This will prompt you to add it to the channel.
3. **Configure the agent:** In Inflection, navigate to **Settings** > **Campaign Operations Agent** and click **Connect to Slack**. Here you will need to:
   1. Add an email template: when the Slack agent creates emails, it will use this template. A template needs to be added here in order for the Slack agent to build emails.
   2. Configure audience rules and content/branding guidelines.
4. **Test & Validate**: To create a campaign, you can either use the `/campaign-intake` command in Slack to pull up a standardized form, or @mention the Inflection bot directly for a conversational campaign creation flow.

## Engage with the Slack Agent

There are two ways to start building a campaign with the Slack agent.

### Option 1: Campaign Intake Form

Type `/campaign-intake` in any Slack channel to open the Campaign Intake form. The form will ask you to provide:

* **Journey Name:** a name for your campaign
* **Journey Description:** describe the campaign goal (e.g., "Create a new campaign for users who have not logged in for the last 30 days. Email them a reminder to log in.")
* **Audience Notes** (optional): specify targeting criteria (e.g., "Target users who haven't logged in for 30+ days, exclude trial users, focus on enterprise customers")
* **Content Copy** (optional): provide tone, offer details, or copy guidance (e.g., "Use a friendly, encouraging tone, include a special offer, mention new features, keep it under 200 words")

Submit the form and the agent will get to work building your campaign assets.

### Option 2: Conversation

Start your chat with the Slack agent with the following prompt:

> @Inflection can you help me create a campaign?

Next, the agent will ask a series of questions it needs answered to build the campaign. Message by message, it will ask you to:

* Name the campaign
* Describe the audience for the campaign
* Describe content for the campaign

<Info>
  Note that every response intended for the agent needs to mention the agent (@Inflection). The agent will respond with 👀 eyes emoji to acknowledge it sees your message. Once it sees the message, it will take a few minutes to think and/or work in Inflection and respond with a message.

  Collaborate with others freely (mention them on content previews or audience counts) — if you don't mention the agent, it won't chime in or get confused.
</Info>

Once you approve assets for creation, the Slack agent will provide a link to each asset.

## Capabilities

### Overview

| **Functions** | **Ideate** | **Create** | **Edit** | **Example/Detail** |
| - | - | - | - | - |
| **Journey Audiences** | ✅ | ✅ | via UI | "I want to target C-level marketers who have logged into the product in the past 30 days." |
| **Email Content** | ✅ | ✅ | via UI | Ideate and draft emails; preview email content; create emails |
| **Journeys: Simple** | ✅ | ✅ | via UI | Create a single flow step journey, like a newsletter or announcement |

### Audiences

The Slack agent can answer questions about your audience and provide counts based on specific criteria.

**What it can do:**

* Answer audience-related questions (counts, lists by properties/activities)
* Create dynamic lists from natural language queries
* Return audience sizes for specific criteria
* Help you understand audience composition

<Tip>
  **Example prompts**

  * "How many users opened an email in the last 7 days?"
  * "Show me the count of customers in the Technology industry"
  * "How many contacts are on our newsletter list?"
  * "Based on the audience criteria in this journey, will my developer audience qualify for this journey?"
</Tip>

### Content

The Slack agent can create and refine email content using natural language instructions.

**What it can do:**

* Generate professional email templates from descriptions
* Modify existing email content while preserving styling and structure
* Work with both HTML templates and BEE (Block Email Editor) JSON format
* Answer questions about content creation and best practices
* Create preview versions of email content
* **Save new emails to your system** when requested

<Tip>
  **Example prompts**

  * "Create a welcome email for new customers with a 20% discount offer"
  * "Make the subject line more engaging and add a call-to-action button"
  * "What are best practices for email subject lines?"
  * "Save this email template"
</Tip>

<Info>
  **Important note:** The system automatically uses the pre-mapped email template configured in Inflection (**Settings** > **Campaign Operations Agent** to review or update).
</Info>

### Journeys

The Slack agent can create simple, single-step journeys with a defined audience and send email flow step.

**What it can do:**

* Create a journey with the defined audience and email asset

<Tip>
  Follow the steps to Engage with the slack agent in the **Engage with Slack Agent** section of this doc.
</Tip>

## General Limitations

While the Inflection agent is powerful, it has intentional limitations:

**Cannot execute or activate:** The agent helps you build segments, content, and journeys, but you control when to activate them.

**Cannot access real-time counts in all contexts**: The agent can provide counts, but real-time population statistics may not always be available.

**Cannot read individual records**: The agent doesn't access PII or explain why specific records qualified/didn't qualify for segments.

**Cannot modify existing items directly:** The agent can suggest changes, but you apply them through the Inflection interface (except when explicitly saving new items).

**Cannot create custom fields**: The agent works with your existing data schema and can't add new fields to your system.

**Cannot analyze performance directly:** For detailed campaign analytics, use analytics tools via the UI rather than asking agents.

**Cannot write malicious code or bypass security**: The agent follows strict security protocols.

### What The Agent Can Access

Agents have access to information needed to help you effectively:

* **Your organization's data schema:** Available fields, attributes, and properties
* **Business context**: Publicly available or user-provided company description, ICP, competitors, target personas, positioning
* **Existing configurations:** Segments, templates, campaigns, and tags you've created
* **Filter types and operators:** Criteria options supported by Inflection
* **Conversation context:** Previous messages in your current session for iterative requests
* **Token functions:** Available personalization tokens and their syntax
* **Event definitions:** Marketing and product events you can segment by

### What The Agent Cannot Access

To protect privacy and data security, agents cannot access:

* **Customer data or PII:** No names, emails, phone numbers, or personal information
* **Individual user records:** Can't see specific contact details or explain individual qualifications
* **Detailed performance metrics:** Use dedicated analytics tools via the UI for campaign performance
* **Other users' conversations:** Each session is isolated and private
* **External systems directly:** The agent will work exclusively within Inflection

## Prompting Best Practices

Get better results from the Segments Agent by following these tips:

**Be specific about your audience goals.** Instead of "create a segment for engaged users," try "create a segment for users who opened at least 3 emails in the last 30 days and made a purchase in the last 90 days."

**Provide context about your business.** Agents work better when they understand your industry, products, and customer base. Consider setting up your business context in settings.

**Describe hierarchies and logic clearly.** If you want mutually exclusive segments or complex branching, explain the priority order and conditions upfront.

**Mention any edge cases or exclusions upfront.** If certain users should never be included (like test accounts or employees), say so at the beginning.

**Ask for explanations when needed.** If you're unsure about the logic, ask the agent to "explain how this segment works" or "walk me through who would be included in each sub-segment."

**Iterate in conversation.** Start with a rough idea and refine it through follow-up messages rather than trying to get everything perfect in one prompt.

**Be explicit about saving.** When you're ready to save segments, journeys, or templates to your system, clearly say "save these segments" or "save this to the system."

## Report Unexpected Outcomes

If you've followed prompting best practices and the agent isn't providing you with an expected outcome, please share the behavior with your customer success team in Slack.

### What counts as a bug

* The agent creates assets that don't match your description
* Generated criteria uses invalid fields or operators
* Logic is incorrect or produces conflicts
* Agent hallucinates, or claims capabilities it doesn't have
* Technical errors or failed responses
* Agent fails to save when explicitly requested

### How to report

Start a thread in your Inflection channel in Slack. Include:

1. A link to the conversation
2. Your goal for the conversation
3. A screenshot of your prompt
4. A screenshot of the unexpected output

Our team reviews all feedback and uses it to improve the agent.

## Share your use cases

We're constantly improving the Segments Agent based on how you use it. We'd love to hear about:

* **Complex segments you've built successfully** - what worked well?
* **Use cases the agent struggles with** - where does it need improvement?
* **Features you wish it had** - what would make it more useful?
* **Workflow integrations** - how does this fit into your broader marketing operations?
* **Time savings** - How have agents improved your productivity?


# Marketo Connector by Inflection
Source: https://docs.inflection.io/agents/marketo-connector

The Inflection-managed Marketo connector

*The Inflection-managed Marketo connector*

Use your Marketo from Claude in plain language. Two one-time setup steps, one by your Marketo Ops admin and one by your Claude admin, and then everyone on the team can use it.

The connector is hosted by Inflection, so there is nothing for your team to install or maintain. If you run into any issues, please reach out to the Inflection team.

***

## Part 1. Marketo Ops: connect Marketo to Inflection (once, \~2 minutes)

Needs an Inflection **admin** account and your Marketo API credentials.

**1.** Go to [**https://mcp-marketo.inflection.io/setup**](https://mcp-marketo.inflection.io/setup) and sign in with your Inflection account.

<img alt="Sign in to the Marketo connector setup page" />

<img alt="Marketo connector setup sign-in continued" />

**2.** Enter your Marketo **Client ID**, **Client Secret**, and **REST base URL**. In Marketo, the ID and secret are under Admin > LaunchPoint, and the URL is under Admin > Web Services (it looks like `https://123-ABC-456.mktorest.com`). Click **Test & Save**.

<img alt="Enter Marketo Client ID, Client Secret, and REST base URL" />

**3.** You'll see the connection confirmed. Marketo is now linked to your organization.

<img alt="Marketo connection confirmed" />

***

## Part 2. Claude admin: add the connector for your org (once, \~1 minute)

> In Claude for Work, custom connectors are added by a workspace **admin**. Individual members can't add them.

In [claude.ai](http://claude.ai), go to **Admin settings > Connectors > Add custom connector**, give it a name (e.g. *Marketo*), and enter the URL:

```javascript theme={null}
https://mcp-marketo.inflection.io
```

<img alt="Add custom connector in Claude admin settings" />

<img alt="Enter connector name and URL" />

Once added, the connector is available to everyone in your Claude workspace.

<img alt="Connector available to the Claude workspace" />

***

## Part 3. Everyone: connect and go

**1.** In a Claude chat, open the tools/connectors menu, find **the MarketoMCP**, and click **Connect**. Sign in with your **Inflection** account when prompted. (First time only; no Marketo credentials needed.)

<img alt="Connect to the MarketoMCP from a Claude chat" />

<img alt="MarketoMCP connect confirmation" />

**2.** Start asking:

* *"Pull the Marketo lead for [jane@acme.com](mailto:jane@acme.com) and show her recent activity."*
* *"What's the open and click rate on the Q2 newsletter?"*
* *"Clone last quarter's webinar program for the November event."*

***

**Something not working?** "Your organization hasn't connected Marketo yet" means Part 1 still needs doing. If you can't see the Marketo connector in Claude at all, Part 2 still needs your Claude admin. For anything else, contact your Inflection team.


# Inflection MCP — Trust & Security
Source: https://docs.inflection.io/agents/mcp-trust-security

This page documents how we run the MCP service, what data we handle, and how to reach us about security or support.

Inflection is a multi-tenant marketing automation platform that includes a Model Context Protocol (MCP) endpoint at `mcp.inflection.io`, exposing your tenant's marketing surface to AI assistants like Claude, ChatGPT, and Cursor.

This page documents how we run that service, what data we handle, and how to reach us about security or support.

## Deployment

* **Model:** Multi-tenant SaaS, single global region.
* **Cloud:** Amazon Web Services, US region.
* **Data plane:** AWS-managed document database (tenant data, run state, artifacts).

## Encryption

* **In transit:** TLS 1.2 minimum, with HSTS enabled.
* **At rest:** AES-256 via AWS KMS for all managed storage.

## Authentication & authorization

* **Protocol:** OAuth 2.1 with PKCE.
* **PKCE method:** `S256` only — `plain` is not accepted.
* **Discovery:** Standard OAuth 2.1 discovery via RFC 9728 (Protected Resource Metadata) and RFC 8414 (Authorization Server Metadata).
* **Tokens:** Bearer tokens; 15-minute access-token lifetime; refresh-token rotation with reuse-detection (a stolen refresh token invalidates the legitimate session).
* **Verification:** Every MCP tool call re-verifies the bearer token with our authorization server before any handler runs.

## Data handling

* **Tenant isolation:** Every MCP tool call is scoped to the caller's tenant ID. Cross-tenant reads are not possible from the MCP surface.
* **Bearer-token caching:** Verified tokens are cached in-memory for the length of their lifetime. Raw tokens are not logged or persisted.
* **Tracing:** LangSmith traces include `user_email`, `tenant_id`, `session_id`, and user-agent. Trace retention follows LangSmith's defaults.
* **Artifact retention:** Tool outputs (artifacts) are tenant-scoped and TTL'd: assets 30 days, agent outputs 7 days, intermediate results 24 hours.

## Compliance

* **SOC 2:** Type II attested (2026). Latest report available under NDA on request — contact `support@inflection.io`.
* **Penetration testing:** Independent third-party penetration test conducted in 2026; summary available under NDA on request.
* **GDPR:** Data Processing Addendum available on request from `support@inflection.io`.
* **CCPA:** Compliant; California resident data subject rights honored per our [Privacy Policy](https://www.inflection.io/legal/privacy-policy).
* **PCI / HIPAA:** Not in scope. We do not process payment card data or protected health information.

## Subprocessors

We share processing data with the following subprocessors:

| Subprocessor | Purpose | Data |
| - | - | - |
| Amazon Web Services | Infrastructure (compute, storage, network, managed database) | All tenant data at rest and in transit |
| OpenAI | LLM inference for AI agents | Prompts and conversation context |
| LangSmith | Agent trace observability | User email, tenant ID, prompts, tool calls |

## CORS configuration

The MCP endpoint at `mcp.inflection.io` uses a wildcard CORS origin (`Access-Control-Allow-Origin: *`). This is deliberate. The security boundary on a remote MCP server is the OAuth 2.1 bearer token, not the origin.

`Access-Control-Allow-Credentials` is set to `false`, which means browsers will not auto-attach cookies or HTTP-authentication credentials under wildcard CORS — CSRF against the MCP endpoint is structurally unreachable. The same wildcard pattern is used by every A-tier remote MCP (Notion, Linear, Atlassian, Stripe, GitHub, Asana).

Restricting the CORS origin would block legitimate AI hosts that we have no advance knowledge of — the product depends on arbitrary client origins reaching the endpoint and presenting valid bearer tokens.

## Support

* **General product support:** `support@inflection.io`
* **Documentation:** `https://docs.inflection.io`

## Security disclosure

To report a security vulnerability, contact `security@inflection.io`

## Change log

| Date | Change |
| - | - |
| 2026-06-02 | Initial publication. |


# Personalized Email Asset
Source: https://docs.inflection.io/agents/personalized-email

One email asset, a unique version per contact — a default email plus per-contact versions pushed in over the API or MCP.

A **personalized email** sends a different version of the same email to each contact — full custom copy, not just merged tokens — while keeping one asset, one journey step, and your usual deliverability and reporting. It's built for AI-generated 1:1 outreach at scale.

Every personalized email holds two things:

* a **default email** — the fallback everyone gets, and
* a store of **per-contact versions** — pushed in over the API or MCP.

At send time, each contact gets their own version if one exists; everyone else gets the default. No blank sends.

<Info>
  **How it resolves:** for each contact at the **Send email** step → their version if it's ready, otherwise the default email. Evaluated per contact, when they reach the step.
</Info>

<video />

## Create a Personalized Email

1. Go to **Emails** → **New Email**.
2. Choose **Per-Contact** as the editor type and give it a name.
3. Pick the **default email** — the fallback sent to anyone without a version. It must be an existing, sendable email (Visual or HTML).
4. Create. You land on the asset's **Versions** page.

<img alt="Creating a personalized email by choosing the Per-Contact editor type and selecting a default email" />

## The Asset at a Glance

The **Versions** page is the home of a personalized email. It has three tabs — **Versions**, **How to add versions**, and **Activity**. The **Versions** tab shows:

* **Stats strip** — Unique versions, Rejected (30d), and Last received.
* **Default email** card — the fallback, with a thumbnail and a **Change** button.
* **Per-contact versions** table — one row per contact (Contact · Status · Source · Updated), searchable by exact contact email.

<img alt="Versions tab showing the stats strip, default email card, and per-contact versions table" />

## Set or Change the Default Email

The default email is **required** — a personalized email can't run without one. To change it, click **Change** on the Default email card, pick another sendable email, and it's saved. Only Visual or HTML emails can be the default (not other personalized or AI emails). The default email also supplies the sender configuration for the asset — from name, from address, and reply-to all come from the default.

## Add Per-Contact Versions

Versions are pushed in programmatically — never typed in the dashboard. Open the **How to add versions** tab for the exact endpoint and MCP tool for this asset.

* **API** — for webhooks and backend integrations. `POST` the asset's endpoint (shown on the **How to add versions** tab) with a `Bearer` access token and a JSON body of `{ assetId, email, subject, preheader, html }` — add an optional `expiresAt` to expire the version. The access token comes from a connected app.
* **MCP** — for AI agents in Claude, ChatGPT, or any MCP client. Connect the [Inflection MCP](/agents/inflection-mcp), then ask in plain language, for example: "Add a personalized version on this asset for [contact@example.com](mailto:contact@example.com) — subject 'A note just for you' and an HTML body that includes an unsubscribe link."

Each version is validated on arrival: the contact must resolve to a known person, the HTML must include the unsubscribe link, be well-formed, contain no other tokens, and stay within the 500 KB size limit. Anything that fails is marked **Rejected** (with a reason) and the default sends instead — never blank.

<img alt="How to add versions tab showing the API endpoint and the MCP prompt for pushing versions" />

## Review Coverage and Preview a Version

The stats strip tells you how many contacts have a version. To check exactly what a contact will receive, click their row in the versions table to open a live preview of their email.

<img alt="Live preview of a contact's personalized version opened from the versions table" />

## Track Changes in Activity

The **Activity** tab is the audit trail: every version **created**, **updated**, **deleted**, or **rejected** (with its reason), filterable by action and source.

<img alt="Activity tab listing version events with time, contact, action, source, and actor" />

## Send It in a Journey

Add a **Send email** step and pick the personalized email. The step shows a **Personalized · falls back to default** pill so you know it resolves per contact. When a contact reaches the step, they get their version if it's ready, otherwise the default.

<img alt="Journey canvas with a Send email step configured with a personalized email" />

## See a Contact's Personalized Versions

On any contact's detail page, the **Personalised assets** tab lists every personalized email that contact has a version for — with its status, source, and last updated.

<img alt="Contact detail page with the Personalised assets tab listing the contact's versions" />

<Info>
  **In short:** one asset = a default email + a per-contact version store. Push versions over API/MCP, review coverage, and send in a journey — each contact gets their version, everyone else gets the default.
</Info>

## Good to Know

* **One asset, one journey step** — resolution happens per contact at send time, so reporting and deliverability work exactly like a normal email.
* **The default is mandatory** — the asset can't run without a sendable default.
* **Versions are programmatic** — pushed over API or MCP, never typed in the dashboard.

## Additional Resources

* [Send Personalized Emails from Clay](/agents/send-personalized-emails-from-clay) — push per-contact versions from a Clay table
* [Integrate with Claude](/agents/integrate-with-claude) — add versions by chatting with an AI agent
* [Inflection MCP](/agents/inflection-mcp) — the complete tool reference


# Send Personalized Emails from Clay
Source: https://docs.inflection.io/agents/send-personalized-emails-from-clay

Push a unique, per-contact email from a Clay table into an Inflection Personalized Email Asset with Clay's HTTP API column.

With Clay's **HTTP API** column, you can push a unique, per-contact email straight into an Inflection **Personalized Email Asset** — so each contact receives their own version of one email, sent from one journey step. This connects Clay's per-row personalization to Inflection's sending, deliverability, and reporting.

<Frame>
  <img alt="Exports4 Ezgif Com Optimize" />
</Frame>

<Info>
  This guide assumes you already have a Personalized Email Asset in Inflection. To create one, see [Personalized Email Asset](/agents/personalized-email).
</Info>

The flow: a Clay table (contact data and one HTML column per row) → an **HTTP API** column → Inflection's Email Versions API. Each contact who has a version gets it at send time; everyone else gets the asset's default email.

## Prerequisites

Before you begin, confirm you have:

* A Clay account with access to the **HTTP API** integration column.
* An Inflection account, and a **Personalized Email Asset** already created. Copy its asset ID from the asset URL (`…/assets/email/per-user/<ASSET_ID>/versions`) or the **How to add versions** tab.
* An Inflection API token — a **Personal Access Token (PAT)** from a connected app, or an OAuth access token. Both work as bearer tokens.
* Test contacts that **already exist** in your Inflection tenant. The API rejects versions for unknown contacts.

## Get Your Inflection Token

Create a PAT under **Settings** → **Connected Apps** — the step-by-step is in [Get Your Personal Access Token](/api-reference/get-your-pat). Copy the token and store it securely — you won't be able to see it again.

<Frame>
  <img alt="Connect Clay To Inflection" />
</Frame>

## Prepare Your Clay Table

Your table needs one column for each field you'll send:

| **Column** | **Description** |
| - | - |
| `Email` | The contact's email address. Must match an existing Inflection contact. |
| `Subject` | The personalized subject line. |
| `Preheader` | The inbox preview text. |
| `Html` | The full HTML of the personalized email. |

Use enrichment or an AI column (drawing on fields like first name, company, or title) to generate the `Html` column before the HTTP step.

<Info>
  **The unsubscribe rule.** Every version's HTML must contain the literal token `{{unsubscribe_url}}`, and Inflection rejects any other `{{…}}` token. Clay's own merge and formula fields also use `{{ }}`, so when you build the `Html` column, make sure `{{unsubscribe_url}}` survives as literal text — for example, wrap it as `{% raw %}{{unsubscribe_url}}{% endraw %}` in a formula. Referenced into the request body as `/Html`, the literal passes through unchanged.
</Info>

## Configure the HTTP API Column

Click **+** to add a column, search for **HTTP API**, and select it. The column's setup has a few sections — fill each one exactly as below.

### 1. Account (Authentication)

The **Account** holds your Inflection token so it never sits in the table. Create it once and reuse it.

1. Click **Select account** → **+ Add account**.
2. Under **API Request Headers**, add one row:
   * **Key:** `Authorization`
   * **Value:** `Bearer <your token>` — paste only the token after `Bearer`, with no quotes, no `<` or `>` or extra spaces.
3. Give the account a name (for example, `Inflection PAT`), save it, and select it.

<Info>
  Keep the token in the Account, not in the column's own Headers — the Account keeps it out of the table and lets you reuse it across columns.
</Info>

<img alt="Adding an HTTP API Account in Clay with the Authorization header" />

### 2. Column Mapping

Fill the request fields:

* **Method:** `POST`
* **Endpoint:** `https://api.inflection.io/v1/email-versions`
* **Body:** choose **JSON** and paste the following. Each `/Column` maps to that column's value for the row:
  ```json theme={null}
  {
    "assetId": "YOUR_ASSET_ID",
    "email": "/Email",
    "subject": "/Subject",
    "preheader": "/Preheader",
    "html": "/Html"
  }
  ```

<Frame>
  <img alt="Exports (2)" />
</Frame>

* **Headers:** add one key/value row —
  * **Key:** `Content-Type`
  * **Value:** `application/json`

<Frame>
  <img alt="Exports (5)" />
</Frame>

Wrap string references in quotes (`"email": "/Email"`); leave numeric or date references unquoted. To expire a version automatically, add an `expiresAt` field (ISO-8601): either a literal `"expiresAt": "2030-01-01T00:00:00Z"`, or map it to a Clay date column such as a "Date + 5 days" formula (unquoted). Omit the field entirely for a version that never expires.

### 3. Retry on Failure

Leave **Retry on failure** off. A rejected version (for example, a missing unsubscribe link) is a data issue to fix in the row, not something a retry resolves — keeping it off makes failures visible.

### 4. Run Settings

* **Auto-run:** off — so the column runs only when you click **Run**. This lets you test one row before pushing the whole table.
* **Custom rate limit:** optional. Set one if you're pushing a large table and want to pace the requests.

## Test, Then Run

1. Click **Run** on a single row.
2. Confirm a `200` response. A stored version returns `{ "data": { "status": "stored" }, "meta": { "status": "SUCCESS" } }`.
3. In Inflection, open the asset's **Versions** tab and confirm the contact now shows a version.
4. Run the column across the full table.

## Optional: Create Contacts First

The Email Versions API rejects versions for contacts that don't exist yet. If your Clay rows include new people, add an upstream **HTTP API** column that seeds them before the versions step — same Account, with:

* **Method:** `POST`
* **Endpoint:** `https://api.inflection.io/v1/contacts`
* **Body:** `{ "email": "/Email" }`

Contact creation is asynchronous — allow a few seconds before the versions step runs.

## Troubleshooting

**401 Unauthorized**

* Confirm the Account header is exactly `Authorization: Bearer <token>` with no duplicated `Bearer`, quotes, or whitespace — a malformed value is the most common cause.
* Confirm the **Endpoint** is `/v1/email-versions`, not a `/dash/...` path.
* Confirm the token's environment matches the host (preprod token → preprod host).

**400 Bad Request**

* Check the JSON — string values need quotes.
* Confirm `assetId` is a valid, existing Personalized Email Asset.

**Version rejected**

* **Contact not found** — the contact doesn't exist in the tenant yet. Seed it first.
* **Missing unsubscribe link** — the `Html` is missing the literal `{{unsubscribe_url}}` token.
* **Disallowed token** — the `Html` contains a `{{…}}` token other than `{{unsubscribe_url}}` (often a Clay merge field that leaked through).
* **Over size limit** — the `Html` is larger than 500 KB. Keep it lean and use hosted image URLs instead of inline base64.

## Good to Know

* **One version per contact, per asset.** Re-sending updates that contact's version.
* **The default always covers the rest.** Contacts without a version get the asset's default email — never a blank send.
* **Clay runs row by row.** Large tables take time depending on your Clay rate limits.

## Additional Resources

* [Personalized Email Asset](/agents/personalized-email) — how the asset, versions, and default work
* [Inflection MCP](/agents/inflection-mcp) — push versions from an AI agent instead of Clay
* [Clay HTTP API documentation](https://university.clay.com/docs/http-api-integration-overview)


# Asynchronous writes
Source: https://docs.inflection.io/api-reference/async-writes

Contact writes return a transaction you poll.

Creating, updating, or batching contacts (`POST`/`PATCH /v2/contacts*`) is processed asynchronously. The call returns `200` with a **PENDING** transaction: an acknowledgement, not the finished contact.

```json theme={null}
{ "data": { "transactionId": "34-7e8009a7-2c91-409e-b5ac-0f1144a0cc7d", "status": "PENDING" },
  "meta": { "status": "SUCCESS" } }
```

Poll `GET /v2/contacts/transactions/{transactionId}` until `status` is `DONE`. A completed batch carries per-contact results:

```json theme={null}
{ "data": { "transactionId": "34-...", "status": "DONE",
    "data": { "results": [ { "email": "jane@acme.com", "status": "CREATED" } ] } } }
```

Per-contact `status` is one of `CREATED`, `UPDATED`, `NO_CHANGE`, or `FAILED`. An unknown transaction id returns `NOT_EXIST` (still HTTP 200).


# Authentication
Source: https://docs.inflection.io/api-reference/authentication

Two ways to authenticate: a Personal Access Token or an OAuth 2.1 connected app.

Every call is authenticated with a bearer credential in the `Authorization` header:

```
Authorization: Bearer <token>
```

Two kinds of token work. Pick by how your integration runs:

| | Personal Access Token (PAT) | OAuth 2.1 connected app |
| - | - | - |
| Best for | Scripts, internal tools, server-side jobs | Multi-user apps, automation platforms, anything that shouldn't hold a long-lived secret |
| Lifetime | Long-lived, valid until revoked | Short-lived access token, renewed with a refresh token |
| Permissions | `READ` / `WRITE` scopes set on the token | Acts as the user who authorized the app |
| Setup | [Get Your Personal Access Token](/api-reference/get-your-pat) | [Inflection Connected Apps using OAuth 2.1](/agents/connected-apps-oauth) |

## Personal Access Tokens

PATs look like `inf_pat_…` and carry explicit scopes:

* **`READ`**: required for every `GET`.
* **`WRITE`**: required for `POST`, `PATCH`, and `DELETE`.

## OAuth access tokens

The access token your connected app obtains through the [OAuth 2.1 + PKCE flow](/agents/connected-apps-oauth) works on the Developer API as-is: same header, no separate registration. Two things to know:

* The token **acts as the user who authorized the app**: workspace admins and members can read and write; viewers are read-only.
* The token must belong to a user. Service-to-service tokens are rejected with `403`.

Refresh the access token with your refresh token as usual; nothing else about your API calls changes.

## Auth failures

Auth failures are returned by the gateway with an **empty body**. The status code carries the meaning:

| Status | Meaning |
| - | - |
| `401` | Missing, malformed, or invalid token. |
| `403` | Token is valid but lacks the required permission, for example a `READ`-scoped PAT attempting a write or a viewer's OAuth token doing the same. |

<Warning>
  A mistyped path or unsupported method under `/v1` or `/v2` also returns **401** (deny-by-default), not 404. If a valid token is suddenly getting 401s, check the path before the credential.
</Warning>


# Get a contact's activity log
Source: https://docs.inflection.io/api-reference/contact-activity/get-a-contacts-activity-log

/api-reference/openapi.yaml get /v2/contacts/{id}/activity-log
Paged, combined activity log. `eventTypes` filters to internal types
(`Contact Event`, `User Event`); other values are ignored.
`activityProperties` is free-form. Returns an empty list for an unknown
contact.




# Get a contact's marketing activity
Source: https://docs.inflection.io/api-reference/contact-activity/get-a-contacts-marketing-activity

/api-reference/openapi.yaml get /v2/contacts/{id}/marketing-activity
Paged list of marketing events (campaigns, forms, website visits, etc.).
Item shape varies by `activityType`; `context` and `additionalData` are
free-form. Returns an empty list for an unknown contact.




# Get a contact's product activity
Source: https://docs.inflection.io/api-reference/contact-activity/get-a-contacts-product-activity

/api-reference/openapi.yaml get /v2/contacts/{id}/product-activity
Paged list of product (in-app) events for the contact. Returns an empty list for an unknown contact.



# Get a contact's Salesforce record
Source: https://docs.inflection.io/api-reference/contact-activity/get-a-contacts-salesforce-record

/api-reference/openapi.yaml get /v2/contacts/{id}/salesforce
Returns the contact's mapped Salesforce record as a free-form object, or
`null` data if the contact exists but has no Salesforce record. The field
set may change.




# Batch create/upsert contacts
Source: https://docs.inflection.io/api-reference/contacts/batch-createupsert-contacts

/api-reference/openapi.yaml post /v2/contacts/batch
Enqueues an upsert for up to 1000 contacts. Returns a single `PENDING`
transaction covering all items; poll the transaction for per-contact
results.




# Create a contact
Source: https://docs.inflection.io/api-reference/contacts/create-a-contact

/api-reference/openapi.yaml post /v2/contacts
Enqueues creation of a contact. Returns a `PENDING` transaction
acknowledgement (200). The contact is created asynchronously. Any `id`
in the body is ignored.




# Get a contact by email
Source: https://docs.inflection.io/api-reference/contacts/get-a-contact-by-email

/api-reference/openapi.yaml get /v2/contacts/by-email/{email}



# Get a contact by id
Source: https://docs.inflection.io/api-reference/contacts/get-a-contact-by-id

/api-reference/openapi.yaml get /v2/contacts/{id}



# Get a contact write transaction
Source: https://docs.inflection.io/api-reference/contacts/get-a-contact-write-transaction

/api-reference/openapi.yaml get /v2/contacts/transactions/{transactionId}
Returns the status of an async contact write. `status` is `PENDING`
while processing, `DONE` with per-contact `data.results` when complete,
or `NOT_EXIST` for an unknown id (still HTTP 200).




# Update a contact
Source: https://docs.inflection.io/api-reference/contacts/update-a-contact

/api-reference/openapi.yaml patch /v2/contacts/{id}
Enqueues an update for the contact. Returns a `PENDING` transaction
acknowledgement (200), applied asynchronously.




# Set a personalized email version
Source: https://docs.inflection.io/api-reference/email-versions/set-a-personalized-email-version

/api-reference/openapi.yaml post /v1/email-versions
Stores the personalized version of a [Personalized Email Asset](/agents/personalized-email) for one contact. One version per contact per asset; re-posting for the same contact replaces their version. At send time the contact receives their version if it's ready; contacts without one get the asset's default email.

Validation on arrival: `email` must resolve to an existing contact, and `html` must contain the literal `{{unsubscribe_url}}` token, contain no other `{{…}}` tokens, and stay within 500 KB. A version that fails validation is rejected with a reason (visible on the asset's **Activity** tab) and the default email sends instead.



# Create an email
Source: https://docs.inflection.io/api-reference/emails/create-an-email

/api-reference/openapi.yaml post /v2/emails



# Get an email
Source: https://docs.inflection.io/api-reference/emails/get-an-email

/api-reference/openapi.yaml get /v2/emails/{id}



# List emails
Source: https://docs.inflection.io/api-reference/emails/list-emails

/api-reference/openapi.yaml get /v2/emails
Paged list of email assets. `type` is repeatable. The heavy fields
(`content`, `contentJson`, `previews`) are not returned. Read one email
for those. `isEmpty` is derived. An unresolvable `folderId` yields an
empty page rather than an error.




# Errors & status codes
Source: https://docs.inflection.io/api-reference/errors

What to expect when something's missing or wrong.

| Situation | Status | Code |
| - | - | - |
| Contact not found (by id or email) | `400` | `BAS-E-002` |
| List or email not found | `404` | `NOT_FOUND` |
| Duplicate list name | `409` | `LIST_ALREADY_EXISTS` |
| Duplicate email name | `409` | `TEMPLATE_ALREADY_EXISTS` |
| Request body fails validation | `400` | `VALIDATION_ERROR`, with a field detail such as `fromEmail._schema` |
| From-email domain not approved for the org | `400` | `UnapprovedEmailDomainException` |
| Removing an unknown contact from a list | `404` | `CONTACT_NOT_FOUND` |
| Rate limit exceeded | `429` | See [Rate Limits](/api-reference/rate-limits) |

<Warning>
  A missing **contact** returns `400`, while a missing **list** or **email** returns `404`. Handle both. Don't assume a single not-found code across resources.
</Warning>

## Errors inside a 200

Two cases return `200` and still carry an error signal. Check the body, not just the status:

* **Bulk member add with unknown ids**: the valid ids are added, and the response's `errors[]` array carries `CONTACTS_NOT_FOUND` for the ids that were skipped.
* **Unknown transaction id**: `GET /v2/contacts/transactions/{transactionId}` returns `200` with `status: NOT_EXIST` instead of an HTTP error.


# Get Your Personal Access Token
Source: https://docs.inflection.io/api-reference/get-your-pat

Create the Personal Access Token (PAT) that authenticates your API calls.

Every Developer API call is authenticated with a **Personal Access Token (PAT)** sent as a bearer credential. You create PATs in the Inflection dashboard. One per integration is a good habit, so you can revoke one without breaking the others.

## Create a token

1. In Inflection, go to **Settings** → **Connected Apps**.
2. Open the **Personal Access Tokens** tab and click **Create app credentials**.
3. Name the token and create it. Copy the token and store it securely. It won't be shown again. If you lose it, revoke the token and create a new one.

<img alt="Creating a Personal Access Token under Settings, Connected Apps" />

## Use it

Send the token on every request:

```
Authorization: Bearer inf_pat_...
```

Tokens are scoped: **READ** for `GET` calls, **WRITE** for `POST`/`PATCH`/`DELETE`. See [Authentication](/api-reference/authentication) for scopes and how auth failures are reported.

<Info>
  PATs are long-lived tokens for the API. They do **not** work for MCP. MCP clients authenticate through a [connected app's OAuth flow](/agents/connected-apps-oauth).
</Info>


# Introduction
Source: https://docs.inflection.io/api-reference/introduction



The Inflection Developer API gives you programmatic access to the core objects of your workspace. It's organized around these resources:

* **Contacts**: look people up by id or email, create them, and keep their attributes in sync.
* **Contact activity**: a contact's product events, marketing engagement, a change log of record properties, and the mapped Salesforce record.
* **Lists & members**: list your static and dynamic lists, and manage static lists and the contacts on them.
* **Emails**: create HTML emails in Inflection, list emails, and fetch emails (both HTML and visual editor) by ID.
* **Journeys**: list journeys and read a journey's schedule and derived status.
* **Stats**: send and engagement metrics for journeys and emails, with rollups across many journeys or emails in one call.
* **Product users**: the product logins underneath a contact, by id or email, with async create and update.
* **Organizations**: company accounts, their product users, and a contact's memberships.
* **Email versions**: push per-contact versions of a [Personalized Email Asset](/agents/personalized-email) via `POST /v1/email-versions` for 1:1 sends at scale. See [Send Personalized Emails from Clay](/agents/send-personalized-emails-from-clay) for a worked example.

<Info>
  Every path lives under `/v2` on the API gateway: `https://api.inflection.io`. `/v2` is `/v1` plus more: every `/v1` endpoint is served under `/v2` unchanged, and `/v1` remains published, so existing clients keep working. Journeys, stats, the email and list collections, product users, and organizations are `/v2` only. The one exception is `POST /v1/email-versions`, which is served under `/v1`.
</Info>

The API is JSON over HTTPS, authenticated with a bearer token, either a Personal Access Token or an OAuth access token (see [Authentication](/api-reference/authentication)). Reads are synchronous; contact writes are processed asynchronously and return a transaction you poll (see [Asynchronous writes](/api-reference/async-writes)).

<CardGroup>
  <Card title="Quickstart" icon="rocket" href="/api-reference/quickstart">
    From zero to your first response in two calls.
  </Card>

  <Card title="Authentication" icon="key" href="/api-reference/authentication">
    Tokens, scopes, and what 401 vs 403 mean.
  </Card>
</CardGroup>


# Get a journey
Source: https://docs.inflection.io/api-reference/journeys/get-a-journey

/api-reference/openapi.yaml get /v2/journeys/{id}
The same passthrough as the listing, but keeping `schedule` and always
omitting `dynamicList`. Takes no query parameters.




# List journeys
Source: https://docs.inflection.io/api-reference/journeys/list-journeys

/api-reference/openapi.yaml get /v2/journeys
Paged list of journeys. `status`, `type` and `tag` are repeatable and OR
within themselves. `tag` matches the tag **name**, not its id, and a tag
or folder resolving to nothing yields an empty page rather than an error.
Repeating a single-valued parameter (`search`, `folderId`, `pageNumber`,
`pageSize`) is a 400.




# Add members to a static list
Source: https://docs.inflection.io/api-reference/lists/add-members-to-a-static-list

/api-reference/openapi.yaml post /v2/lists/{id}/members
Adds contacts (by id) to the list. Unknown contact ids are skipped and
reported in `errors` with a still-successful **200** (partial success).




# Create a static list
Source: https://docs.inflection.io/api-reference/lists/create-a-static-list

/api-reference/openapi.yaml post /v2/lists



# Delete a static list
Source: https://docs.inflection.io/api-reference/lists/delete-a-static-list

/api-reference/openapi.yaml delete /v2/lists/{id}
Soft delete. Returns **200** with a result body (not 204).



# Get a static list
Source: https://docs.inflection.io/api-reference/lists/get-a-static-list

/api-reference/openapi.yaml get /v2/lists/{id}



# Get members of a static list
Source: https://docs.inflection.io/api-reference/lists/get-members-of-a-static-list

/api-reference/openapi.yaml get /v2/lists/{id}/members



# List static and dynamic lists
Source: https://docs.inflection.io/api-reference/lists/list-static-and-dynamic-lists

/api-reference/openapi.yaml get /v2/lists
Both kinds behind one endpoint: static rows first, then dynamic, each
stamped with `type`. The row shape differs by kind. Discriminate on
`type`. Here `type` is **single-valued** rather than repeatable; omit it
to get both. `pagination.totalElements` is the sum of the two sources'
own counts. This endpoint takes no `folderId`.




# Remove a member from a static list
Source: https://docs.inflection.io/api-reference/lists/remove-a-member-from-a-static-list

/api-reference/openapi.yaml delete /v2/lists/{id}/members/{contactId}



# Update a static list
Source: https://docs.inflection.io/api-reference/lists/update-a-static-list

/api-reference/openapi.yaml patch /v2/lists/{id}
At least one of `name` or `folder` must be provided.



# Add product users to an organization
Source: https://docs.inflection.io/api-reference/organizations/add-product-users-to-an-organization

/api-reference/openapi.yaml post /v2/orgs/{id}/users
Asynchronous. The response is a transaction to poll, with one item per
user. Membership is many-to-many, so adding a user does not remove any of
its existing organizations.




# Create an organization
Source: https://docs.inflection.io/api-reference/organizations/create-an-organization

/api-reference/openapi.yaml post /v2/orgs
Synchronous, unlike contact and product-user writes: organizations have no
asynchronous pipeline, so the created organization is returned directly
rather than a transaction to poll.

A property whose name matches a column on your organization table is
written to that column as well as to the stored property bag, so it reads
back the same way an ingested organization does. A property with no
matching column is still stored, but only in the bag. Names the platform
owns (`id`, `_source`, `properties`, `properties_timestamp` and the
`_*_time` audit columns) are rejected.




# Get an organization
Source: https://docs.inflection.io/api-reference/organizations/get-an-organization

/api-reference/openapi.yaml get /v2/orgs/{id}



# List a contact's organizations
Source: https://docs.inflection.io/api-reference/organizations/list-a-contacts-organizations

/api-reference/openapi.yaml get /v2/contacts/{id}/orgs
The distinct organizations the contact belongs to. A contact holding
several product users in one organization yields that organization once.




# Update an organization
Source: https://docs.inflection.io/api-reference/organizations/update-an-organization

/api-reference/openapi.yaml patch /v2/orgs/{id}
Synchronous, like create. Supply `name`, `properties`, or both; a body with
neither is rejected. Properties are merged into the stored bag rather than
replacing it, so omitting a key leaves it untouched. There is no way to
remove a key through this endpoint.




# Pagination
Source: https://docs.inflection.io/api-reference/pagination

1-based pages on every list endpoint.

| Query param | Default | Notes |
| - | - | - |
| `page_number` | 1 | 1-based page index. |
| `page_size` | 20 | Items per page; max 200. |

Paged responses echo the window under `pagination` (`pageNumber`, `pageSize`, `totalElements`, `totalPages`).


# Create a product user
Source: https://docs.inflection.io/api-reference/product-users/create-a-product-user

/api-reference/openapi.yaml post /v2/users
Asynchronous. The response is a transaction to poll, not the created user,
because product-user writes are resolved by the ingestion pipeline that
owns per-field source precedence.

`orgIds` is a convenience for creating memberships in the same call; each
one becomes its own item in the transaction. An organization id that is
neither a known organization nor already referenced by a membership is
rejected. Organizations are never created implicitly.




# Get a product user
Source: https://docs.inflection.io/api-reference/product-users/get-a-product-user

/api-reference/openapi.yaml get /v2/users/{id}
One membership for this product user, carrying the login's fields and
that organization's fields together. A product user in several
organizations has one row per organization; this returns one of them
under a stable order, preferring a row that names an organization, and
reports which one in `orgId`. Use `/v2/contacts/{id}/users` to see all
of them.




# Get a product user by email
Source: https://docs.inflection.io/api-reference/product-users/get-a-product-user-by-email

/api-reference/openapi.yaml get /v2/users/by-email/{email}
`email` is the product user's own address. It is indexed but **not**
unique, so an address shared by two **different** product users is
rejected with **400** rather than picking one -- look those up by id. A
single user belonging to several organizations is not ambiguous and
resolves normally. Returns the same membership shape as
`/v2/users/{id}`.




# Get a product-user write transaction
Source: https://docs.inflection.io/api-reference/product-users/get-a-product-user-write-transaction

/api-reference/openapi.yaml get /v2/users/transactions/{transactionId}
Poll until `status` is `DONE`. Per-item results appear once every item has
been processed and is readable; while `PENDING` only the status and
`createdAt` are returned.




# List a contact's product users
Source: https://docs.inflection.io/api-reference/product-users/list-a-contacts-product-users

/api-reference/openapi.yaml get /v2/contacts/{id}/users
One entry per membership, so a product user in three organizations
appears three times with a different `orgId`. Each entry carries the
login's fields **and** that organization's fields.




# List an organization's product users
Source: https://docs.inflection.io/api-reference/product-users/list-an-organizations-product-users

/api-reference/openapi.yaml get /v2/orgs/{id}/users
One entry per membership, carrying the login's fields and this organization's fields.



# Update a product user
Source: https://docs.inflection.io/api-reference/product-users/update-a-product-user

/api-reference/openapi.yaml patch /v2/users/{id}
Asynchronous, like create. The response is a transaction to poll.
Properties are merged by the ingestion pipeline; the email cannot be
changed here.




# Quickstart
Source: https://docs.inflection.io/api-reference/quickstart

From zero to your first response in two calls.

## 1. Authenticate

Every request carries a bearer token, either a Personal Access Token or an [OAuth access token](/api-reference/authentication), in the `Authorization` header. Reads need `READ` permission.

```bash theme={null}
# Look a contact up by email (remember to URL-encode the @ as %40)
curl https://api.inflection.io/v2/contacts/by-email/jane%40acme.com \
  -H "Authorization: Bearer inf_pat_your_token_here"
```

## 2. Read the response

Success comes back wrapped in a `data` / `meta` envelope. Contact attributes live under `properties`, using **snake\_case** keys.

```json theme={null}
{
  "data": {
    "id": "0001760c4a86bc38a4a60bcceae32540",
    "email": "jane@acme.com",
    "properties": {
      "first_name": "Jane",
      "last_name": "Doe",
      "company_name": "Acme",
      "_source": "CONTACTS_SYNC_API"
    }
  },
  "meta": { "status": "SUCCESS", "timestamp": "2026-07-02T10:00:00Z" }
}
```

<CardGroup>
  <Card title="Authentication" icon="key" href="/api-reference/authentication">
    Tokens, scopes, and what 401 vs 403 mean.
  </Card>

  <Card title="Contacts" icon="address-book" href="/api-reference/contacts/get-a-contact-by-id">
    Read, create, and sync people.
  </Card>
</CardGroup>


# Rate Limits
Source: https://docs.inflection.io/api-reference/rate-limits

No usage caps, just a rate limit of 10 requests per second per workspace.

The Developer API has **no usage limits**: no monthly quotas or total-call caps. What you build against is a rate limit:

* **10 requests per second, per workspace.** Every `/v1` and `/v2` endpoint counts against it, and all of a workspace's credentials (PATs and OAuth apps) share the same budget.

<Info>
  This is an interim limit while we finalize per-endpoint rate limits. We'll update this page when they change.
</Info>

## Going over the limit

Requests beyond the limit are rejected with **429 Too Many Requests**. Back off briefly and retry. Exponential backoff with a little jitter is plenty.

<Tip>
  Pushing a large batch, like seeding contacts or email versions from a big table? Pace the run instead of firing everything at once. Most integration tools have a rate-limit setting, and a few calls that can be made once per run (like checking that a list exists) don't need to be repeated for every row.
</Tip>


# The response envelope
Source: https://docs.inflection.io/api-reference/response-envelope

One predictable shape for every response.

Responses are wrapped in a consistent envelope. `data` holds the payload; `pagination` appears only on paged lists; on failures `errors` is populated and `meta.status` becomes `FAILURE`.

```json theme={null}
{
  "data": /* payload: object or array */,
  "pagination": { "pageNumber": 1, "pageSize": 20, "totalElements": 151, "totalPages": 8 },
  "errors": [ { "errorCode": "...", "message": "...", "detail": "..." } ],
  "meta": { "status": "SUCCESS", "timestamp": "..." }
}
```

<Info>
  Gateway-level auth errors (401 / 403) are the exception: they have **no body at all**. Only errors from the services carry the `errors` envelope.
</Info>


# Email stats rollup
Source: https://docs.inflection.io/api-reference/stats/email-stats-rollup

/api-reference/openapi.yaml get /v2/emails/stats
Counters for many emails in one call. An email reused across journeys is
reported once here, on its own totals. Per-journey stats cannot answer
"how is this email performing" when the caller does not know which
journeys send it.

`data.aggregate` is a single ungrouped query over the **whole** matching
set, so it is **not** the sum of `data.records`. Those cover only the
current page.

It is also **not** the sum of every page. A send that carries two
different templates counts once in `data.aggregate` but once per template
in `data.records`, so summing all pages can exceed the aggregate by a
small margin (1 in 27,613 on our staging data). The aggregate is the
de-duplicated figure; prefer it over adding the rows up.

Emails are matched on **send** activity. An email with opens or clicks
but no send record is not reported, and its engagement is not in the
aggregate either.

At most **one** of `ids`, `folderId` may be given; both is a 400.
Explicit `ids` return a full row of zeros for an email with no activity,
whereas a `folderId`/unfiltered request returns only emails that have
activity. A filter matching more than 1000 emails is a 400
(`RESULT_SET_TOO_LARGE`). Nothing is silently trimmed. That guard cannot
trigger when `ids` is used, since `ids` is itself capped at 50.

An email whose template record no longer exists is still reported when it
has send activity. The sends happened, and the tracking is the record of
them. Those ids are therefore reported here but return 404 from
`GET /v2/emails/{id}/stats`. This is deliberately unlike the journey
rollup, which reports only live journeys.




# Get a journey's stats
Source: https://docs.inflection.io/api-reference/stats/get-a-journeys-stats

/api-reference/openapi.yaml get /v2/journeys/{id}/stats
The thirteen counters for one journey. `since`/`until` bound the **send**
time; omitting both covers all time.




# Get an email's stats
Source: https://docs.inflection.io/api-reference/stats/get-an-emails-stats

/api-reference/openapi.yaml get /v2/emails/{id}/stats
The same thirteen counters as journey stats, aggregated across **every**
journey that sends this email.




# Journey stats rollup
Source: https://docs.inflection.io/api-reference/stats/journey-stats-rollup

/api-reference/openapi.yaml get /v2/journeys/stats
Counters for many journeys in one call, so reporting on 50 journeys is
one request rather than 50.

`data.aggregate` is a single ungrouped query over the **whole** matching
set, so it is **not** the sum of `data.records`. Those cover only the
current page. `pagination.totalElements` counts the whole matching set.

At most **one** of `ids`, `tag`, `folderId` may be given; more than one
is a 400. Explicit `ids` return a full row of zeros for a journey with no
activity, whereas a `tag`/`folderId`/unfiltered request returns only
journeys that have activity. A filter matching more than 1000 journeys is
a 400 (`RESULT_SET_TOO_LARGE`). Nothing is silently trimmed. That guard
cannot trigger when `ids` is used, since `ids` is itself capped at 50.




# Amplitude
Source: https://docs.inflection.io/connections/amplitude

Use Amplitude product activity to build audiences, trigger journeys, and personalize messaging in Inflection.

Amplitude is a product analytics platform that captures user and group behavior across web, mobile, and server applications. The Amplitude integration sends those events to Inflection, so you can use Amplitude product activity to build audiences, trigger journeys, and personalize messaging in Inflection.

This article covers Amplitude as a **source** (Read flow), i.e., events flowing from Amplitude into Inflection. Amplitude as a destination is not yet supported.

## What You'll Receive From Amplitude

Inflection ingests events and user properties that Amplitude pushes through the direct partner integration. **Event names and event properties** become product activities in Inflection, available in the Product Data Explorer. **User properties** sent on `identify` calls map to Inflection user attributes.

## Prerequisites

<Info>
  Before you start, make sure you have:

  * Admin access to your Inflection workspace.
  * Admin access to your Amplitude project and permission to configure destinations in the Amplitude Integration Portal.
</Info>

## Set Up the Amplitude Connection

Follow these steps to connect Amplitude as a source. Inflection generates a unique endpoint URL and API key for your workspace; you paste both into Amplitude's Integration Portal so Amplitude can push events to Inflection.

### Step 1: Open the Amplitude Connection

In Inflection, open the **Connections** sidebar and click **Amplitude**.

<img alt="Connections sidebar in Inflection with Amplitude selected" />

### Step 2: Generate Your API Key

The **Connect Amplitude** modal opens.

1. Review the connection summary.
2. Click **Generate API Key**.
3. Two fields appear:
   * **Inflection Endpoint URL:** the HTTPS endpoint Amplitude will push events to. Click **Copy**.
   * **API Key:** the authentication key Amplitude will use. Click **Copy**. Treat this key as sensitive — anyone with the key can send events to your Inflection workspace.
4. Click **Done** to save the connection.

<img alt="Connect Amplitude modal showing the Inflection endpoint URL and API key" />

### Step 3 Configure the Destination in Amplitude

In Amplitude:

1. Login to Amplitude as admin.

2. Go to **Data** → **Destinations** from the left menu bar.

3. Click **Add Destination** → **Webhook** type (Events and Users)

   <img alt="Amplitude Destinations catalog with the Webhook destination type" />

4. Copy these data points -
   1. Webhook URL: [https://amplitude.webhook.inflection.io/integrations/amplitude/events](https://amplitude.webhook.inflection.io/integrations/amplitude/events)
   2. Add these in Headers as key-value:
      1. AUTHORIZATION: Bearer \<API key from inflection>
      2. X-Inflection-App-Id: **ask Inflection team for this**
      3. Content-Type: application/json

5. Send events:
   1. Define event custom payload - paste this:

      ```javascript theme={null}
      <#setting number_format="0.####">
      {
      "type": "track",
      "messageId": <#if input.uuid??>"${input.uuid}"<#elseif input.insert_id??>"${input.insert_id}"<#else>"amp-${(input.user_id!'unknown')}-${input.event_time}"</#if>,
      "userId": <#if input.user_id??>"${input.user_id}"<#else>null</#if>,
      "eventTime": "${input.event_time}",
      "email": <#if input.user_properties?? && input.user_properties.email??>"${input.user_properties.email}"<#else>null</#if>,
      "eventName": "${input.event_type}",
      "properties": {<#if input.event_properties??><#list input.event_properties?keys as key><#assign value = input.event_properties[key]>"${key}": <#if value?is_number || value?is_boolean>${value}<#else>"${value}"</#if><#if key_has_next>,</#if></#list></#if>},
      "userProperties": {<#if input.user_properties??><#list input.user_properties?keys as key><#assign value = input.user_properties[key]>"${key}": <#if value?is_number || value?is_boolean>${value}<#else>"${value}"</#if><#if key_has_next>,</#if></#list></#if>},
      "orgIds": <#if parameters.groupTypeKey?has_content && input.groups?? && input.groups[parameters.groupTypeKey]??><#if input.groups[parameters.groupTypeKey]?is_sequence>[<#list input.groups[parameters.groupTypeKey] as v>"${v}"<#sep>,</#sep></#list>]<#else>["${input.groups[parameters.groupTypeKey]}"]</#if><#else>[]</#if>,
      "sessionId": <#if input.session_id??><#if input.session_id?is_number>${input.session_id?c}<#else>"${input.session_id}"</#if><#else>null</#if>,
      "deviceId": <#if input.device_id??>"${input.device_id}"<#else>null</#if>,
      "platform": <#if input.platform??>"${input.platform}"<#else>null</#if>,
      "osName": <#if input.os_name??>"${input.os_name}"<#else>null</#if>,
      "country": <#if input.country??>"${input.country}"<#else>null</#if>,
      "region": <#if input.region??>"${input.region}"<#else>null</#if>,
      "city": <#if input.city??>"${input.city}"<#else>null</#if>,
      "language": <#if input.language??>"${input.language}"<#else>null</#if>,
      "appVersion": <#if input.version_name??>"${input.version_name}"<#else>null</#if>,
      "revenue": <#if input.revenue??><#if input.revenue?is_number>${input.revenue?c}<#else>"${input.revenue}"</#if><#else>null</#if>,
      "revenueType": <#if input.revenue_type??>"${input.revenue_type}"<#else>null</#if>,
      "productId": <#if input.product_id??>"${input.product_id}"<#else>null</#if>,
      "insertId": <#if input.insert_id??>"${input.insert_id}"<#else>null</#if>,
      "library": <#if input.library??>"${input.library}"<#else>null</#if>,
      "osVersion": <#if input.os_version??>"${input.os_version}"<#else>null</#if>,
      "deviceBrand": <#if input.device_brand??>"${input.device_brand}"<#else>null</#if>,
      "deviceModel": <#if input.device_model??>"${input.device_model}"<#else>null</#if>,
      "deviceType": <#if input.device_type??>"${input.device_type}"<#else>null</#if>,
      "ipAddress": <#if input.ip_address??>"${input.ip_address}"<#else>null</#if>,
      "dma": <#if input.dma??>"${input.dma}"<#else>null</#if>,
      "amplitudeUserId": <#if input.amplitude_id??><#if input.amplitude_id?is_number>${input.amplitude_id?c}<#else>"${input.amplitude_id}"</#if><#else>null</#if>
      }
      ```

6. Enable the events you want to forward to Inflection.

   <img alt="Amplitude webhook destination event forwarding toggle" />

7. Send users:
   1. Define user custom payload - paste this:

      ```javascript theme={null}
      <#setting number_format="0.####">
      <#function js v>
        <#if v?is_boolean || v?is_number><#return v?c>
        <#elseif v?is_string><#return '"' + v?json_string + '"'>
        <#elseif v?is_sequence><#local items = []><#list v as it><#local items = items + [js(it)]></#list><#return '[' + items?join(',') + ']'>
        <#elseif v?is_hash_ex><#local entries = []><#list v?keys as k><#local entries = entries + ['"' + k?json_string + '":' + js(v[k])]></#list><#return '{' + entries?join(',') + '}'>
        <#else><#return 'null'>
        </#if>
      </#function>
      {
        "type": "identify",
        "messageId": <#if input.uuid??>${js(input.uuid)}<#elseif input.insert_id??>${js(input.insert_id)}<#else>${js("amp-id-" + (input.user_id!'unknown') + "-" + (input.event_time!'unknown'))}</#if>,
        "userId": <#if input.user_id??>${js(input.user_id)}<#else>null</#if>,
        "eventTime": <#if input.event_time??>${js(input.event_time)}<#else>null</#if>,
        "email": <#if input.user_properties?? && input.user_properties.email??>${js(input.user_properties.email)}<#else>null</#if>,
        "userProperties": <#if input.user_properties??>${js(input.user_properties)}<#else>{}</#if>,
        "sessionId": <#if input.session_id??>${js(input.session_id)}<#else>null</#if>,
        "deviceId": <#if input.device_id??>${js(input.device_id)}<#else>null</#if>,
        "platform": <#if input.platform??>${js(input.platform)}<#else>null</#if>,
        "country": <#if input.country??>${js(input.country)}<#else>null</#if>,
        "language": <#if input.language??>${js(input.language)}<#else>null</#if>,
        "appVersion": <#if input.version_name??>${js(input.version_name)}<#else>null</#if>,
        "library": <#if input.library??>${js(input.library)}<#else>null</#if>,
        "osVersion": <#if input.os_version??>${js(input.os_version)}<#else>null</#if>,
        "ipAddress": <#if input.ip_address??>${js(input.ip_address)}<#else>null</#if>,
        "amplitudeUserId": <#if input.amplitude_id??>${js(input.amplitude_id)}<#else>null</#if>
      }
      ```

8. Enable the users you want to forward to Inflection.

   <img alt="Amplitude webhook destination user forwarding toggle" />

9. Activate the webhook status and click Save.

   <img alt="Amplitude webhook destination status toggle and Save button" />

10. Verify the connection with test data

    <img alt="Amplitude webhook test panel for verifying the connection with test data" />

11. After this, Amplitude will begin pushing events to Inflection within a few minutes.

## Sync Group Properties From Amplitude

In Amplitude, a **group** represents an account or workspace that your users belong to (for example, an organization). Group properties such as ARR, plan, seat count, and renewal date are shared by every user in the group. Inflection syncs these as org (workspace) attributes, so you can build account-based audiences and personalize on account-level data alongside each contact's own activity.

Unlike events and user properties, which arrive in near real time through the webhook, group properties are pulled on a schedule through Amplitude's Export API. Configure this in the **Group Properties** section of the Amplitude connection.

<Info>
  Group property sync is configured separately from the webhook and needs its own credentials: an Amplitude **API Key**, **Secret Key**, and the **Group Profile Name** to sync.
</Info>

### Step 1: Generate an Amplitude API Key and Secret Key

In Amplitude:

1. Click **Settings** in the left navigation.
2. Scroll to **API Keys**.
3. On the **API Key** tab, generate an API key.
4. Open the **Secret Key** tab and copy the secret key. The secret key is shared across the Amplitude project.
5. Keep both values handy - you will paste them into Inflection.

<img alt="Generate a new API key in Amplitude under Settings and API Keys" />

### Step 2: Find Your Group Profile Name

Group properties in Amplitude live under group profiles.

1. In Amplitude, open the **Group Profiles** tab.
2. Note the profile name you want to sync - this is the tab name shown for the group (for example, `org_group`). You will enter this exact value in Inflection.

<Info>
  Most workspaces use a single group profile, such as organization. If you maintain more than one, sync the profile that holds the account attributes you want to use in Inflection.
</Info>

<img alt="Amplitude Group Profiles tab showing the available group profile names" />

### Step 3: Add Group Properties to the Inflection Connection

In Inflection, in the Amplitude connection, find the **Group Properties** section and enter:

1. **API Key:** the Amplitude API key from Step 1.
2. **Secret Key:** the Amplitude secret key from Step 1.
3. **Group Profile Name:** the profile name from Step 2 (for example, `org_group`).

Save the connection. Inflection begins pulling group properties on the next Export API sync.

<Info>
  When you edit an existing connection, you can update these values, but the saved API key and secret key are hidden for security.
</Info>

<img alt="Group properties section of the Amplitude connection in Inflection" />

### How Group Properties Sync

Group property sync runs on a schedule, not in real time. Two things must happen before a group property change appears in Inflection:

* **A sync cycle runs.** Inflection calls Amplitude's Export API approximately every one to two hours.
* **A user in the group fires an event.** Amplitude attaches group properties to user activity, so a contact in the group must fire at least one product activity event during the cycle for the latest group properties to be picked up.

Because of this, expect group properties to update with a delay of up to a couple of hours, and only for groups whose users are active. User properties, by contrast, sync in near real time through the webhook.

### Where Group Properties Appear in Inflection

Synced group properties appear as org attributes on the Product User. Open a contact who belongs to an Amplitude group to see the group's properties (for example, ARR, plan, and active status) by clicking on the **Org id**. A contact who belongs to more than one group shows the properties for each group.

<img alt="Org details modal on the Product User tab showing synced Amplitude group properties" />

## Sync Group Properties From Amplitude

In Amplitude, a **group** represents an account or workspace that your users belong to (for example, an organization). Group properties such as ARR, plan, seat count, and renewal date are shared by every user in the group. Inflection syncs these as org (workspace) attributes, so you can build account-based audiences and personalize on account-level data alongside each contact's own activity.

Unlike events and user properties, which arrive in near real time through the webhook, group properties are pulled on a schedule through Amplitude's Export API. Configure this in the **Group Properties** section of the Amplitude connection.

<Info>
  Group property sync is configured separately from the webhook and needs its own credentials: an Amplitude **API Key**, **Secret Key**, and the **Group Profile Name** to sync.
</Info>

### Step 1: Generate an Amplitude API Key and Secret Key

In Amplitude:

1. Click **Settings** in the left navigation.
2. Scroll to **API Keys**.
3. On the **API Key** tab, generate an API key.
4. Open the **Secret Key** tab and copy the secret key. The secret key is shared across the Amplitude project.
5. Keep both values handy — you will paste them into Inflection.

<img alt="Generate a new API key in Amplitude under Settings and API Keys" />

### Step 2: Find Your Group Profile Name

Group properties in Amplitude live under group profiles.

1. In Amplitude, open the **Group Profiles** tab.
2. Note the profile name you want to sync — this is the tab name shown for the group (for example, `org_group`). You will enter this exact value in Inflection.

<Info>
  Most workspaces use a single group profile, such as organization. If you maintain more than one, sync the profile that holds the account attributes you want to use in Inflection.
</Info>

<img alt="Amplitude Group Profiles tab showing the available group profile names" />

### Step 3: Add Group Properties to the Inflection Connection

In Inflection, in the Amplitude connection, find the **Group Properties** section and enter:

1. **API Key:** the Amplitude API key from Step 1.
2. **Secret Key:** the Amplitude secret key from Step 1.
3. **Group Profile Name:** the profile name from Step 2 (for example, `org_group`).

Save the connection. Inflection begins pulling group properties on the next Export API sync.

<Info>
  When you edit an existing connection, you can update these values, but the saved API key and secret key are hidden for security.
</Info>

<img alt="Group properties section of the Amplitude connection in Inflection" />

### How Group Properties Sync

Group property sync runs on a schedule, not in real time. Two things must happen before a group property change appears in Inflection:

* **A sync cycle runs.** Inflection calls Amplitude's Export API approximately every one to two hours.
* **A user in the group fires an event.** Amplitude attaches group properties to user activity, so a contact in the group must fire at least one product activity event during the cycle for the latest group properties to be picked up.

Because of this, expect group properties to update with a delay of up to a couple of hours, and only for groups whose users are active. User properties, by contrast, sync in near real time through the webhook.

### Where Group Properties Appear in Inflection

Synced group properties appear as org attributes on the Product User. Open a contact who belongs to an Amplitude group to see the group's properties (for example, ARR, plan, and active status) by clicking on the **Org id**. A contact who belongs to more than one group shows the properties for each group.

<img alt="Org details modal on the Product User tab showing synced Amplitude group properties" />

## Manage the Connection

Once connected, the **Amplitude** entry in the Connections sidebar opens the Amplitude Connection Details page. The page has two tabs.

### Connection Details Tab

The Connection Details tab shows:

* A connection status badge **Connected** or **Disconnected**.
* The **Inflection API Key** in masked form with a **Copy** button.
* A **Refresh API Key** button.

<img alt="Amplitude Connection Details tab with status badge, masked API key, and Refresh API Key button" />

### Refresh Your API Key

Refresh the API key if you suspect it has been exposed or want to rotate credentials.

1. On the Connection Details tab, click **Refresh API Key**.
2. Read the confirmation dialog: refreshing the key immediately deactivates the existing key.
3. Click **Confirm** to generate a new key.
4. Copy the new key and update it in Amplitude's Integration Portal. Event flow resumes once Amplitude is using the new key.

## Monitor Sync Activity

Use the **Sync Activity** tab on the Amplitude Connection Details page to monitor incoming events and troubleshoot delivery issues.

The tab shows:

* A **time range selector** — 24 hours, 30 days, 60 days, or 90 days.
* A **line chart** plotting **Events Received** and **Errors** over the selected range.
* An **error list** below the chart with columns for **Timestamp**, **Event Name**, **Error Type**, and **Description**. Expand a row to see the full event payload.

<img alt="Sync Activity tab with events chart and error list" />

## Find Amplitude Events in the Product Data Explorer

Open **Connections** > **Product Data Explorer** to see every event that has reached Inflection across all connected sources, including Amplitude.

* The **Source** column at the top of the table lets you narrow the list to **Amplitude**, **Segment**, or **All Sources**.
* The **Source** column on each row shows the originating source for that event.
* Use the toggle on each row to enable an event for use in audiences, journeys, and personalization.

<img alt="Product Data Explorer filtered by source showing Amplitude events" />

Click an event name to open its detail page. The detail page shows:

* **Event Name** and **Source**.
* An editable **Description**.
* A **Status** toggle for enabling or disabling the event.
* A **Properties** table listing each property with its **Data Type**, **Description**, and **Sample Preview**.

<img alt="Event detail page with description, status toggle, and properties table" />

## Use Amplitude Data in Campaigns and Journeys

Once events are enabled and properties are mapped, Amplitude data is available everywhere product data is used in Inflection — no additional configuration is needed:

* **Dynamic lists and audiences:** filter on Amplitude event names, event counts, and mapped user properties.
* **Journey batch triggers and exit criteria:** Trigger journeys on Amplitude events or use them as exit conditions.
* **Contact profile:** Amplitude events appear in the product activity timeline alongside events from other sources.
* **Personalization tokens:** mapped Amplitude user properties can be used as tokens in email and other channels.

## Common Use Cases

* **Onboarding journeys driven by product behavior.** Trigger a welcome series when a user fires the `account_created` event in Amplitude, then branch based on whether they fire `first_value_milestone` within seven days.
* **Re-engagement based on activity gaps.** Build a dynamic list of users who have not fired any Amplitude event in the last 30 days and enroll them in a winback campaign.
* **Feature adoption nudges.** Target users who have fired the `feature_x_viewed` event but not `feature_x_used` within 14 days.
* **Cross-source segmentation.** Combine Amplitude product activity with attributes from your other connected sources (for example, Salesforce account stage) in a single audience.

## Amplitude Connection FAQ

<AccordionGroup>
  <Accordion title="Can I send events from Inflection to Amplitude (Amplitude as a destination)?">
    The current feature covers Amplitude as a source only - events flow from Amplitude into Inflection. Sending Inflection marketing activities to Amplitude is not supported yet.
  </Accordion>

  <Accordion title="What happens if I refresh my API key?">
    The previous key is deactivated immediately and Amplitude stops being able to push events until you save the new key in the Amplitude Integration Portal. Plan key rotations during low-traffic windows to minimize the event gap.
  </Accordion>

  <Accordion title="Where do I troubleshoot if events are not arriving?">
    Check the **Sync Activity** tab on the Amplitude Connection Details page. The error list shows the most recent ingestion errors with the event name, error type, and description. If you see no events at all in the chart, verify the endpoint URL and API key in Amplitude's Integration Portal match the values shown in Inflection.
  </Accordion>
</AccordionGroup>


# Common Connections & Use Cases
Source: https://docs.inflection.io/connections/common-connections-use-cases

How data from Sales, Product, and Marketing come together to power personalization at scale.

Inflection brings together data from Product, Marketing, and Sales to create a fully-contexed, 360-degree view of a prospect or customer. This enables marketers to target and personalize across their product and account-based data. (Learn about setting up and configuring integrations at our help center.)

<AccordionGroup>
  <Accordion title="Sales data (CRM)">
    Inflection natively integrates with Salesforce.

    ### Objects & fields

    Inflection integrates with Salesforce Leads, Contacts, Campaign Members, Campaigns, and Accounts.

    | Summary | **Read** | **Write** | **Create** |
    | - | - | - | - |
    | **Leads** | ✅ | ✅ | ✅ |
    | **Contacts** | ✅ | ✅ | ✅ |
    | **Campaign Members** | ✅ | ✅ | ✅ |
    | **Campaigns** | ✅ | | |
    | **Accounts** | ✅ | | |
    | **Opportunities** | ✅ | | |

    Inflection does not interact with Activities or Custom Objects at this time.

    ### Common Use Cases

    #### Leads and contacts

    * When a marketing contact is created in Inflection, nurture and score the contact until it is ready for Sales follow-up; then, create a lead in Salesforce.
    * Update score, status, lifecycle (etc.) fields in either system and see updates reflected in the other in near real-time.
    * When an Inflection contact is identified as a key contact on a target account (through Inflection Contact-to-Account matching), create as a contact in Salesforce.

    #### Campaigns and campaign members

    * When an Inflection contact submits a Sales or campaign form, add them to the appropriate Salesforce campaign for reporting and attribution.
    * Use Salesforce campaigns and statuses to track event registration, attendance, and other statuses.
    * Target Inflection contacts based on campaign membership and status.

    #### Accounts

    * Trigger and/or dynamically populate emails based on account attributes like rep and renewal date.
    * With Inflection Contact-to-Account matching, apply account-based segmentation *before* the Inflection contact has been created in Salesforce.
    * Target Inflection contacts based on activity or attributes of other members of the account. e.g., Target executives at an account where at least one member has an active free trial.

    #### Opportunities

    * Suppress contacts at accounts with active deals to keep marketing aligned with sales during negotiations (e.g., exclude renewal nurtures while Stage is Discovery, Negotiation, or Proposal Sent).
    * Run executive nurtures keyed to deal size: target CFOs at accounts with Opportunities above a threshold amount.
    * Segment audiences by deal stage: education sequences for Discovery-stage contacts, deal-acceleration content for Negotiation, expansion offers for Closed Won.
    * Surface deal context on every contact and account profile so marketers know which accounts are mid-deal before reaching out.

    ### Sync & monitoring

    Inflection is built for enterprise PLG companies that have high-volume, high-velocity data feeds. At this time, there is no limit to the volume of data Inflection can house or sync.

    Salesforce API limits can be configured and sync health can be monitored from Inflection.

    The scope of leads/contacts that sync between Inflection and Salesforce can be configured via the integration user’s permission set in Salesforce, and/or in Inflection. Learn more about configuring the [Inflection\<>Salesforce integration](/connections/salesforce).
  </Accordion>

  <Accordion title="Product data (CDP/DWH)">
    Inflection natively integrates with Big Query, Databricks, Redshift, Segment.io, and Snowflake, with more on the way. We are constantly expanding the providers we support.

    Inflection natively supports the following tables/views.

    | Tables | **Read** | **Write** |
    | - | - | - |
    | Product Activities | ✅ | |
    | Product Users | ✅ | |
    | Product Workspaces | ✅ | |
    | Journey Activities | | ✅ |

    ### Common Use Cases

    #### Product Activities

    Think of the product activity table as a receipt of every tracked action (commonly called events) each user takes in your product. Inflection ingests an unabridged feed of the events you choose, complete with event properties.

    * Understand which onboarding milestones a new user has reached, and which they have left to complete. Personalize an onboarding nurture to only message around the next-best action (milestone) for each user.
    * Detect when a free plan user shows signs that they are ready to upgrade (i.e., they are trying to use a paid-only feature). Send a timely nudge to the user to upgrade.
    * Send abandoned-cart messaging to users who view the pricing page but do not upgrade.

    [Read how Formstack jacked up their expansion revenue with product-informed campaigns.](https://www.inflection.io/post/how-formstack-ditched-legacy-marketing-automation-for-inflection-io)

    #### Product Users

    For many product-led companies, it is common that their customers participate in multiple product workspaces; therefore one customer can have many users. Inflection supports the many-to-many relationship between users and workspaces.

    Inflection can distinguish between, segment, and personalize to a person who is an admin in a free trial workspace **and** a member in a paid workspace.

    * Send a personalized message to admins regarding their account, with deep links to features within their workspace, and workspace details like plan or billing details.
    * Identify users who have downgraded from a paid workspace but are still active in a free workspace; offer targeted win-back campaigns.
    * Identify users in free workspaces who belong to accounts where a paid workspace is already available; nudge the free user to join the paid workspace (growing upsell potential for the existing customer).

    #### Product Workspaces

    Workspaces, also called orgs, typically include attributes like plan. This is information about the workspace that multiple users can share.

    * Trigger account-wide upgrade or renewal campaigns based on workspace plan type, billing cycle, or trial expiration.
    * Identify workspaces with high user activity but limited seat usage and promote expansion offers.
    * Deliver account-specific messages (like onboarding guides, feature highlights, or renewal tips from the AE or CSM) to members of enterprise workspaces.

    #### Journey Activities

    Inflection writes journey activities back to CDP/Data Warehouses in order to power reporting, insights, and attribution in our customers’ analytics environment. These activities include email events (open, click, bounce, unsubscribe), form and webhook submissions, and journey lifecycle events (journey entered, journey completed, journey exited) (read more in the set-up doc).

    * Correlate email engagement with in-product activity to understand which messages drive feature adoption.
    * Attribute upgrades and expansion revenue to specific campaigns or nurture sequences by joining journey events with conversion data.
    * Create dashboards in your BI tool to visualize the full funnel from email send to product milestone completion to paid conversion.
    * Report on journey-level performance: entries, completions, and early exits alongside email engagement to see where contacts drop out of a nurture.

    Learn more about configuring [data warehouse](/connections/import-from-data-warehouse) or [CDP](/connections/segment) integrations with Inflection.
  </Accordion>

  <Accordion title="Web data">
    Inflection's web tracking captures anonymous and identified visitor behavior across your marketing website, documentation, pricing pages, and other digital properties. This behavioral data enriches your customer profiles and enables precise targeting based on demonstrated interest and intent signals.

    ### Web tracking data

    Inflection natively supports web tracking through a lightweight JavaScript snippet that captures page views, form submissions, and link clicks.

    | Event Type | **Track** | **Properties** | **Identity Resolution** |
    | - | - | - | - |
    | **Page Views** | ✅ | URL, title, referrer, timestamp | ✅ |
    | **Form Submissions** | ✅ | Form ID, field values, page context | ✅ |
    | **Link Clicks** | ✅ | Link URL, text, destination, context | ✅ |

    Inflection automatically captures UTM parameters, device type, browser, and geographic information with every event.

    ### Common Use Cases

    #### Page views

    Page view tracking reveals what content prospects engage with before and after they convert, providing critical context for personalization and lead scoring.

    * Identify prospects who visit high-intent pages like pricing, security, or enterprise features multiple times; score them and trigger sales alerts.
    * Segment contacts based on content theme engagement (e.g., "visited 3+ integration-related pages") to deliver targeted campaign messaging about your integration capabilities.
    * Detect when a prospect returns to your website after going dark; automatically re-engage them with content related to pages they previously viewed.

    #### Form submissions

    Form submissions are high-value conversion events that signal explicit interest. Inflection captures both the fact that a form was submitted and the data entered.

    * When a prospect submits a demo request form, immediately route to sales and trigger a personalized nurture sequence that references their specific use case or pain point mentioned in the form.
    * Track which content downloads (whitepapers, case studies, templates) each contact has requested; use this to understand their role, priorities, and stage in the buying journey.
    * Identify contacts who submit multiple forms across different topic areas; flag them as high-intent and enable multi-threading sales outreach.

    #### Link clicks

    Link click tracking reveals micro-commitments and specific areas of interest, especially valuable for content embedded in your website.

    * Track clicks on "Book a Demo" or "Contact Sales" CTAs even when they don't result in form submissions; these are strong intent signals worth scoring or alerting on.
    * Monitor clicks on integration or feature pages to understand technology stack and feature priorities; personalize follow-up content accordingly.
    * Track social proof interactions like clicks on customer logos, awards, or analyst reports; use this to gauge trust-building progress.

    ### Identity resolution & enrichment

    Inflection automatically resolves anonymous web visitors to known contacts when they identify themselves through form submissions or email link clicks. This creates a complete behavioral timeline from first anonymous visit through customer journey.

    This means new contact records will enrich with historical web behavior data automatically upon identification.

    Learn more about setting up web tracking with Inflection: [Web Tracking](/connections/web-tracking).
  </Accordion>
</AccordionGroup>


# Custom Forms
Source: https://docs.inflection.io/connections/custom-forms

Collect prospect or customer responses using Inflection's forms API.

Inflection lets you ingest data from any third-party form tool that supports outbound webhooks. With a custom form connection, you receive data in JSON format and use it to update contact properties or filter audiences inside journeys. You can secure each connection with different authentication methods.

<Info>
  **Key concepts:**

  * **Form provider**: The external tool you're using to collect submissions (e.g., Typeform, Jotform).
  * **Custom form connection**: The authenticated webhook connection between Inflection and your form provider.
  * **Group**: A subset of submissions within a connection, split by a field you choose - used to separate submissions from multiple forms on one connection.
</Info>

## Step 1: Set Up a Custom Form Connection

A custom form connection uses the **same two-step flow as inbound webhooks**: **Endpoint setup** → **Map fields**, finishing with **Continue to map fields** and then **Finish setup**.

1. Navigate to **Forms** in the main sidebar (Forms is now a top-level item - see [Inflection Forms](/connections/inflection-forms#create-a-form)).
2. Click **New Form** and, in the **Create form** drawer, choose **Custom form connection**.
3. On the **Endpoint setup** step, enter a connection name (required), authentication, an optional description, and the create-contact option, then click **Continue to map fields**.
4. On the **Map fields** step, copy the **Webhook URL** into your form provider, then submit a sample payload and map the detected fields.

<img alt="The full-page Custom form connection flow on the Endpoint setup step, with the Endpoint setup and Map fields step indicator" />

The sample-payload submission, the field-mapping table, and grouping all work exactly as they do for inbound webhooks - see [Step 2: Map Fields and Group Submissions](#step-2-map-fields-and-group-submissions) below for the full walkthrough.

### Connection Detail Page

A custom form connection opens as a single scrolling page, the same as an inbound webhook connection.

At the top are two badges:

* A **lifecycle** badge (see [Lifecycle actions](#lifecycle-actions)).
* A **readiness** badge showing how far along the connection is: **Setup incomplete**, **Mapping needed**, **Ready**, or **New fields found**.

Below the badges, a stat strip shows four tiles: **Submissions**, **Groups**, **Errors**, and **Grouped By**.

The rest of the page includes:

* **Connection Details** card - lists Type, Create Contact, Last Activity, Authentication, Date Created, and **Processing Lane** (Real-time or Bulk - controls which ingestion lane this connection uses; see [Processing Lanes](#processing-lanes)). For a custom form connection, **Type** reads **Form API**.
* **Endpoint URL** - with a copy control.
* **Connection Health** - includes a **View submission errors** action.
* **Groups table** - columns **Group**, **Submissions**, **Errors**, and actions, plus a **Refresh** control. Connected form assets appear as rows here.

Submission errors surface under **Connection Health** - use **View submission errors** to review them.

### Authentication

Select the authentication option that matches your security requirements. Using No Auth can expose your webhook to spam and malicious data — Basic Auth or API Key is strongly recommended.

**No Auth**

No authentication. Anyone with the webhook URL can send data.

<Info>
  Not recommended. Risk of spam or malicious data.
</Info>

**Basic Auth**

Uses a username and password combination.

* Credentials are hidden after setup. Copy and store them securely.
* To reset: Click **Reset Password** from the connection page and enter a new password. Update the password in your third-party system.

**API Key**

An API key is automatically generated.

* Configure in your form provider using **one** of the following methods:
  * **Option 1 — Custom Header**: Key: `Authorization` / Value: `Bearer <YOUR_API_KEY>`
  * **Option 2 — Bearer Token**: Paste the API key directly into the "Token" or "Authorization" field in your integration settings.
* To reset: Click **Refresh API Key** under Authentication Details. Update the API key in your third-party system.

<Info>
  Credentials are hidden after setup. If you reset credentials, update your third-party system immediately. The webhook URL remains unchanged. Once the connection is created, the authentication method cannot be changed.
</Info>

### Lifecycle Actions

A custom form connection uses the same lifecycle actions as an inbound webhook. The **lifecycle** badge shows the connection's current state - a connection is **Active** while it is processing incoming data. Use the lifecycle actions to control that:

* **Pause** - Confirmation reads "Pausing stops incoming data processing until this connection is resumed." The confirm button is **Pause sync**. While paused, incoming POSTs are **rejected, not queued**.
* **Resume** - Sets a paused connection back to **Active**. Applies immediately, with no confirmation dialog.
* **Disable** - Confirmation reads "Once disabled, this connection will no longer process incoming data." Once disabled, a connection **cannot be self-resumed**.

<Info>
  Lifecycle actions and editing are available to **Admins** and **Editors**. They're hidden from **Viewers**.
</Info>

## Step 2: Map Fields and Group Submissions

Field mapping happens on the **Map fields** step of the two-step flow, not as a separate enable step.

<img alt="The Map fields step showing the Webhook URL, sample payload, grouping control, and field-mapping table" />

1. Copy the endpoint from the **Webhook URL** block using its copy control, then configure it (with any credentials) in your form provider.
2. In the **Payload** textarea, either paste your own JSON or use the sample that's prefilled for you. The helper text reads "Use the sample payload or paste your own JSON." If the JSON is invalid, you'll see **Enter a valid JSON object before submitting.**
3. Click **Submit sample payload**. On success you'll see **Payload received. Fields are ready to map.** and the detected fields populate the mapping table.

<Info>
  Nested JSON objects arrive **flattened** using dot notation. For example, `{"props": {"company": "Acme"}}` appears as the field `props.company`.
</Info>

The field-mapping table lists every field detected in your payload. It has four columns:

| Column | What it shows |
| - | - |
| **Payload field** | The field name from your JSON (dot notation for nested fields). |
| **Sample Preview** | The example value from the submitted payload. |
| **Contact field** | The contact property this field maps to. Unmapped rows show **None (Unmapped)**. |
| **Mapping rule** | How the value is applied: **Always overwrite** or **Update if empty**. |

You must map the **Email** contact field before you can continue. If it isn't mapped, you'll see **Map the Email contact field before continuing.**

Click **Save mapping** to persist your mapping.

### Group Submissions

To split submissions from multiple forms on one connection, group them by a field in the payload:

* Use the **Group submissions by field (optional)** control to pick the grouping field.
* The **How it works** link opens a **How grouping works** explainer.

<img alt="The How grouping works explainer opened from the How it works link on the Map fields step" />

<Warning>
  The grouping field is permanent. Once you set a grouping field and click **Finish setup**, it is locked for the life of the connection. If you reopen the setting later, it appears disabled with a lock icon and the text "Grouping is set once for a connection and can't be changed afterwards." Choose your grouping field carefully before finishing setup.
</Warning>

## Review Submission Errors

Submission errors surface under **Connection Health** on the connection detail page - click **View submission errors** to review them. Common errors and fixes:

* **"No valid email present in submission"** → Ensure the email field is mapped.
* **"Obtained email is not valid"** → Verify the correct email format is being sent.
* **"Mapping failed due to date format error"** → Check date format compatibility between your form tool and the contact property.

## Processing Lanes

Every custom form connection is assigned to a **processing lane** - either **Real-time** or **Bulk**. Processing lanes isolate your webhook traffic so that high-volume submissions on one connection don't slow down another.

<Info>
  **How processing lanes work**

  * Each customer gets **two separate lanes** for processing webhook data. One connection's traffic cannot congest the other lane.
  * **There is no difference in processing speed between the two lanes.** Both Real-time and Bulk process submissions at the same rate. The names refer to the intended use case, not to a speed difference.
  * Use **Real-time** for connections where speed-to-lead matters (for example, demo-request forms or high-priority lead sources).
  * Use **Bulk** for high-volume, batch-style data imports where you want to keep the traffic separate from your real-time connections.
</Info>

### Default Assignments

Existing connections are automatically assigned a default lane:

| Connection type | Default lane |
| - | - |
| Inbound webhook connections | Bulk |
| Custom form connections | Real-time |

You can change a connection's lane at any time from the **Connection Details** card on the connection detail page.

### Changing a Connection's Lane

1. Open the connection's detail page and open its settings for editing.
2. Under **Processing lane**, select one of the two options:
   * **Real-time** - recommended for form submissions and low-to-moderate volume.
   * **Bulk** - recommended for automations and high-volume sources.
3. Click **Save**.

<img alt="The Processing lane selector on the connection settings form, with Real-time and Bulk options and their recommended use descriptions" />

The change takes effect immediately for new incoming submissions.

## Using Form Submissions in Journeys

You can use custom form submissions within **Journeys** for automated follow-up.

1. Navigate to **Journeys → Create New Journey** (or open an existing journey).
2. Add an entry condition: **Performed a Marketing Activity → Submitted a form**.
3. Select the specific form asset to trigger the journey.

You can also use form submissions in **Branch by Filter** to tailor communications based on specific field values submitted.

Every data sync event is recorded under the **Marketing Activity** tab for each contact. You can also filter contacts in **Dynamic Lists** using form submission data by applying conditions based on specific form fields.

## Supported Form Providers

Inflection's API / Custom Forms approach works with any tool that can POST JSON to a webhook URL. Below are step-by-step guides for Webflow and Formstack, followed by links for other supported providers.

Both Webflow and Formstack start from the **Create form** drawer (**New Form → Webflow form** or **Formstack form**). Step 1 shows the provider webhook URL with a copy control, then a **Submission test** step you can **skip**. You can **Disconnect** a provider at any time from its connection page.

### Connecting Webflow Forms

1. In the **Create form** drawer, choose **Webflow form**.
2. Copy the shown provider webhook URL and go to your Webflow site builder.
3. In your Webflow dashboard, go to **Site Settings → Apps & Integrations → Webhooks**. Click **Add Webhook**. Set the configuration as shown and paste the copied link into the **Webhook URL** field.

<Info>
  Inflection only supports **API V1** for Webflow.
</Info>

4. Return to Inflection to reach the **Submission test** step. Submit a test form to verify the setup (recommended), or skip this step.
5. Submissions from your Webflow forms will now appear in Inflection.

<Info>
  A Webflow form's name is not editable in Inflection - the field shows the tooltip "Webflow form name is not updatable".
</Info>

### Connecting Formstack Forms

1. In the **Create form** drawer, choose **Formstack form**.
2. Copy both the **webhook link** and the **shared secret key** shown in Inflection (Formstack requires the shared secret in addition to the URL), then go to your Formstack form builder.
3. In Formstack, open your form and go to **Form Settings → Emails & Actions → Advanced Settings → Add a Webhook**. Click **Add a Webhook** and configure as follows:
   * **Webhook URL**: Paste the link copied from Inflection.
   * **Shared Secret**: Paste the secret key copied from Inflection.
   * Leave all other settings exactly as shown in the Formstack webhook configuration screen.

<Info>
  Ensure that the Webhook settings are configured exactly as shown above.
</Info>

4. Return to Inflection to reach the **Submission test** step. Provide a test submission to verify the setup (recommended), or skip this step.
5. Submissions from your Formstack forms will now appear in Inflection.

### Other Commonly Used Providers

Inflection works with any form tool that supports outbound webhooks posting JSON. External setup guides:

* [Typeform](https://www.typeform.com/developers/webhooks/)
* [Jotform](https://www.jotform.com/integrations/webhooks)
* [Formsite](https://support.formsite.com/hc/en-us/articles/360000546194-Webhooks)
* [SurveyMonkey](https://help.surveymonkey.com/en/apply/build/webhook-overview/)
* [Feathery.io](http://Feathery.io)
* [Fillout](https://www.fillout.com/help/webhook)
* [Zoho Forms](https://help.zoho.com/portal/en/kb/forms/integrations/webhooks/articles/webhook-configuration)
* [Form.io](http://Form.io)
* [QuestionScout](https://support.questionscout.com/article/26-webhooks)
* [Paperform](https://paperform.co/help/articles/how-to-use-webhooks/)

## Custom Forms FAQs

<AccordionGroup>
  <Accordion title="Why is my custom form connection on the Real-time lane by default?">
    Custom form connections default to **Real-time** because form submissions - like demo requests or event registrations - are typically time-sensitive and benefit from isolated, priority processing. If your form handles high-volume batch imports instead, you can switch it to **Bulk** from the **Connection Details** card. Both lanes process data at the same speed; the separation ensures one connection's traffic doesn't affect the other.
  </Accordion>
</AccordionGroup>


# Export to Data Warehouse
Source: https://docs.inflection.io/connections/export-to-data-warehouse

Export raw data to your data warehouse to support marketing analytics.

Exporting marketing data from Inflection to your data warehouse enables your marketing, operations, and data teams to build custom reports and run analytics in their BI tools. Track email engagement, journey performance, and form submissions alongside your product and revenue data for comprehensive growth insight

## Data You Can Export

Inflection allows you to export marketing data (email events, journey activity, and form & inbound webhook submissions) directly to your data warehouse. This makes it easier for your marketing, ops, and data teams to create reports and run analytics in their BI tools.

The events and attributes are supported:

| Event Type | Events | Attributes |
| - | - | - |
| Email | Processed<br />Sent<br />Open<br />Clicked<br />Bounced<br />Spam<br />Unsubscribe<br />Delivered | • Contact: `Inflection Contact ID`, `Contact Email`<br />• Email Asset: `Email Asset ID`, `Email Asset Name`, `Email Asset Link`, `Email event Detail`<br />• Journey: `Run ID`, `Journey ID`, `Journey Name`<br />• Datetime<br />• Engagement: `is_bot` inside `event_meta` (Open, Clicked, and Unsubscribe events) |
| Journey | Journey Entered<br />Journey Completed<br />Journey Exited | • Contact: `Inflection Contact ID`, `Contact Email`<br />• Journey: `Run ID`, `Journey ID`, `Journey Name`<br />• Datetime |
| Forms & Inbound Webhooks | Form Submitted<br />Inbound Webhook Submitted | • Contact: `Inflection Contact ID`, `Contact Email`<br />• `Datetime` |

<Tip>
  All ID columns are accompanied by human-friendly names to make querying and dash-boarding easy.
</Tip>

<Info>
  Email Open events are deduplicated before export. If a contact opens the same email several times in a short window, one Open row is exported.
</Info>

<Info>
  **Journey Completed vs. Journey Exited**: **Journey Completed** is triggered when a record finishes all flow steps in the journey and reaches the end. **Journey Exited** is triggered when a record meets the journey's exit criteria and exits the journey.
</Info>

## Configure Data Warehouse Export

Inflection currently supports importing data from the following data warehouses:

* [Big Query](/connections/warehouses/bigquery)
* [Databricks](/connections/warehouses/databricks)
* [Redshift](/connections/warehouses/redshift)
* [Snowflake](/connections/warehouses/snowflake)

## Manage Data Warehouse Export

Once your data export connection is active, you can review its status, manage what data is being synced, and monitor sync activity via:

* **Sync Settings**: View sync history, sync errors, monitor record counts, and track export status.
* **Connection Details**: Review or edit connection configuration and view SQL snippet used for creating the export tables.

### Sync Settings

The **Sync Details** tab gives you visibility into the status and history of all sync activity.

Here you can:

* See **next scheduled sync time** and the **last completed sync duration**
* Track the **number of records synced** and **total tables updated**
* View a **sync history table** showing:
  * Timestamp of each sync
  * Target table (e.g., `Inflection Activities`, `Entity`)
  * Number of rows inserted or updated
  * Count of any errors
* Filter history by:
  * **Date range** (via calendar selector)
  * **Empty vs. non-empty syncs**

You can also pause the entire sync using the **Pause Sync** button in the top-right corner.

### Connection Details

The **Connection Settings** tab shows the credentials and database details configured for your data warehouse export connection. This is where you can review or update your connection setup.

Here you’ll find:

* **Connection Credentials**
  * **Account Name**: Your data warehouse account identifier
  * **Username**: The user Inflection will authenticate as
  * **Password**: Stored securely and not visible in the UI
* **Database Details**
  * **Connection Name**: Internal name for this export connection
  * **Database**: The destination database for exported data
  * **Schema**: The schema where Inflection will write tables
* **Table Creation SQL (Snowflake only)**
  * Pre-generated SQL code to create the required tables in your warehouse
  * You can **view**, **copy**, or **send** the SQL to your data team

<Info>
  To update credentials or database information, click **Edit Details**. The sync will be paused before making changes.
</Info>

## Table Schema

Inflection exports two tables to your data warehouse:

### 1. `inflection_marketing_activities`

This is the main event log table. Each row corresponds to a single marketing activity or event such as an email send, form fill, or journey entry.

| Column Name | Data Type | Description |
| - | - | - |
| id | STRING | Unique identifier for the event record. |
| event\_name | STRING | Name of the event (e.g., "Email Clicked", "Journey Entered", "Form Submitted"). |
| event\_details | STRING | Additional metadata about the event (e.g., delay timing, webhook names, etc.). |
| event\_time | DATETIME | UTC timestamp when the event occurred. |
| inflection\_contact\_id | STRING | Internal ID of the contact within Inflection. |
| contact\_email\_id | STRING | Contact's email address. |
| asset\_id | STRING | Unique ID of the asset involved in the event, if applicable. |
| asset\_link | STRING | Direct URL to the asset. |
| run\_id | STRING | ID representing the unique run session of a journey. |
| journey\_id | STRING | ID of the journey where the event occurred. |
| event\_meta | JSON | Additional event information as JSON. For email Open, Clicked, and Unsubscribe events this includes `is_bot`, which is `true` when Inflection detected the activity as automated, such as a security scanner or link checker. Filter on `event_meta.is_bot` to exclude bot activity from your reports. |
| created\_at | DATETIME | Timestamp when the event was first logged. |
| updated\_at | DATETIME | Timestamp when the event record was last updated. |

### 2. `inflection_marketing_entities`

This is a supporting table used for mapping IDs in the event table to their corresponding names and types. It improves readability and enables easier joins in BI tools.

| Column Name | Data Type | Description |
| - | - | - |
| id | STRING | Unique identifier of the entity (e.g., journey, template, flowstep). |
| entity\_type | STRING | Type of entity (e.g., `JOURNEY`, `TEMPLATE`, `FLOW_STEP`). |
| entity\_name | STRING | Human-readable name of the entity. |
| entity\_meta\_info | STRING | Additional metadata or context for the entity (e.g., delay info, linked IDs). |
| is\_deleted | BOOLEAN | Boolean which says entity deleted or not |
| created\_at | DATETIME | Timestamp when the entity was first recorded. |
| updated\_at | DATETIME | Timestamp when the entity record was last modified. |

<Tip>
  `entity_type` and `entity_name` can be joined with IDs in the main table to create user-friendly reports and dashboards.
</Tip>

## Permissions & Security

Inflection only requires **table-level permissions** for export:

* `INSERT`
* `UPDATE`
* `DELETE`
* `ALTER`

We do **not** require database or schema-level access.

<Info>
  Databricks requires you to grant `USE CATALOG` and `USE SCHEMA` permissions to Inflection’s service principal.

  These don’t give access to your data; they just let Inflection choose the right catalog and schema when running queries.
</Info>

This ensures you can maintain tight control over what Inflection can access and modify.

## Example Reports You Can Build

Once your data is in the warehouse, you can use any BI tool to generate reports like:

* Journey funnel drop-off
* A/B test performance
* Email click rates over time, excluding bot activity by filtering on `event_meta.is_bot`
* Unsubscribes vs. sends (MoM)
* Cross-journey activity trends

## Troubleshooting & FAQs

**My sync is stuck. What do I do?**

* Check the **Sync Health Status** on the connection page. Common issues include:
  * Table structure mismatch
  * Missing permissions
  * Connection credentials expired
* Contact your data team to validate the table setup or re-run the setup script.


# Import from Data Warehouse
Source: https://docs.inflection.io/connections/import-from-data-warehouse

Connect your data warehouse as a source of Inflection data. Send marketing activities from Inflection to DWH for analytics.

Connecting your data warehouse to Inflection enables you to centralize product usage, user, and organizational data for powerful marketing automation and personalization. Sync all your product users, organizations, and activity events to drive targeted campaigns based on real product behavior.

## Overview & Considerations

Each Inflection object has specific schema requirements for the source data warehouse table, so be sure to read these requirements carefully before connecting. The sources for these objects can be either views or tables in the data warehouse. For the purposes of this document we will refer to the source entities generally as “tables," although views are equally supported and have the same schema requirements as tables.

There is no limit to the number of data warehouse connections. With the exception of Product Activity, each Inflection object can only be connected to one data warehouse table, but each Inflection object can be connected to other sources like Salesforce and Segment, in addition to one data warehouse table. For example, the **Inflection Contact** can be connected to a Redshift table, Segment, and Salesforce, while the **Inflection Org** is connected to Snowflake or a second Redshift instance. **Product Activity** is synced from a single table or view. If your events live in one table per event, point Inflection at a view that unions them.

Fields mapped from a data warehouse to Inflection are connected in one direction only: Inflection will read the field from the data warehouse and write it to the mapped Inflection field, but any updates to this field in Inflection will not be written back to the data warehouse. For this reason, we advise treating these fields as data warehouse only fields in Inflection and not updating them from other sources (like Salesforce, forms, etc.).

Inflection supports both **1:many** and **many:many** relationships between Contacts and Organizations. Use **many:many** if a single email address can belong to many different organizations within your product. If an email address can only belong to one organization in your product, then use **1:many**.

Contact Inflection support ([support@inflection.io](mailto:support@inflection.io)) for help setting up this mapping.

## What Data to Send to Inflection

Unlike many other services, Inflection is built to handle massive scale when connecting data sources.

We recommend syncing **all** product users (people using your product) and org data to Inflection.

As for Product Activity, we recommend syncing all the product activity data that might someday be used by the marketing, growth, sales, and success teams. Some events, like debugging, logging, or internal engineering events need not be synced and will only clutter the Inflection instance for the GTM teams using Inflection.

When in doubt, we recommend syncing more data so the Inflection users can work autonomously and not have to request work from your data or engineering teams.

## Prerequisites

Before connecting your data warehouse, ensure you have:

* Admin access to your Inflection account
* Access credentials for your data warehouse
* Source tables that meet the schema requirements outlined below

Note that once your data warehouse connection is configured, you will contact Inflection support ([support@inflection.io](mailto:support@inflection.io)) for assistance with initializing the sync.

## Configure Your Data Warehouse Connection

Inflection currently supports importing data from the following data warehouses:

* [Snowflake Setup and Configuration (using storage integration)](/connections/warehouses/snowflake)
* [BigQuery Setup and Configuration](/connections/warehouses/bigquery)
* [Databricks Setup and Configuration](/connections/warehouses/databricks)
* [Redshift Setup and Configuration](/connections/warehouses/redshift)

Select your data warehouse from the list above and follow the warehouse-specific setup instructions.

Syncs run on a schedule you choose per connection: every 10 minutes, 30 minutes, hourly, every 4 hours, every 12 hours, or daily.

## Mapping Data Warehouse to Inflection Objects

The field requirements below follow the Inflection connection setup wizard, which checks each object's key fields before the connection can be activated. Every object needs a **last modified** timestamp; Inflection uses it to sync only rows that changed since the previous run. If that column has no time zone, the wizard asks you which zone it is in.

### Contacts

Contacts in Inflection represent a person and are **unique by email address**. Any data warehouse table mapped to Contacts needs to also be unique by email address (no duplicate email addresses in the email column of the data warehouse table). Inflection supports multiple product users to have the same email address across multiple orgs with the Product User object. In addition to uniqueness by email, any data warehouse table that is connected to the Inflection Contact object must have the following schema restrictions:

* `email_address` field is **unique & required.  If the** `email_address `**is null or not a valid email address, Inflection will not sync that row.**
* must have a `unique id` (`primary key`), non-null and unique per contact
* must have a `last modified date` (`timestamp`)
* a `created date` is optional and can be mapped as a custom field

In addition to the required and recommended fields, any number of custom fields can be added to the Contact object in Inflection and synced from the data warehouse source table.

Below shows the Inflection table-import screen; the connection setup wizard shows these fields on its **Contacts** step.

<img alt="Image" />

To connect a table, open the connection setup wizard, choose **Contacts**, pick the source table or view, confirm the ID, Email and Last modified columns the wizard detected, then map any additional columns.

<img alt="Image" />

### Product Activity

Product Activity in Inflection represents the stream of immutable events coming from your product. These Product Activity events are typically generated by a CDP like Segment or Rudderstack, or a product analytics platform like Amplitude, Pendo, or Heap. Inflection can consume this stream of events from the data warehouse using the Product Activity object.

Data warehouse tables synced to the Inflection Product Activity object must follow the following schema:

* must have a `primary key` (`id`) that is unique per event and up to 100 characters.  If your table has no unique event ID, Inflection can generate a composite key.
* `event date` is a required non-nullable field (`timestamp`) representing when the event happened.  It is also the incremental sync cursor.
* `event name` is a required non-nullable field (`string`, `char`, or `varchar`, up to 200 characters)
* `product user id` is a required non-nullable field.  It must match the `id` of a row in the Product User table.

<img alt="Image" />

Optional columns: `email`, and `event properties` (JSON), for which you choose the source columns that are folded into it. Product Activity is read from one table or view as-is; joins and transforms are not available for this object, so do any reshaping in a view on your side.

### Product Users

The Product User object in Inflection represents the person using your product. Every Product User has an associated Contact and optionally can have an Org and Product Activity associated with it.

Any data warehouse table that is connected to the Inflection Product User object must have the following schema restrictions:

* `email_address` field is **required** & **non-nullable**
* rows with a null or invalid `email_address` are skipped
* must have a `unique id` (`primary key`), non-null and unique per product user
* must have an `org id`: the `id` of the Org the user belongs to.  The Inflection product has specific capabilities around Orgs, and this relationship enables them.
* must have a `last modified date` (`timestamp`)
* a `created date` is optional and can be mapped as a custom field

Any custom columns on the Product User data warehouse source table can be mapped directly to the Product User object in Inflection and can also mapped directly to the Contact object in Inflection. For example, a Contact record in the CRM will have a `First Name` and `Last Name` field which will likely be mapped to the `First Name` and `Last Name` on the Inflection Contact object. Additionally, the product may collect a `First Name` and `Last Name` in product signup. There are a few options in this case:

1. Map the `First Name` and `Last Name` from the product sign up to the Product User as custom fields. Journeys, Tokens, personalization, etc. inside Inflection will have access to `First Name` and `Last Name` fields on both Contact and Product User (and these values can be different).
2. Map the `First Name` and `Last Name` from both the CRM and the product to the same fields on Contact. In this case, the most recent update will “win."  Note that if there is also a bi-directional connection to the CRM setup for the `First Name` and `Last Name` fields, then `First Name` and `Last Name` updates from the product (through the DW source table) could cause an update in the CRM First Name field.
3. Map the `First Name` and `Last Name` fields to the Product User, and use operational campaigns to update the `First Name` and `Last Name` on the Contact based on custom business logic.

Below shows the Inflection table-import screen; the connection setup wizard shows these fields on its **Product users** step.

<img alt="Image" />

### Organizations

Organizations (or “Orgs") represent the group of people in your product. Sometimes also referred to as “workspaces” and are distinctly different than Accounts.

Data warehouse tables synced to the Inflection Org object must follow the following schema:

* must have a `unique id` (`primary key`), non-null and unique per organization
* must have a `last modified date` (`timestamp`)
* a `created date` is optional and can be mapped as a custom field
* strongly recommended to have a `name` (`string`, `char`, or `varchar`) for display in the Inflection UI.  Without a name, the Inflection app will show the `id`

In addition to the required and recommended fields, any number of custom fields can be added to the Organization object in Inflection and synced from the data warehouse source table.

<img alt="Image" />

### Person Organization Mappings

This mapping represents that a user belongs into an organization or workspace in your product. Mapping is used to represent a **many to many** relationship in your schema.

Data warehouse tables synced to the Inflection Mapping object must follow the following schema:

* must have a `unique id` (`primary key`), non-null and unique per membership row
* must have a `user id` which matches a Product User `id`
* must have an `org id` which matches an Organization `id`
* must have a `last modified date` (`timestamp`)
* `email` is optional

In addition to the required fields, any number of custom fields can be added to the Mapping object in Inflection and synced from the data warehouse source table to represent properties of that User in relation to the Org (example: is\_admin, role, etc.).

<img alt="Image" />

### Accounts

Accounts represent the Account object in the CRM and are distinct from Orgs which represent the Org (or workspace) in the product. For example, your sales or sales ops teams likely decide what Contacts are connected to what Account in the CRM, but your customers can add whoever they want to the org in your product. So these objects are distinct in Inflection.

Most Inflection customers sync Account data from the CRM and not from the data warehouse.  Syncing Account data exclusively from data warehouse, or from both data warehouse and CRM is supported. The most common case for syncing Accounts from data warehouse is if you are using a CRM that Inflection does not have a direct API integration with.

Contacts are linked to Accounts by matching one Contact field to one Account field (for example, email domain to account website). Inflection support configures this pairing for your instance.

Data warehouse tables synced to the Inflection Account object must follow the following schema:

* must have a `unique id` (`primary key`), non-null and unique per account.  **If Salesforce is also connected, this must be the Salesforce Account Id.**  Inflection merges account records by ID, so a different ID creates a duplicate account.
* must have a `last modified date` (`timestamp`)
* a `created date` is optional and can be mapped as a custom field
* strongly recommended to have a `website (or domain)` (`string`, `char`, or `varchar`) for Contact to Account mapping
* strongly recommended to have a `name` (`string`, `char`, or `varchar`) for display in the Inflection UI.  Without a name, the Inflection app will show the `id`

In addition to the required and recommended fields, any number of custom fields can be added to the Account object in Inflection and sync’d from the DW source table.


# Inbound Webhooks
Source: https://docs.inflection.io/connections/inbound-webhooks

Connect to other third-party tools using inbound webhooks.

Inflection lets you ingest data from any third-party provider that supports outbound webhooks. With **Inbound Webhooks**, you receive data in **JSON format** and use it to **update contact properties** and **filter audiences inside journeys**. You can secure each webhook with different authentication methods to control who can send data.

<Info>
  We recommend limiting webhook submissions to 1,000 requests/minute. If you need higher throughput, reach out to your customer success team.
</Info>

<Info>
  **Key concepts**

  * **Connection provider**: The external system sending data to Inflection (for example, Zapier, a webinar tool, or a custom integration).
  * **Inbound webhook connection**: The authenticated connection between Inflection and your provider, with its own endpoint URL, field mapping, and lifecycle state.
  * **Group**: A subset of submissions within a connection, split by a field you choose (see [Group submissions](#group-submissions)).
</Info>

## Step 1: Set Up an Inbound Webhook Connection

Creating a connection is a full-page, two-step flow: **Endpoint setup** → **Map fields**. There is no third step.

1. From the **Inbound Webhooks** list, click **Create**.
2. In the **Connection provider** panel, select **Generic Inbound Webhook**.

<img alt="The two-step creation flow with the Connection provider panel and the Endpoint setup and Map fields step indicator" />

3. On the **Endpoint setup** step, fill in the connection details:
   * **Connection name** (required). If you leave it empty, you'll see **Connection name should not be empty**.
   * **Authentication** - choose the method that matches your security needs. While "No Auth" is available, we strongly recommend Basic Auth or API Key to prevent spam and unauthorized access.
   * **Description** (optional).
   * **Create contact** option - sets whether a new contact is created when an email address that isn't already in Inflection is received.
4. Click **Continue to map fields**.

### Authentication

Select the authentication option that matches your security requirements. Using No Auth can expose your webhook to spam and malicious data - Basic Auth or API Key is strongly recommended.

**No Auth**

No authentication. Anyone with the webhook URL can send data.

<Info>
  Not recommended. Risk of spam or malicious data.
</Info>

**Basic Auth**

Uses a username and password combination.

* Credentials are hidden after setup. Copy and store them securely.
* To reset: Click **Reset Password** from the connection page and enter a new password. Update the password in your third-party system.

**API Key**

An API key is automatically generated.

* Configure in your third-party tool using **one** of the following methods:
  * **Option 1 - Custom Header**: Key: `Authorization` / Value: `Bearer <YOUR_API_KEY>`
  * **Option 2 - Bearer Token**: Paste the API key directly into the "Token" or "Authorization" field in your integration settings.
* To reset: Click **Refresh API Key** under Authentication Details. Update the API key in your third-party system.

<Info>
  Credentials are hidden after setup. If you reset credentials, update your third-party system immediately. The webhook URL remains unchanged. Once the connection is created, the authentication method cannot be changed.
</Info>

## Step 2: Map Fields and Group Submissions

The **Map fields** step gives you everything you need to point your provider at Inflection and describe the payload it sends.

<img alt="The Map fields step showing the Webhook URL, sample payload, grouping control, and field-mapping table" />

1. Copy the endpoint from the **Webhook URL** block using its copy control, then configure it (with any credentials) in your third-party tool.

2. In the **Payload** textarea, either paste your own JSON or use the sample that's prefilled for you:

   ```json theme={null}
   {"email": "demo@example.com", "first_name": "Demo", "webinar_id": "july26"}
   ```

   The helper text reads "Use the sample payload or paste your own JSON." If the JSON is invalid, you'll see **Enter a valid JSON object before submitting.**

3. Click **Submit sample payload**. On success you'll see **Payload received. Fields are ready to map.** and the detected fields populate the mapping table.

<Info>
  Nested JSON objects arrive **flattened** using dot notation. For example, `{"props": {"company": "Acme"}}` appears as the field `props.company`.
</Info>

4. Map the detected fields to contact properties. The field-mapping table lists every field detected in your payload. It has four columns:

| Column | What it shows |
| - | - |
| **Payload field** | The field name from your JSON (dot notation for nested fields). |
| **Sample Preview** | The example value from the submitted payload. |
| **Contact field** | The contact property this field maps to. Unmapped rows show **None (Unmapped)**. |
| **Mapping rule** | How the value is applied: **Always overwrite** or **Update if empty**. |

5. Click **Save mapping** to persist your mapping. You must map the **Email** contact field before you can continue - if it isn't mapped, you'll see **Map the Email contact field before continuing.**

### Group Submissions

You can split a connection's submissions into groups based on a field in the payload - useful when one endpoint receives data for several sources (for example, one row per webinar).

* Use the **Group submissions by field (optional)** control to pick the grouping field.
* The **How it works** link opens a **How grouping works** explainer.

<img alt="The How grouping works explainer opened from the How it works link" />

<Warning>
  The grouping field is permanent. Once you set a grouping field and click **Finish setup**, it is locked for the life of the connection. If you reopen the setting later, it appears disabled with a lock icon and the text "Grouping is set once for a connection and can't be changed afterwards." Choose your grouping field carefully before finishing setup.
</Warning>

## Connection Detail Page

Each connection opens as a single scrolling page.

At the top are two badges:

* A **lifecycle** badge (see [Lifecycle actions](#lifecycle-actions)).
* A **readiness** badge (see the states below).

Below the badges, a stat strip shows four tiles: **Submissions**, **Groups**, **Errors**, and **Grouped By**.

The rest of the page includes:

* **Connection Details** card - lists Type, Create Contact, Last Activity, Authentication, Date Created, and **Processing Lane** (Real-time or Bulk - see [Processing Lanes](#processing-lanes)).
* **Endpoint URL** - with a copy control.
* **Connection Health** - includes a **View submission errors** action.
* **Groups table** - columns **Group**, **Submissions**, **Errors**, and actions, plus a **Refresh** control. If no groups exist yet, it shows a **Default group** placeholder row.

### Readiness States

The readiness badge tells you how far along the connection is:

| State | What it means |
| - | - |
| **Setup incomplete** | The connection is created but nothing has been received yet. |
| **Mapping needed** | A payload has arrived, but the mapping isn't finished. |
| **Ready** | Mapping is complete and the connection is processing data. |
| **New fields found** | A payload arrived containing a field that isn't mapped yet. |

## Lifecycle Actions

The **lifecycle** badge shows the connection's current state - a connection is **Active** while it is processing incoming data.

Use the lifecycle actions to control whether a connection is processing incoming data:

* **Pause** - Confirmation reads "Pausing stops incoming data processing until this connection is resumed." The confirm button is **Pause sync**. While paused, incoming POSTs are **rejected, not queued**.
* **Resume** - Sets a paused connection back to **Active**. Applies immediately, with no confirmation dialog.
* **Disable** - Confirmation reads "Once disabled, this connection will no longer process incoming data." Once disabled, a connection **cannot be self-resumed**.

<Info>
  Lifecycle actions and editing are available to **Admins** and **Editors**. They're hidden from **Viewers**.
</Info>

## Delete a Connection

Deletion is available to **Admin** users only, and it isn't available from the list. To delete, open a group's actions on the connection detail page and choose delete.

If the group or connection is still referenced by journeys or dynamic lists, a modal blocks deletion and lists the blockers with links:

> The following journeys or audiences still reference these inbound webhooks. Remove every reference, then click Refresh.

The confirm button reads **Resolve dependencies to delete** and stays disabled until every reference is removed.

To free the connection for deletion:

1. Open each blocking journey or audience from its link and remove the inbound webhook reference, then save.
2. Return to the modal and click **Refresh**.
3. When no references remain, the block clears and you can delete the connection.

<Info>
  Removing a reference changes how that journey or dynamic list behaves. Confirm the reference is no longer needed before you remove it.
</Info>

## Processing Lanes

Every inbound webhook connection is assigned to a **processing lane** - either **Real-time** or **Bulk**. Processing lanes isolate your webhook traffic so that high-volume submissions on one connection don't slow down another.

<Info>
  **How processing lanes work**

  * Each customer gets **two separate lanes** for processing webhook data. One connection's traffic cannot congest the other lane.
  * **There is no difference in processing speed between the two lanes.** Both Real-time and Bulk process submissions at the same rate. The names refer to the intended use case, not to a speed difference.
  * Use **Real-time** for connections where speed-to-lead matters (for example, demo-request forms or high-priority lead sources).
  * Use **Bulk** for high-volume, batch-style data imports where you want to keep the traffic separate from your real-time connections.
</Info>

### Default Assignments

Existing connections are automatically assigned a default lane:

| Connection type | Default lane |
| - | - |
| Inbound webhook connections | Bulk |
| Custom form connections | Real-time |

You can change a connection's lane at any time from the **Connection Details** card on the connection detail page.

### Changing a Connection's Lane

1. Open the connection's detail page and open its settings for editing.
2. Under **Processing lane**, select one of the two options:
   * **Real-time** - recommended for form submissions and low-to-moderate volume.
   * **Bulk** - recommended for automations and high-volume sources.
3. Click **Save**.

<img alt="The Processing lane selector on the connection settings form, with Real-time and Bulk options and their recommended use descriptions" />

The change takes effect immediately for new incoming submissions.

## Use Inbound Webhooks in Journeys

You can use webhook submissions as audience filters or branching criteria:

1. Navigate to **Journeys → Create New Journey**.
2. Add a condition: **Performed a Marketing Activity → Inbound webhook sync**.

You can also use **Branch by Filter** to personalize flows based on any mapped field.

## Examples for Inbound Webhook Setup

**General purpose enterprise automation platform**

[Zapier](/connections/webhooks/zapier)

**Social lead generation**

[Linkedin](/connections/webhooks/linkedin)

**Webinars**

[Zoom](/connections/webhooks/zoom)

[Goldcast](/connections/webhooks/goldcast)

**Enrichment**

[Clearbit](/connections/webhooks/clearbit)

[Clay](/connections/webhooks/clay)

**Data sync with CRMs/MAPs**

[Marketo](/connections/webhooks/marketo)

[Hubspot](/connections/webhooks/hubspot)

**Forms**

[Formsite](https://support.formsite.com/hc/en-us/articles/360000546194-Webhooks)

[Typeform](https://www.typeform.com/developers/webhooks/)

## Inbound Webhooks FAQs

<AccordionGroup>
  <Accordion title="Why are the lanes called Real-time and Bulk?">
    The names describe the **intended use case**, not a speed difference. Both lanes process data at the same rate. "Real-time" is meant for connections where you want fast, isolated processing (like lead-capture forms), and "Bulk" is for high-volume imports you want to keep on a separate lane. The key benefit is **traffic isolation** - one lane's load cannot affect the other.
  </Accordion>
</AccordionGroup>


# Inflection Forms
Source: https://docs.inflection.io/connections/inflection-forms

Collect prospect or customer responses with native Inflection forms.

Inflection's native form builder lets you capture lead and contact data directly from your website — with automatic field mapping and built-in attribution tracking. Create conversion-optimized forms in minutes using your existing contact fields, then connect them to journeys for instant automated follow-up.

<Info>
  Inflection also supports a Forms API (also called custom forms) for more advanced integration scenarios.
</Info>

## The Forms List

**Forms** is now a top-level item in the main sidebar, listed after **Outbound Webhooks** and **Inbound Webhooks**. It's a single unified list - every form type appears here, whichever provider it came from.

The list has these columns:

| Column | What it shows |
| - | - |
| **Form name** | The internal name of the form. |
| **Form provider** | The provider the form came from (for example, Inflection form or a connected third-party provider). |
| **Submissions** | The number of submissions received. |
| **Last submission** | When the form last received a submission. |
| **Status** | The current status of the form. |

Use the **Active only** toggle to hide inactive forms and show only active ones.

## Create a Form

Click **New Form** to open the **Create form** drawer. It offers exactly these options:

* **Inflection form** - the native form builder documented below.
* **Webflow form** - connect forms from Webflow.
* **Formstack form** - connect forms from Formstack.
* **Custom form connection** - post JSON to a webhook from any form tool. See [Custom Forms](/connections/custom-forms).

<img alt="The Create form drawer showing the Inflection form, Webflow form, Formstack form, and Custom form connection options" />

<Info>
  If a provider is already connected in this workspace, its option is disabled with the tooltip "This provider is already connected in this workspace."
</Info>

## Prerequisites

* Access to Inflection with permission to create forms
* Contact fields configured in your Inflection account (navigate to **Connections** > **Contact Fields** to review)
* For first-touch attribution capture: Inflection website tracking script installed on your site

<Info>
  Contact fields with sync preference set to **Always use Salesforce** will not appear in form field mapping lists, as these fields can only be updated by Salesforce. To use these fields in forms, update the sync preference in **Contact Fields**.
</Info>

## Create a New Inflection Form

1. In the **Create form** drawer, choose **Inflection form**.
2. Enter an internal name in the top-left field (e.g., `webinar_march`). This name is for internal reference only and will not appear on your website.
3. Enter a form title. This title is displayed to visitors on the rendered form.

## Add and Configure Form Fields

1. Locate the contact field list on the left panel of the form builder.
2. Drag and drop fields from the left panel onto the form canvas. The form preview updates in real time on the right.

<Info>
  **Email** is required on every form and cannot be removed.
</Info>

The following options are available for each field:

* **Label**: Change the display label (e.g., rename **First Name** to **Name**). The field mapping indicator below the label confirms which contact field the data maps to.
* **Placeholder**: Set placeholder text displayed inside the input.
* **Width**: Set to **Full** or **Half**. Setting two adjacent fields to half-width places them side by side in a two-column layout.
* **Required**: Toggle to make the field mandatory for submission.
* **URL Pre-fill**: When enabled, the field auto-populates if a matching query parameter is present in the page URL (e.g., `?first_name=John`). Toggle off to opt out.
* **Mapping rule**: Control how submitted values interact with existing contact data. Choose **Overwrite** to always update the contact field with the submitted value, or **Update only if empty** to only populate the field when no value exists on the contact record.

<Info>
  Use **Update only if empty** to protect existing contact data — for example, to avoid overwriting a known lead source with a later form submission.
</Info>

### Add Custom Fields

1. Click **Create Custom Field** below the contact field list.
2. Enter a field name (e.g., **City**) and select a field type (e.g., **Text**).
3. The custom field appears on the canvas. To store its value in a contact property, select a target field from the **Map to** dropdown.

### Add Hidden Fields

1. Click **Add Hidden Field**.
2. Enter a key and a static value (e.g., Key: `webinar_id`, Value: `1234`).
3. Hidden fields are not visible to form visitors but their values are submitted with the form data. Optionally, map hidden fields to a contact property using the **Map to** dropdown.

### Add Custom URL Parameters

1. Click **Add Custom URL Parameter**.
2. Enter the parameter name (e.g., `first_page`).
3. When the form loads on a page with that parameter in the URL, the value is captured and can be mapped to a contact field.

### URL Attribution Capture

Forms automatically capture the following attribution data when the Inflection tracking script is installed on your website:

* First-touch and last-touch UTM parameters (`utm_source`, `utm_medium`, `utm_campaign`, etc.)
* Referrer URL
* Session ID

Map these values to contact fields using the dropdowns in the **URL Query Params** section.

## Style the Form

1. Click the **Form Styling** tab in the form builder (lower right).
2. Configure the following options:
   * **Label display**: Choose between **Label and Placeholder** or **Placeholder Only** (labels move inside input fields).
   * **Font**: Select a font family for the form.
   * **Background**: Choose a solid color or select **Transparent** to show the host page's background through the form — useful when embedding on pages with a non-white background.
   * **Text color**: Set the label and input text color.
   * **Button color**: Set the submit button background color.
   * **Button text color**: Set the submit button text color.
   * **Button label**: Customize the submit button text (default: Submit).
   * **Corner radius**: Adjust the border radius of input fields and buttons.

## Set Up Validation and Tracking

1. Click the **Validation & Tracking** tab (lower right).
2. **Block personal emails**: Toggle on to reject submissions from personal email domains (Gmail, Outlook, Yahoo, etc.).
3. **Consent text**: Enter consent language (e.g., "By submitting this form, you agree to our Privacy Policy"). Add a link URL for the privacy policy page.
4. **Consent checkbox**: Toggle on to display a checkbox that visitors must select before submitting. Map the checkbox to a boolean contact field (e.g., Opt-in) to track opt-in status — when the checkbox is checked on submit, the mapped field is set to true.
5. **reCAPTCHA**: Toggle on to add bot protection to your form. When enabled, Google's reCAPTCHA challenge is presented to visitors identified as suspicious before they can submit.

<Info>
  Google reCAPTCHA is risk-based - the challenge does not appear on every submission. Google determines when to show it based on visitor behavior signals, so most legitimate visitors will submit without interruption.
</Info>

## Configure the Thank You Message

1. Click **Save and Continue** to proceed to Step 2.
2. Choose one of the following:
   * **Thank you message**: Display a default or custom confirmation message after submission.
   * **Redirect URL**: Redirect visitors to a custom thank you page after submission. Enter the full page URL.
3. Click **Save and Continue** to generate the embed code.

## Embed Your Form

1. After saving the thank you message, the embed code is displayed.
2. Click **Copy** to copy the embed script.
3. Paste the script into the HTML of the page on your website where you want the form to appear. The form renders automatically.

<Info>
  Any changes you make to the form in Inflection reflect immediately on your website — no need to update the embed code.
</Info>

## View Form Submissions

1. Navigate to **Forms** and click on your form to open it.
2. Open the **Submissions** tab to view all form submissions.
3. Each submission displays the captured field values, hidden fields, and UTM attribution data.

<Info>
  Form submission data for mapped contact fields will update the contact record according to the mapping rule set for each field (Overwrite or Update only if empty).
</Info>

<Info>
  Each form submission creates a marketing activity entry on the contact's record. Use this activity as a journey trigger or in dynamic list filters to automate follow-up based on form submissions.
</Info>

## Edit an Existing Form

1. Navigate to **Forms** in the left sidebar.
2. Locate the form you want to edit and click **Edit** (or click the form name).
3. Make changes to fields, styling, or validation settings.
4. Click **Save and Continue** through each step. Changes take effect immediately on any page where the form is embedded.


# Outbound Webhooks
Source: https://docs.inflection.io/connections/outbound-webhooks

Send data to external systems in real time.

**Outbound Webhooks** allow Inflection to send data to external systems in real time. Use them to enrich contact records with third-party data, trigger actions in other tools, or connect Inflection to any service that accepts HTTP requests, all without writing code.

Outbound Webhooks support GET, POST, PUT, PATCH, DELETE, and HEAD request methods, and can be used as a step in any journey to automate data flow at scale.

<AccordionGroup>
  <Accordion title="View and Manage Webhooks">
    Navigate to **Outbound Webhooks** from the left sidebar to view all configured webhooks.

    <img alt="Outbound Webhooks entry in the left sidebar" />

    The listing page displays each webhook's name, request method, response mapping status, creator, and creation date. Use the search box to find a webhook by name, or filter by request type, creator, or date range.
  </Accordion>

  <Accordion title="Create a New Webhook">
    There are two ways to create a new outbound webhook:

    * Click **Outbound Webhooks** in the left sidebar, then click **New Outbound Webhook** on the listing page.
    * Navigate to a folder and create a new 'Outbound webhook' directly in the folder
  </Accordion>

  <Accordion title="Configure the Webhook">
    1. Enter a name and description for the webhook.
    2. Select a request method (GET, POST, PUT, PATCH, DELETE, or HEAD).
    3. Enter the destination URL. Use the variable picker to insert fields directly into the URL if needed.
    4. Add any custom request headers. For example, to authenticate with an external service, add an **Authorization** header with a Bearer token.
    5. Click **Save Draft**

       <img alt="Configure tab with request method, destination URL, and custom headers" />

    ### Import From cURL

    Instead of manually configuring a webhook, import a cURL command to auto-populate the method, URL, headers, and payload.

    1. Click **Import from cURL** on the **Configure** tab.
    2. Paste a cURL command into the text area and click **Parse**.
    3. Review the parsed preview showing the method, URL, headers, and body.

       <img alt="Import from cURL dialog with parsed preview of method, URL, headers, and body" />

    Click **Import** to apply the configuration to the webhook. This replaces any existing configuration
  </Accordion>

  <Accordion title="Configure the Request Body">
    1. Navigate to the **Request Body** tab.

    2. Select a content type: `application/json`, `text/plain`, or `application/xml`.

    3. Enter the request payload. Use the variable picker to insert contact variables.

       For example, if you want to send email, first name, and last name to the endpoint, your request body would look something like this:

       ```json theme={null}
       {
         "email": "{{ column("email") }}",
         "firstname": "{{ column("first_name") }}",
         "lastname": "{{ column("last_name") }}"
       }
       ```

    4. Click **Save Draft**.
  </Accordion>

  <Accordion title="Test the Webhook">
    1. Navigate to the **Test** tab.

    2. Search for a contact by email and select one from the dropdown. If applicable, select the org context for the contact.

    3. Click **Send Test Request**. Contact variables in the URL and payload are replaced with the selected contact's actual values before sending.

       <img alt="Test tab showing a test request result for a selected contact" />

    4. Expand **View request sent** to review the exact URL, headers, and body that were sent.

    A successful test returns a 2xx status code. A failed test returns a 4xx or 5xx status code, clearly marked in the UI.

    <Info>
      Response mapping is optional. After a successful test, navigate back to the listing page if response mapping is not needed.
    </Info>
  </Accordion>

  <Accordion title="Set Up Response Mapping">
    Response mapping allows webhook response data to automatically update contact properties in Inflection. After running a successful test, the response fields are available for mapping.

    1. Navigate to the **Response Mapping** tab. Each field from the response appears as a row with its detected data type.

       <img alt="Response Mapping tab listing response fields with detected data types" />

    2. Click **Edit** to enter edit mode.

    3. For each field to map, select a **Contact Property** from the dropdown. Only contact properties that match the field's data type are shown.

    4. Select a **Mapping Rule** for each mapped field:
       * **Update If Empty:** Updates the contact property only if it currently has no value. This is the default.
       * **Always Overwrite:** Updates the contact property every time, regardless of its current value.

    5. Click **Save**.

    Each contact property can only be mapped to one response field. The stats badge at the top shows how many fields are mapped out of the total.

    <Info>
      Each contact property can only be mapped to one response field. The stats badge at the top shows how many fields are mapped out of the total.
    </Info>
  </Accordion>

  <Accordion title="Use a Webhook in a Journey">
    Add an outbound webhook as a step in any journey to send data to external systems as contacts flow through the journey.

    1. Open a journey in the flow builder.
    2. Add a **Run Outbound Webhook** step to the flow.
    3. Click the webhook step and select a webhook from the list.
    4. Save the journey.

    <Info>
      When the journey runs, each contact that reaches the webhook step triggers the configured HTTP request. Fields in the URL and payload are replaced with each contact's actual values.
    </Info>

    <Tip>
      After the journey runs, the webhook step displays success and failure counts on the canvas. Click the counts to open a detailed report showing individual results.
    </Tip>

    <Info>
      If response mapping is configured, contact properties are updated according to the mapping rules as each webhook call completes.
    </Info>
  </Accordion>
</AccordionGroup>


# Salesforce
Source: https://docs.inflection.io/connections/salesforce

Connect your Sales database to Inflection via our bidirectional, native integration.

The salesforce sync ensures that the contacts in your Inflection account reflects the latest data from your Salesforce account.

Inflection integrates with Salesforce Leads, Contacts, Campaign Members, Campaigns, and Accounts. We support bi-directional sync with Salesforce for both Lead and Contact objects, and read-only sync for Account objects.

| Summary | Read | Write |
| - | - | - |
| **Leads** | ✅ | ✅ |
| **Contacts** | ✅ | ✅ |
| **Campaign Members** | ✅ | ✅ |
| **Campaigns** | ✅ | |
| **Accounts** | ✅ | |
| **Opportunities** | ✅ | |

Inflection does not interact with Activities or Custom Objects at this time.

## Install the App

As required by Salesforce, new connected apps must be installed by a System Administrator, or by a user with the `Approve Uninstalled Connected Apps` permission.

<Info>
  You must be a System Administrator or have the Approve Uninstalled Connected Apps permission.
</Info>

### Authorize the Inflection connected app in Salesforce

* Open the correct link for your instance type
  * Regular: [https://login.salesforce.com/services/oauth2/authorize?client\_id=3MVG9OGq41FnYVsE24zTULLGqhaM8wOKF3Rd5EhSxqkbQlwEG.hkGRLg1DqUTaw\_Zm38froHzEgduB\_7iNMAu\&redirect\_uri=https://app.inflection.io/salesforce/install-app\&response\_type=code](https://login.salesforce.com/services/oauth2/authorize?client_id=3MVG9OGq41FnYVsE24zTULLGqhaM8wOKF3Rd5EhSxqkbQlwEG.hkGRLg1DqUTaw_Zm38froHzEgduB_7iNMAu\&redirect_uri=https://app.inflection.io/salesforce/install-app\&response_type=code)
  * Sandbox: [https://test.salesforce.com/services/oauth2/authorize?client\_id=3MVG9OGq41FnYVsE24zTULLGqhaM8wOKF3Rd5EhSxqkbQlwEG.hkGRLg1DqUTaw\_Zm38froHzEgduB\_7iNMAu\&redirect\_uri=https://app.inflection.io/salesforce/install-app\&response\_type=code](https://test.salesforce.com/services/oauth2/authorize?client_id=3MVG9OGq41FnYVsE24zTULLGqhaM8wOKF3Rd5EhSxqkbQlwEG.hkGRLg1DqUTaw_Zm38froHzEgduB_7iNMAu\&redirect_uri=https://app.inflection.io/salesforce/install-app\&response_type=code)
* Sign in to Salesforce if prompted. If already signed in, you will be redirected automatically.
* Click **Allow** to authorize the Inflection connected app for your Salesforce org.

<img alt="Salesforce Allow Access screen for the Inflection connected app" />

* After authorization, proceed to install the app.

### Install the Inflection connected app in Salesforce

* In Salesforce, go to Setup.
* Under **Platform Tools**, navigate to **Apps** → **Connected Apps** → **Connected Apps OAuth Usage**.
* Click **Install** next to the `Inflection.io` connected app.

<img alt="Connected Apps OAuth Usage list showing the Install button for Inflection.io" />

* In the modal, click **Install** to complete the installation.

<img alt="Install confirmation modal for the Inflection connected app" />

After these steps are complete, the Inflection connected app is installed in your Salesforce Instance.

## Set up & Sync

<Info>
  **Pre-requisites**: Before setting up a Salesforce connection in Inflection, decide which objects to sync and ensure the following:

  * You have administrator access to your Salesforce account
  * Your Salesforce edition has API access
  * Your user profile meets the minimum requirements
</Info>

<Info>
  Note than only one Salesforce connection is allowed per account.
</Info>

<AccordionGroup>
  <Accordion title="Set up a Salesforce Connection">
    1. In **Connections**, navigate to **Data Connections** and click **Add new connection.** Select **Salesforce.**
    2. Make sure that you have provided admin credentials to the Inflection sync user and it has API access. Name your connection and click **Save**.
    3. You will be re-directed to log in to Salesforce. Log in.
    4. The Inflection screen displays the available permissions for each object. If you don't have the necessary permissions for the object you wish to sync, provide the correct access to the Inflection sync user in Salesforce. You can click **Re-check permissions** to validate the permissions. Once the appropriate permissions are provided, click **Proceed**.
    5. You will be directed to a modal where you can define the object sync and API settings. Here, you can specify which objects to sync with/from Salesforce and the APIs that you want to allocate to Inflection.
    6. After clicking **Proceed**, you will be directed to the final summary page. This page displays the connection name, the number of APIs allocated to Inflection, the approximate sync interval, and the synced objects.

       <Info>
         If you click **Cancel**, the wizard will close. You can always start the sync process again. You can always update these settings later in the Salesforce settings tab
       </Info>

       * **Option 1 | Recommended Settings**: selecting this option will automatically map Salesforce default fields to Inflection fields. Custom fields will not be mapped at this point, but you can map them later in the unified mapping.

         <Info>
           If you have Segment or any other system configured in the unified mapping, checking this box will override any previously mapped Segment fields with Salesforce fields and immediately start the sync.

           For example, if the last name field is currently mapped with Segment, selecting the **recommended settings** option will override and map the Inflection last name field with Salesforce. If you want to manually map standard or custom fields and start the sync later, choose the option below.
         </Info>

       * **Option 2 | Custom Settings (Start Sync Later)**: If you select this option, the sync will not start immediately. You can use the unified mapping to map your default and custom fields, and then start the sync with Salesforce when you are ready.

         <Info>
           If you select Custom Settings and decide to sync later, by default your Start Sync is disabled. At least one field will need to be mapped for sync to be enabled.

           We recommend mapping all default fields (and any fields that are mandatory in Salesforce for lead/contact creation). You can auto-map the default fields by clicking on the **Auto-map** function in the unified mapping (explanation detailed **in the video**). To know which all are the mandatory fields for respective objects in your Salesforce instance, contact your Salesforce system administrator.
         </Info>

    <Info>
      **Tip:** By default, the Salesforce objects you defined will start syncing to Inflection. However, Inflection will not start **creating** leads or contacts in Salesforce by default. If you want Salesforce leads or contact to be created right after you have started the sync, then select **Custom Settings - Start sync later**, come back to the **Inflection to Salesforce settings** and manage your preferences here. Once you have updated these, then you can start the sync.
    </Info>
  </Accordion>

  <Accordion title="Configure General Settings for a Salesforce Connection">
    Choose what person objects are synced from Salesforce to Inflection.

    <img alt="General Settings showing which person objects sync from Salesforce" />

    Inflection supports syncing of Account objects. To enable Account sync, toggle the switch if it is not already enabled. Read more on account sync here
  </Accordion>

  <Accordion title="Set up Salesforce → Inflection">
    By default, all Salesforce records with a valid email address sync from Salesforce.

    * Where an Inflection contact already exists, the Inflection contact will link to the Salesforce lead or contact record.
    * Where an Inflection contact does not already exist, the Inflection contact will be created and linked to the Salesforce lead or contact record.

      <img alt="Salesforce to Inflection sync settings" />

    Limit which new Salesforce leads/contacts are created in Inflection by configuring **Selective Sync**.

    1. Create a Boolean field in Salesforce on the lead and contact objects called **Sync to Inflection**.
    2. Mark the above field as `true` for all leads/contacts that you want to create in Inflection.

    <Info>
      Note that even where **Sync to Inflection** is `false`, if the record already exists in Inflection, the Salesforce record will be linked to the already-existing Inflection record. Field updates for both records will follow the mapping rules configured in Inflection.
    </Info>

    Once the above steps are complete, in Inflection: toggle **Selective sync for leads** and/or **Selective sync for contacts**. Select the Boolean field from the below list.

    * To selectively sync Salesforce leads, toggle **Selective sync for leads** and pick the Boolean field in Salesforce. Now the lead object in Salesforce will create in Inflection only if `true`.
    * To selectively sync Salesforce contacts, toggle **Selective sync for contacts** and pick the Boolean field in Salesforce. Now the contact object in Salesforce will create in Inflection only if `true`.

    #### Setting Up Sync Rules

    Configure what happens when an object is created, updated or deleted in Inflection.

    <img alt="Sync rules configuration for create, update, and delete actions" />
  </Accordion>

  <Accordion title="Set up Inflection → Salesforce Sync">
    Inflection supports bi-directional sync with Salesforce

    <img alt="Inflection to Salesforce sync settings" />

    * **Define what happens when Leads and/or Contacts are created or updated in Salesforce** - In this setting, you can define what happens when a Salesforce lead or contact is created or updated. Below are the options that you can select from:
      * **Leads**
        * Create a contact in Inflection
        * Do Nothing (default)
      * **Contacts**
        * Create a contact in Inflection
        * Do Nothing (default)
    * **Define what happens when Leads and/or Contacts are deleted in Salesforce** - In this setting you can define what happens when a Salesforce lead or contact is deleted. Below are the options that you can select from:
      * **Leads**
        * Delete the contact in Inflection but keep product data
        * Do Nothing (Default)
      * **Contacts**
        * Delete the contact in Inflection but keep product data
        * Do Nothing (Default)

    <Note>
      **Note:** The action of creation, deletion or do nothing will only take effect from the time this setting is updated. For example:- If the setting for deletion was set to do nothing on day 1 and the setting is updated to delete on day 2, the action of deleting associated Inflection people will only take place for leads/contacts who are deleted in Salesforce since the time this setting was updated on day 2.
    </Note>

    <Info>
      **Converted leads:** When a lead has been converted to a contact in Salesforce and that contact is later deleted, Inflection deletes the contact and does not recreate the person as a lead. This applies regardless of the Lead deletion preference.
    </Info>

    #### Inclusion List

    If you want to control which contacts in Inflection are initially created on Salesforce, you can do so by setting up a Salesforce inclusion list. You can select one of three list types:

    * Dynamic list asset
    * Static list
    * Journey Audience

    Once you define the inclusion list, only contacts who are members of this list will be created on Salesforce. Contacts not in the inclusion list will not be created on Salesforce until they are added to the list.

    <img alt="Salesforce inclusion list settings" />
  </Accordion>

  <Accordion title="Disconnect a Salesforce Connection">
    Disconnecting your salesforce connection in Inflection would remove contact and account field mappings along with custom integration settings, custom object sync settings and field mappings.

    Inflection will still have the data of all the contacts created from Salesforce Lead/Contacts objects along with Account object data.

    <img alt="Disconnect Salesforce connection dialog" />
  </Accordion>
</AccordionGroup>

### Sync Health

The **Sync Health** tab lets you monitor API usage and investigate sync errors between Inflection and Salesforce.

To access Sync Health, go to **Connections > Salesforce** and click the **Sync Health** tab in the sidebar.

The page displays:

* An **API Limit** summary at the top showing your current Salesforce API usage.
* A **Sync Errors** table below it with a count header (e.g. "Sync errors (42)").

<img alt="Sync Health tab showing the API call usage summary and the Sync errors table" />

#### Sync Errors Table

The Sync Errors table shows individual errors from Salesforce sync runs. Each row includes:

| Column | Description |
| - | - |
| Time | When the error occurred. Shows "--" if unavailable. |
| Email | The contact's email address. Click to navigate to the contact's detail page in Inflection. Shows "--" if unavailable. |
| Object name | The Salesforce object type (e.g. Contact, Lead, Account, Opportunity, Campaign Member). |
| Object ID | The Salesforce record ID. For supported object types (Contact, Lead, Account, Opportunity), this is a clickable link that opens the record in Salesforce. For other object types, it displays as plain text. |
| Sync type | The sync operation that failed (e.g. Read, Update, Upsert, Insert, Trigger, Delete). |
| Message | The error message from Salesforce describing what went wrong. |
| Sync run ID | The identifier for the sync run that produced this error. |
| Campaign ID | For Campaign Member errors, the Salesforce Campaign ID extracted from the error context. Shows "--" for non-campaign object types. |
| Campaign name | For Campaign Member errors, the resolved campaign name. Shows "--" for non-campaign object types. |

<Info>
  Cells with no data display "--" instead of blank values.
</Info>

#### Filter Sync Errors

Click the **filter icon** next to the search field to open the filter panel. The following filters are available:

| Filter | Type | Options |
| - | - | - |
| Time | Date range | Preset ranges or custom date range. Select **All time** to view errors from all time periods. |
| Object name | Multi-select | Lead, Contact, Account, Opportunity, Campaign Member, Connection, Campaign, Campaign Member Status, Opportunity Contact Role |
| Sync type | Multi-select | Read, Update, Upsert, Insert, Trigger, Delete |
| Show archived | Toggle | Include or exclude archived sync errors. |

Applied filters appear as chips above the table. Click the **X** on a chip to remove that filter.

<img alt="Filter sync errors panel with the Object name filter options expanded" />

#### Search by Email

Use the **Search by email** field above the table to find errors for a specific contact. Type an email address and the table filters after a short delay. The search field accepts up to 200 characters.

#### Navigate From Sync History

You can jump directly from a sync run to its errors:

1. Go to the **Sync History** tab.
2. Find a sync run that has errors (shown as a red underlined count, e.g. "3 errors").
3. Click the error count. The view switches to the **Sync Health** tab with the Sync Errors table filtered to that sync run. A filter chip "Sync run: \[runId]" appears above the table.
4. To clear the filter and see all errors, click the **X** on the sync run filter chip.

#### CRM Links and Contact Navigation

* **Email column:** Click any email address to navigate to that contact's detail page in Inflection.
* **Object ID column:** For object types that have a CRM record page — Contact, Lead, Account, and Opportunity — the Object ID is a clickable link that opens the Salesforce record in a new browser tab. For other object types (e.g. Connection, Campaign Member Status), the Object ID displays as plain text.

### Opportunity Sync

Inflection supports read-only sync of Salesforce Opportunities and the Contact Roles attached to them. Use Opportunity data to suppress contacts during active deals, segment by deal stage, and target accounts with significant pipeline.

<Info>
  **Pre-requisites:**

  * An active Salesforce connection in Inflection
  * Read access to the Opportunity object on your Salesforce sync user's profile
  * Read access to the Opportunity Contact Role object
</Info>

#### Enable Opportunity Sync

To enable Opportunity sync:

1. Navigate to **Connections** and open your Salesforce connection
2. Go to **Sync Settings** → **General Settings**
3. In the **Opportunity Sync** section, toggle **Enable Opportunity read sync** to ON

<img alt="Enable Opportunity read sync toggle in General Settings" />

<Info>
  Toggling on for the first time triggers a one-time historical backfill of all your existing Opportunity records. Subsequent syncs run on the standard interval and pull only Opportunities updated since the last sync.
</Info>

#### Set the Opportunity Matching Strategy

Your **Opportunity Matching Strategy** controls which contacts a **Has Salesforce Opportunity** filter returns. It is a single workspace-wide setting that applies to every Dynamic List, journey audience, and segment, so deal-aware audiences behave consistently everywhere. Choose the strategy in the same Opportunity Sync settings, below the sync toggle:

* **Deal Team Only:** matches a person to an Opportunity only when they appear as an explicit Contact Role on the deal. Smallest, most precise audience; depends on your Salesforce Contact Role data quality.
* **Salesforce Account Only:** matches anyone Salesforce links to the Opportunity’s account. Broader than Contact Roles but limited to contacts Salesforce has on the account, not Inflection’s own matches.
* **Salesforce + Our Matches:** matches anyone at the Opportunity’s account, including the contact-to-account matches Inflection discovers automatically. Broadest reach across the account.

<img alt="Opportunity Matching Strategy options in the Opportunity Sync settings" />

<Info>
  Workspaces that already use Opportunity sync stay on **Deal Team Only**, the original behavior, so your existing audiences do not change. Switch to a broader strategy whenever you are ready; the change applies on the next list evaluation, with no need to rebuild your lists.
</Info>

#### Map Opportunity Fields

Opportunity fields are mapped in [Unified Mapping](/connections/unified-mapping). Click **Unified Mapping**, and open the **Opportunity Mapping** tab to map the standard and any custom Opportunity fields.

<Info>
  **Opportunity ID**, **Is Deleted**, **Salesforce Created Time**, and **Salesforce Modified Time** are handled automatically. Opportunity ID is the identifier for the record, and the other three are connection-managed fields fetched from Salesforce. None of them can be mapped.
</Info>

#### Browse Synced Opportunities

After sync completes, view all synced Opportunities in the listing page.

To open the listing page:

1. In the left navigation, click the **Database** icon
2. Select **Salesforce Opportunities**

<img alt="Salesforce Opportunities listing page" />

The listing page shows the following columns:

* **Opportunity** — Opportunity name with a link to open the record in Salesforce
* **Account** — The associated Salesforce Account
* **Stage** — Current Opportunity stage (e.g., Prospecting, Closed Won)
* **Amount** — Opportunity amount
* **Close Date** — Expected or actual close date
* **Created Date** — When the Opportunity was created in Salesforce
* **Owner** — Salesforce Owner of the Opportunity
* **Contacts** — Total Contact Roles on the Opportunity in Salesforce
* **Contacts in Inflection** — How many of those Contact Roles are matched to contacts in your Inflection database
* **Last Synced** — When Inflection last refreshed this record from Salesforce

<Tip>
  The **Contacts in Inflection** column is a quick way to gauge how a contact-role-based audience will perform before you build it. A low value relative to **Contacts** indicates Salesforce contact roles that haven't been matched to any Inflection contact yet.
</Tip>

Use the **Search by opportunity name** field or **Add filter** to narrow the listing.

#### View Opportunities on a Contact

Each contact's profile shows the Opportunities they're associated with, alongside their Salesforce Campaign membership and sync status.

To view Opportunities on a contact:

1. Open any contact record
2. Click the **Salesforce** tab in the contact navigation
3. Scroll to the **Salesforce Opportunities** section

The Opportunities table on a contact profile shows:

* **Opportunity Name**, **Account**, **Stage**, **Amount**, **Close Date**

<img alt="Salesforce Opportunities section on a contact profile" />

#### Filter Audiences by Opportunity

Use the **Has Salesforce Opportunity** filter in any Dynamic List, journey audience, or segment to target contacts based on deal data: Stage, Amount, Close Date, Owner, custom Opportunity fields, and more.

<Info>
  For full setup of the filter and best practices on chaining conditions, see [Building Audiences](/database/building-audiences).
</Info>

## Contact Field Mapping

Navigate to **Connections > Contact Fields** to view and update contact field mapping in Inflection.

<img alt="Contact field mapping page in Connections" />

* **Automap Fields:** To revert to the default schema of mapping, click **Automap**.
* **Sync Preference:** Define sync preferences for each field.
  * `Two Way`: Salesforce and Inflection will use the most recent value available. (Default)
  * `Always use Salesforce`: Inflection update with the most recent value from Salesforce.
  * `Prefer Salesforce unless blank`: Inflection will update with the most recent value from Salesforce, unless the Salesforce field is empty. If empty, Inflection will update Salesforce
* **Add New Field:** Click **Edit** and **Add a new field** to create a new contact field in Inflection.

  <Info>
    When creating a custom field and mapping it to Salesforce, ensure that the field type is the same in both platforms. i.e., Mapping an Inflection field that is Boolean to a Salesforce field that is string can result in sync errors.
  </Info>

  * Next, look up & map the corresponding Salesforce fields on the lead and contact that you want to map to your Inflection custom field.
  * Click “Save” to save the mapping. Once save is clicked, the exchange of data will begin between Inflection and Salesforce.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How does Inflection handle duplicate Salesforce records?">
    Inflection sees person records as unique by email address. It will not allow duplicates (with rare exception). If two records exist in Salesforce with the same email address (two leads, two contacts, or a lead and a contact), Inflection will sync with the oldest record.
  </Accordion>

  <Accordion title="What happens when a lead is converted to a contact?">
    Inflection follows the record. The Inflection contact that was synced to a lead continues to sync with the contact it was converted to.

    If the converted contact is later deleted in Salesforce, and your Contact deletion preference is set to delete, Inflection deletes the contact. The person is **not** recreated as a lead from the original lead record.
  </Accordion>

  <Accordion title="How frequently does Inflection sync with Salesforce?">
    Inflection users set this frequency — the most frequent option is every 1 minute. What this means: 1 minute after every complete sync, Inflection/Salesforce sync records that were modified since the previous sync. Note that this frequency refers to the frequency between the syncs; the syncs themselves can take longer than 1 minute.
  </Accordion>

  <Accordion title="Can I sync custom Opportunity fields?">
    Yes. Map custom Opportunity fields on the **Opportunity Mapping** tab in [Unified Mapping](/connections/unified-mapping), the same way you map Account or Contact custom fields.
  </Accordion>

  <Accordion title="How are Opportunities linked to my Inflection contacts?">
    Inflection links Opportunities to contacts using your workspace’s **Opportunity Matching Strategy**, set in your Salesforce connection’s Opportunity Sync settings. Choose **Deal Team Only** to match only contacts with an explicit Contact Role, **Salesforce Account Only** to match contacts linked to the account in Salesforce, or **Salesforce + Our Matches** to also include the contacts Inflection matches to the account automatically. Workspaces that already had Opportunity sync stay on **Deal Team Only** until you change it.
  </Accordion>

  <Accordion title="Can I write back to Salesforce Opportunities or trigger journeys on stage changes?">
    Opportunity sync is read-only, and Opportunity-based journey triggers and conversion events are planned for a future release. For now, use scheduled journeys with Dynamic List audiences that filter on Opportunity Stage.
  </Accordion>

  <Accordion title="Will my Dynamic List audiences change when matching strategy is released?">
    No. Workspaces that already use Opportunity sync stay on **Deal Team Only**, the same behavior as before, so your existing audience counts will not change. To reach more contacts at an account — for example, to suppress an entire account during an active deal — switch your **Opportunity Matching Strategy** in the Salesforce connection’s Opportunity Sync settings.
  </Accordion>
</AccordionGroup>


# Segment
Source: https://docs.inflection.io/connections/segment

Connect product data from your CDP to Inflection for targeting and personalization. Send marketing activities from Inflection to Segment for analytics.

Segment is a customer data platform (CDP) that allows businesses to collect, clean, and control their customer data. It provides a single API to track customer data across multiple platforms and devices, and sends that data to various tools for analytics, marketing, and data warehousing.

Inflection provides a way to send and receive product events from Segment. You can connect Segment to Inflection via the following options:

* **Segment as a Source:** Send product events from Segment to Inflection, where they can be used for targeting and segmentation. (These can be product events from your website, application, mobile devices, etc.).
* **Segment as a Source and Destination**: In addition to the above, send Inflection events to Segment. (These include marketing activities such as delivered, opened, clicked, bounced an email.)

## Segment as a Source

Inflection can receive `identify`, `track`, and `group` calls from Segment.

* User information from `identify` calls map to Inflection contacts.
* Workspace information from `group` calls map to Inflection orgs.
* Activities and activity attributes from `track` calls map to product activities.

## Segment as a Destination

Inflection can export marketing activities (email events, journey activity, and form & inbound webhook submissions) directly to Segment. This makes it easier for your marketing, ops, and data teams to create reports and run analytics in their BI tools.

The events and attributes are supported:

| **Event Type** | **Events** | **Attributes** |
| - | - | - |
| **Email** | **Delivered**<br />**Opened**<br />**Link Clicked**<br />**Bounced**<br />**Spam**<br />**Unsubscribed** | **Contact**: `Email`, `Person ID`, `Product User ID`, `Org ID`<br />**Email Asset**: `Email Asset ID`, `Email Asset Name`, `Email Subject`, `Email Asset Link URL`, `Email event Detail`<br />**Journey**: `Journey ID`, `Journey Name`, `Journey Run ID`<br />**Timestamps**: `original_timestamp` (time of the event), `timestamp` (time at which the event was ingested into Segment)<br />**Engagement**: `is_bot` (Opened, Link Clicked, and Unsubscribed events) |
| **Journey Lifecycle** | **Journey Entered**<br />**Journey Completed**<br />**Journey Exited** | **Contact**: `Email`, `Person ID`, `Product User ID`, `Org ID`<br />**Journey**: `Journey ID`, `Journey Name`, `Run ID`, `Journey Type`, `Trigger Event ID`, `Trigger Source`<br />**Timestamps**: `original_timestamp` (time of the event), `timestamp` (time at which the event was ingested into Segment) |
| **Forms & Inbound Webhooks** | **Form Submitted**<br />**Inbound Webhook Submitted** | **Contact**: `Inflection Contact ID`, `Contact Email`<br />**Timestamps**: `Datetime` |

<Tip>
  All ID columns are accompanied by human-friendly attributes to make querying and dash-boarding easy.
</Tip>

<Info>
  Email Opened, Email Link Clicked, and Email Unsubscribed events include an `is_bot` property. It is `true` when Inflection detected the activity as automated, such as a security scanner or link checker. Inflection sends all events to Segment, including flagged ones. Filter on `is_bot` in your downstream tools to report on real engagement only. Opens from Apple Mail Privacy Protection and the Gmail image proxy are not flagged.
</Info>

<Info>
  **Journey Completed vs. Journey Exited**: **Journey Completed** is triggered when a record finishes all flow steps in the journey and reaches the end. **Journey Exited** is triggered when a record meets the journey's exit criteria and exits the journey.
</Info>

<Info>
  Email events currently include both the legacy `campaign_id`, `campaign_name`, and `campaign_run_id` properties and their replacements `journey_id`, `journey_name`, and `journey_run_id`. We will be removing `campaign_*` properties in future releases. Update any reports or downstream models that reference the `campaign_*` properties to use the `journey_*` properties.
</Info>

### Example Payloads

Email event:

```javascript theme={null}
analytics.track('Email Opened', {
  'person_id': '1a6d7b02a2f6ba48f0e75d7948066090',
  'email': 'jane@acme.com',
  'original_timestamp': '2026-07-21T09:29:30.000Z',
  'email_asset_id': '6a59ca2f799c0392d414937c',
  'journey_id': '6a5dcf5b37610845316e5b0b',
  'journey_name': 'Onboarding nurture',
  'journey_run_id': '6a5f3bdcca48083b271bb829',
  'campaign_id': '6a5dcf5b37610845316e5b0b',      // will be deprecated in future
  'campaign_name': 'Onboarding nurture',          // will be deprecated in future
  'campaign_run_id': '6a5f3bdcca48083b271bb829',  // will be deprecated in future
  'is_unique_open': true
})
```

Journey lifecycle event:

```javascript theme={null}
analytics.track('Journey Entered', {
  'person_id': '1a6d7b02a2f6ba48f0e75d7948066090',
  'product_user_id': 'u_204981',
  'org_id': 'org_5521',
  'email': 'jane@acme.com',
  'original_timestamp': '2026-07-21T17:02:51.569Z',
  'journey_id': '6a5f9a93fb88b0705b53957d',
  'journey_name': 'Onboarding nurture',
  'run_id': '6a5fa62577f3b0289092e3b7',
  'journey_type': 'batch',
  'trigger_event_id': '',
  'trigger_source': ''
})
```

Form Submitted event:

```javascript theme={null}
analytics.track('Form Submitted', {
    'person_id': '1d72628148f5e9sdfsc01cf30515',
    'email': 'jane@acme.com',
    'original_timestamp': '2026-07-21T17:00:58.569Z',
    'form_id': '6a61cfsfdds0c22656feace3',
    'form_name': 'Contact Form',
    'source': 'generic-form',
    'api_key': '0999w9x9ewew0990xxxxxxxx',
    'submission_id': '6e392c9b-accb-4e2b',
    'submission_data': {
        'unsubscribe': true,
        'email': 'jane@acme.com',
        'date': '2026-07-28T13:36:00.000Z',
        'first_name': 'jane'
    }
})
```

## Set up & Configuration

### Segment as a Source

1. Navigate to Connections and select **Add new connection**

   <img alt="Connections page in Inflection with the Add new connection button" />

2. Select **Segment as a Source** or **Segment as a Source and Destination**.

   <img alt="Choosing between Segment as a Source and Segment as a Source and Destination" />

3. Copy the provided API key into your Segment destination and click **Save** in Inflection.

   <img alt="Segment connection screen in Inflection showing the API key to copy" />

### Segment as a Destination

1. From the Source catalog page in the Segment App, select **Inflection**.
2. Get the API write key generated by Segment, and paste it in inflection.
3. The data will be sent to Segment and you will be able to see those events in Segment.

## Monitoring

Once configured, monitor incoming data in **Connections** > **Segment** > **Sync Activity**.

<img alt="Segment Sync Activity view showing incoming data" />

## Mapping

For events and attributes coming from Segment to be usable in Inflection, you must complete mapping.

### Segment Events to Inflection

Navigate to **Connections** > **Product Data Explorer**. The page lists everything Inflection has received from Segment in two tables:

* **User properties** shows the `identify` and `group` calls, with when each was first and last seen, how many times it occurred, and how many properties it carries. Click **identify** or **group** to see the properties available for mapping.
* **Track** shows every track event, with the same first seen, last seen, and occurrence counts, plus an **Org ID Property** column and a **Status** toggle.

Use the **Status** toggle to enable or disable an event. When an event is enabled, it is available for segmentation, list building, and personalization.

Use **Search events/properties** and **Add filter** to find an event, and **Export** to download the event list.

<img alt="Screenshot 2026 09 26 At 11 12 10 AM 1" />

#### Org ID Property

The org ID property controls which event property supplies the org for each product activity record. It is set in two places:

* **Default Org ID property**, above the Track table, is the connection-level default. For Segment it is **Use Segment group ID** unless you change it. Click **Edit** to choose a different property.
* **Org ID Property** column: each event shows **Connection default** or the property that overrides it. To set an override, click the event name to open its details, choose a property from the **Org ID property** dropdown, and click **Save**. Choose **Use connection default** to clear the override.

Events where the configured property is missing or empty are recorded without an org and do not match org-requiring filter conditions in dynamic lists.

<img alt="Event Details page with the Org ID property dropdown listing Use connection default and event properties" />

### Segment User and Org Attributes to Inflection

Map user and org attributes in [Unified Mapping](/connections/unified-mapping). Traits from `identify` calls are mapped on the **Product User Mapping** tab, and traits from `group` calls on the **Organization Mapping** tab. On the tab, click **Edit mapping**, find the field, click **+ Add source**, select **Segment**, and choose the trait to read from. See [Map a Field to a Source](/connections/unified-mapping#map-a-field-to-a-source) for the full steps.

To see which traits Segment has sent, click **identify** or **group** in the **User properties** table on the **Product Data Explorer** screen.

Once mapped, these attributes are available for segmentation, list building, and personalization.

Note that to be valid:

* Identify calls require user ID and email address.
* Group calls require user ID and group ID.

### Inflection Events to Segment

1. Navigate to **Connections** > **Segment** and open the **Destination Settings** tab.
2. Click **Edit** in the top-right corner.
3. Select the Inflection events to send back to Segment:
   * Email events: **Email Delivered**, **Email Opened** (optionally **Send Unique opens only**), **Email Bounced**, **Email Reported as Spam**, **Email Clicked** (optionally **Send Unique clicks only**), and **Email Unsubscribes**.
   * **Submission Events**: **Form Submitted** and **Webhook Received**.
   * **Journey Lifecycle Events**: **Journey Entered**, **Journey Completed**, and **Journey Exited**. Select these to send an event to Segment when a contact enters, completes, or exits a journey.
4. Save your changes.

<img alt="Destination Settings tab with Email, Submission, and Journey Lifecycle event sections" />

### Map Segment Identify Traits to Contact Fields

Map the traits coming from your Segment identify calls directly to Inflection contact fields.

1. Navigate to **Unified Mapping** > **Contact Fields**.
2. Locate the Inflection contact field you want to populate from Segment. To add a new one, click **+ Add new field**.
3. In the **Source** column, select **Segment**.
4. In the **Contact property** column, select the Segment identify trait to map (e.g., user\_name, email, organisation\_id). The dropdown lists every trait Inflection has seen on a recent identify call for your connection.
5. Click **Save**.

<img alt="Contact Fields screen mapping Segment identify traits to Inflection contact fields" />

The **Lead property** column stays blank for Segment-sourced fields it only applies when the source is Salesforce. The **Sync preference** column defaults to **Prefer Connection** for Segment, meaning Inflection uses the most recent value coming from your Segment identify calls.

<Info>
  When creating a new custom field for Segment data, make sure the field type matches the trait type in your Segment payload. Mapping an Inflection field that is Boolean to a Segment trait that is a string can result in sync errors.
</Info>

## Segment Connection FAQs

<AccordionGroup>
  <Accordion title="How does Inflection map email addresses from Segment identify calls?">
    Inflection maps email addresses from Segment identify calls using the following priority:

    1. Top-level email field from the identify call payload
    2. Email extracted from traits (properties) if top-level email does not exist
    3. Email extracted from the `userId` field if neither above exists

    When the header email and traits email differ, Inflection saves the traits email as a property on the user associated with the header email.
  </Accordion>

  <Accordion title="Are contacts only created in Inflection through Segment Identify calls? Can they be created through Segment events (track calls)?">
    A Segment Identify call is required to create a new contact in Inflection. A new contact cannot be created directly from a Segment track call.

    If product users are created in Inflection through a data warehouse connection and the product user IDs match the user IDs in Segment track calls, the track call will attach to the existing user or contact record without requiring a Segment identify call.
  </Accordion>

  <Accordion title="Does Inflection support nested JSON properties from Segment?">
    Inflection will treat nested JSON properties as a string.
  </Accordion>
</AccordionGroup>


# Unified Mapping
Source: https://docs.inflection.io/connections/unified-mapping

Control where every field of your customer data comes from, how conflicts between sources resolve, and which fields write back to Salesforce.

<Info>
  This feature is in beta release. If you don't have access to this feature and would like to get access, please contact your CS team.
</Info>

## Control Where Your Data Comes From

Unified Mapping gives you one place to control where every field of your customer data comes from. Each field on each entity reads from one or more sources: Salesforce, your data warehouse, Segment, Amplitude and Inflection resolves them into a single unified record (the golden record) that powers your dynamic lists, journeys, tokens, and personalization across the platform.

<Info>
  You need admin access to your Inflection workspace to change mapping. Connect at least one source (Salesforce, a data warehouse, Segment, or Amplitude) before configuring mapping for it.
</Info>

## Open the Mapping Page

Click **Connections** in the left navigation, then click **Unified Mapping.**

<Frame>
  <img alt="Screenshot 2026 08 12 At 6 11 58 PM" />
</Frame>

The Mapping page has one tab per entity: **Contact Mapping**, **Account Mapping**, **Opportunity Mapping**, **Product User Mapping**, **Organization Mapping**, and **Product User Organization Mapping** plus a **Change Log**. Each tab lists the entity's fields, their sources, and their settings. Click **How mapping works** in the top bar any time for an in-product explainer.

## The Six Entities

| Entity | What it holds | Sources you can map |
| - | - | - |
| Contact | Your marketable people and their attributes | Salesforce (Contact and Lead), data warehouse, Segment, Amplitude |
| Account | CRM accounts | Salesforce, data warehouse |
| Opportunity | Salesforce opportunities | Salesforce |
| Product User | Users of your product | Segment, data warehouse |
| Organization | Product workspaces or organizations your users belong to | Segment, data warehouse |
| Product User Organization Mapping | How your product users map to organizations | Data warehouse, Segment |

## How Mapping Works

### The Unified Record

Each field reads from one or more sources. Inflection resolves the sources into one value per field, the unified record, and that value is what you filter on, personalize with, and trigger from everywhere in Inflection.

<Frame>
  <img alt="Umv2high (1)" />
</Frame>

### Backfill and Resolution

Resolution runs when a source sends an update. Here's which changes reach back into records you already have:

**Applies from the next source update**

| Change | What happens |
| - | - |
| Reordering sources | New order is used the next time a source sends an update |
| Switching resolution mode (Priority ↔ Last wins) | Existing values are kept as-is |
| Toggling accept nulls | Only affects future updates from that source |
| Toggling editing in Inflection | Only affects edits made after the change |

**Backfills existing records**

| Change | What happens |
| - | - |
| Adding or repointing a Salesforce source | All Salesforce records are re-read; unified values change where Salesforce wins |
| Adding a Segment source | The last 30 days of Segment events are replayed; unified values change where Segment wins. Anything older than 30 days is not backfilled |
| Triggering a resync on a data warehouse connection | Changing mapping here does not resync a data warehouse connection. Updating the warehouse mapping triggers a resync |

<Info>
  Segment backfill might take some time. If you don't see your backfilled values within 24 hours of adding a Segment source, please contact your CS team.
</Info>

### Sources and Priority

Every connection is its own source block. The Salesforce block contains both **Contact** and **Lead** properties for Person fields; each data warehouse connection, Segment, and Amplitude are separate blocks. When a field has more than one source, choose how conflicts resolve:

* **Priority order:** the first source in the list that has a value wins. Reorder sources with the arrows next to each source number. <img alt="A field mapped to Salesforce, Segment, and Amplitude with reorder arrows next to each source number" />
* **Last wins:** the newest change across all sources wins.

Contact and Account fields support both modes. Product User, Organization, and Product User Organization Mapping fields resolve with last wins. Opportunity fields have a single source (Salesforce).

### Accept Null Values

By default, when a source's value for a field is blank or null, that source is skipped and the next source that has a real value wins instead. Turn on **Accept null values** for a source to let its blank value win its priority slot and clear the field, which is useful when an empty value is a meaningful signal. Leave it off for sources like event streams where blanks are just noise.

<img alt="Accept null values toggle on a source with its explanatory tooltip" />

### Editing in Inflection

The **Editing** toggle controls whether a field can be changed from inside Inflection: forms, manual edits, CSV uploads, Journeys, Webhooks, and Data Normalization. When on, Inflection edits compete with the sources on a last-write-wins basis. Turn it off to make the field read-only on all Inflection surfaces.

<Info>
  Manual edits always follow last-wins; they are never part of the priority order.
</Info>

### Write Back to Salesforce

The **Write back** toggle sends the unified value back to Salesforce. It requires Salesforce to be one of the field's sources, and when the field uses Priority order, Salesforce must stay at the top of the order. The page enforces this and shows **Salesforce must stay at the top while write-back is enabled**. Blank values are never written back: Inflection only updates a Salesforce field when the unified record has a non-empty value.

<img alt="A field with write back enabled showing the message that Salesforce must stay at the top of the priority order" />

## Map a Field to a Source

1. On the entity's tab, click **Edit mapping**.
2. Find the field. Use **Search fields** to filter the list.
3. Click **+ Add source** on the field row.
4. Select the connection block (for example, **Salesforce**, **Segment**, or your warehouse connection).
5. Select the source property to read from. For Salesforce Person fields, set the **Contact** and **Lead** properties.
6. Optionally turn on **Accept null values** for the source.
7. Click **Save changes**.

To remove a single source from a field, click the **×** on its source block. The field itself and its current values are preserved, and the remaining sources continue to resolve.

## Create a Custom Field

1. Click **+ Add new field** on the entity's tab.
2. Enter a **Field name**. Names are case- and space-insensitive.
3. Select a **Field type** — String, Number, Boolean, or Datetime.
4. Optionally add a **Description** (up to 300 characters) so your team and Inflection's AI agents know what the field represents.
5. Click **Add field**.

<Info>
  Field names must start with a letter, be 250 characters or fewer, and be unique per entity. Names ending in `_pom` are reserved for Product User Organization Mapping fields.
</Info>

## Delete a Custom Field

Only custom fields can be deleted: system, default, and Inflection-managed fields are protected. Deletion is blocked while the field is in use by journeys, segments, exports, or forms, while changes are still saving, or while another delete is in progress. Inflection runs a dependency check and asks for confirmation before removing anything.

## Field Descriptions and Insights

Click **Add description** or **Edit description** under a field name to document what the field represents. Descriptions appear here and in **Insights from data dictionary** wherever you build filters.

Click the book icon next to a field name to open **Insights from data dictionary** for that field — how many records have a value (populated count and percentage) and a searchable list of distinct values sorted by frequency.

<img alt="Insights from data dictionary panel showing populated count and distinct values for the Title field" />

## Track Mapping Changes

Click **Change Log** to see every mapping change in the workspace — date and time, entity, change type (for example **Field created** or **Mapping changed**), the field, and who changed it. Filter by field name or date range, and click **Show details** on any row.

<img alt="Change Log tab listing mapping changes with date, entity, change type, field, and who changed it" />

## Fields You Can't Map

* **Identity fields** (marked **Identifier**) uniquely identify records and cannot be mapped — for example Person **Inflection ID** and **Email**, Account **Account Id**, and Opportunity **Opportunity ID**.
* **System fields** are managed by Inflection and cannot be edited.
* **Inflection-managed fields**, such as account scoring fields, always have Inflection as their locked source — no external source can be mapped to them.
* **Unsubscribed** always allows Inflection edits, and when Salesforce is one of its sources it always writes back — this keeps opt-outs consistent everywhere.

## Common Use Cases

* **Keep Salesforce authoritative with product data as backup.** Put Salesforce first in the Priority order and Segment second — Salesforce wins whenever it has a value, and Segment fills the gaps.
* **Let the freshest system win.** Use Last wins on fields fed by both your warehouse and product events so the most recent update always shows.
* **Lock a field against manual changes.** Turn Editing off to make a warehouse-owned field read-only in forms, CSV imports, and manual edits.
* **Push enriched values back to your CRM.** Map a field from your warehouse, turn on Write back, and Inflection keeps the Salesforce field up to date.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="What happened to Auto-map?">
    Auto-map was removed. Fields are mapped explicitly on the Mapping page, so what you see there is always exactly what is configured.
  </Accordion>

  <Accordion title="What happened to Sync Preference (Two Way, Always use Salesforce, Prefer Connection)?">
    Sync preferences were replaced by the source, resolution, editing, and write-back model. The closest equivalents: **Two Way** is a Salesforce source with Editing and Write back on; **Always use Salesforce** is Salesforce as the only (or top-priority) source with Editing off; **Prefer Connection** is Last wins.
  </Accordion>

  <Accordion title="Can I use Priority order on Product User, Organization, or Product User Organization Mapping fields?">
    Not yet. These entities resolve with Last wins for now; priority resolution is planned for a future release.
  </Accordion>

  <Accordion title="Can I see which source produced the current value for a specific person?">
    Not yet — a per-record source view is planned. The Change Log shows every mapping configuration change today.
  </Accordion>

  <Accordion title="Are Segment field types validated?">
    No. Segment traits carry no type information, so a type-mismatched Segment mapping saves without error and can fail later at sync time. Keep the Inflection field type matched to the trait's actual type.
  </Accordion>

  <Accordion title="My write-back saved but values aren't landing in Salesforce. Why?">
    Write permission on the Salesforce field is not checked when you save the mapping. If the Salesforce field isn't updateable for the integration user, writes fail at sync time — check the field's accessibility in Salesforce.
  </Accordion>

  <Accordion title="Do data warehouse fields still need a second mapping step?">
    The current warehouse flow is unchanged: sync the table, then map its columns as sources. A single-step flow is planned.
  </Accordion>

  <Accordion title="What happens to my existing mappings?">
    Existing mappings are converted automatically and keep their behavior. A small number of patterns need cleanup during conversion — for example a Salesforce field mapped to the wrong entity's object, or a write-back where Salesforce isn't the top source. The Inflection team coordinates any cleanup with you.
  </Accordion>

  <Accordion title="Why do I see &#x22;Unable to validate mapping — please check your connection&#x22;?">
    The referenced connection is errored, deleted, or mid-setup. Fix the connection under **Connections > Data Connections**, then save the mapping again. If the provider is temporarily unreachable you'll see a transient error instead — just try again.
  </Accordion>
</AccordionGroup>


# BigQuery Setup and Configuration
Source: https://docs.inflection.io/connections/warehouses/bigquery

Set up BigQuery as an Inflection data source and export destination.

## Export Inflection Data to BigQuery

For information on tables and schemas that inflection exports to BigQuery, please read this

<AccordionGroup>
  <Accordion title="Set up Export to BigQuery in Inflection">
    These steps need to be run by someone with access to

    1. Go to **Connections → Data Connections**, then click **Add new connection**.

       <img alt="Add new connection button on the Data Connections page" />

    2. **Choose your platform**: Select **BigQuery** as your destination platform.

    3. **Select connection type**: Choose **Export Data to BigQuery**.

       <img alt="Choosing BigQuery as the platform and Export Data to BigQuery as the connection type" />

    4. **Enter your BigQuery credentials**
       * Connection name - A human friendly name for this **BigQuery** connection
       * Google Project Id - Project id of the GCP
       * Dataset - Name of the dataset where inflection should write data

    5. Click **Create Connection** to set up the connection. Note that syncing will NOT BEGIN and connection will be in INACTIVE state until the credentials and destination tables are created Inflection.
  </Accordion>

  <Accordion title="Set up BigQuery to accept Inflection Data">
    ### Verifying access to sync data

    Inflection requires specific permissions to sync data.

    * On your Google Cloud console, ensure that you've selected the project containing your BigQuery Instance.
    * From the navigation menu, go to IAM & Admin Panel. Click on "Grant Access".
    * Then, add the following service account as principle and add the specified role.
    * This will help us read the data and sync the data to inflection.

    **Principal:** [inflection-datawarehouse-write@silken-fortress-380708.iam.gserviceaccount.com](mailto:inflection-datawarehouse-write@silken-fortress-380708.iam.gserviceaccount.com)

    **Roles:**

    ```json theme={null}
    bigquery.jobs.create, bigquery.tables.create, bigquery.tables.delete, 
    bigquery.tables.get, bigquery.tables.getData, bigquery.tables.update, 
    bigquery.tables.updateData
    ```
  </Accordion>

  <Accordion title="Submit Setup for Activation">
    Once your credentials are saved and your data team gave above accesses, your setup is complete.

    At this point:

    * Inflection's team will validate the setup and activate the sync for you.
    * No additional steps are required from your side.
      * Optionally, you may test or delete the connection at this stage
    * You will be notified once the sync has started and data is being sent.

    <Info>
      Activation may take up to two business days.
    </Info>
  </Accordion>
</AccordionGroup>

<img alt="Export to BigQuery connection created and pending activation" />

And that's it! Once you are set up, you can monitor sync health by following our guide here

## Import Product Activity from BigQuery to Inflection

For information on generic import guidelines, please read this.

<AccordionGroup>
  <Accordion title="Set up Inflection to read from BigQuery">
    1. In the Inflection UI, select Connections on the left sidebar > "Data Connections" > "Add new Connection"

       <img alt="Add new Connection option under Data Connections in the Inflection UI" />

    2. Copy the dataset name and select Continue to add required permissions.

       <img alt="Dataset name shown with Continue button to add required permissions" />

    3. Name your connection in the Connection name field, add your Project id, and save the connection:

       <img alt="Connection name and Project id fields for the BigQuery connection" />
  </Accordion>

  <Accordion title="Set up BigQuery to allow Inflection reads">
    The below permission needs to be given to our service account by the customers on their project:

    1. `bigquery.dataViewer`: For us to read the data. Cloud console command:

    ```shell theme={null}
    gcloud projects add-iam-policy-binding <project_id> --member serviceAccount:<inflection_service_account_email> --role roles/bigquery.dataViewer
    ```

    2. `biguquery.user`: For us to read the dataset's metadata and list tables in the dataset, and also to run export job. Cloud console command:

    ```shell theme={null}
    gcloud projects add-iam-policy-binding <project_id> --member serviceAccount:<inflection_service_account_email> --role roles/bigquery.user
    ```

    3. `bigquery.dataEditor`: This role has to be provided to the service account on the dataset `inflection`. This is for us to calculate diffs within the dataset `inflection`. Cloud console command:

    ```shell theme={null}
    bq query --nouse_legacy_sql 'GRANT `roles/bigquery.dataEditor` ON SCHEMA inflection TO "serviceAccount:<inflection_service_account_email>"'
    ```
  </Accordion>
</AccordionGroup>


# Databricks Setup and Configuration
Source: https://docs.inflection.io/connections/warehouses/databricks

Set up Databricks as an Inflection data source and export destination.

## Export Inflection Data to Databricks

For information on tables and schemas that inflection exports to Databricks, please read this

<AccordionGroup>
  <Accordion title="Set up Export to Databricks in Inflection">
    These steps need to be run by someone with access to

    1. Go to **Connections → Data Connections**, then click **Add new connection**.

       <img alt="Add new connection button on the Data Connections page" />

    2. **Choose your platform**: Select **Databricks** as your destination platform.

    3. **Select connection type**: Choose **Export Data to Databricks**.

       <img alt="Choosing Databricks as the platform and Export Data to Databricks as the connection type" />

    4. **Enter your DW credentials**

       Give a name for your data warehouse connection and fill in your credentials.

       * For **Databricks**: Enter client ID, client secret, host, catalog, schema and HTTP path.

    <Warning>
      Make sure the service principal used for Inflection access has at least the following minimum permissions on the target catalog for data export.

      <img alt="Minimum permissions required on the target catalog for the Inflection service principal" />
    </Warning>

    2. Click **Create Connection** to set up the connection. Note that syncing will NOT BEGIN and connection will be in INACTIVE state until the credentials and destination tables are validated by your Inflection team.
  </Accordion>

  <Accordion title="Set up Databricks to accept Inflection Data">
    We provide a custom SQL script tailored to your configuration. You'll need to run this script to create the export tables in your DW.

    <img alt="Sample SQL. Do not use this directly. Please refer to the SQL shown on inflection UI for your connection" />

    The script creates tables with the necessary structure and permissions (INSERT, UPDATE, DELETE) for Inflection to write data.
  </Accordion>

  <Accordion title="Submit Setup for Activation">
    Once your credentials are saved and your data team has created the required tables in your warehouse, your setup is complete.

    At this point:

    * Inflection's team will validate the setup and activate the sync for you.
    * No additional steps are required from your side.
      * Optionally, you may test or delete the connection at this stage
    * You will be notified once the sync has started and data is being sent.

    <Info>
      Activation may take up to two business days. Please ensure your data team notifies you once your tables are set up in your data warehouse.
    </Info>
  </Accordion>
</AccordionGroup>

And that's it! Once you are set up, you can monitor sync health by following our guide here.

## Import Databricks Data to Inflection

Inflection can read data directly from your Databricks workspace using **Databricks-to-Databricks Delta Sharing**. You stay fully in control of what's shared; Inflection only receives read-only access to the specific tables you choose.

This instructions below walk you through:

1. Setting up a **Delta Sharing share** in your Databricks Unity Catalog.
2. Granting Inflection access using our **metastore identifier**.
3. Configuring the **Databricks connection** inside Inflection.

<AccordionGroup>
  <Accordion title="Pre-requisites">
    To complete this setup, you'll need:

    * A **Unity Catalog–enabled** Databricks workspace.
    * Permissions to:
      * Create and manage **shares** and **recipients** in Unity Catalog.
      * Grant `SELECT` access on the tables/schemas you want to share.
    * The Inflection **Databricks metastore identifier**:

      ```text theme={null}
      aws:us-west-2:7bd7c54d-5bf4-41c6-b6c8-752437ed524d
      ```
  </Accordion>

  <Accordion title="Part 1: Configure Databricks">
    ### Step 1: Choose what to share

    Decide which objects Inflection should have access to:

    * One or more **tables**, for example:
      * `your_catalog.your_schema.product_activity`
      * `your_catalog.your_schema.contacts`
    * Or an entire **schema** in a catalog (e.g. `your_catalog.your_schema`).

    You can add or remove objects from the share later; no need to get it perfect on day one.

    ### Step 2: Create a Share in Unity Catalog

    You can create the share using the **Catalog Explorer**.

    1. In Databricks, open the **Catalog** panel.

    2. Click the **gear icon (⚙)** and choose **Delta Sharing**.

    3. Under **Shared by me**, click **Create share** / **Share data**.

    4. Enter a **Share name**, for example:

       ```text theme={null}
       inflection_share
       ```

    5. Click **Save and continue**.

    6. On the next step, add the tables/schemas you want to share to Inflection, then save.

    You'll use this exact **Share name** again when you configure the connection in Inflection.

    ### Step 3: Create a Databricks Recipient for Inflection

    Next, create a **recipient** that represents Inflection's Unity Catalog metastore, using the identifier we provided.

    1. In Databricks, go to **Catalog → ⚙ Delta Sharing**.

    2. Go to the **Shared by me** tab.

    3. Click **New recipient**.

    4. Choose a **Recipient name**, for example:

       ```text theme={null}
       inflection_recipient
       ```

    5. For **Recipient type**, select **Databricks**.

    6. In the **Databricks metastore identifier** field, paste:

       ```text theme={null}
       aws:us-west-2:7bd7c54d-5bf4-41c6-b6c8-752437ed524d
       ```

    7. Save the recipient.

    ### Step 4: Grant the Share to Inflection

    Finally, grant the share to the recipient you just created.

    1. In **Catalog → ⚙ Delta Sharing → Shared by me**, click your share (`inflection_share`).
    2. Open the **Recipients** tab.
    3. Add `inflection_recipient` and grant it access.
  </Accordion>

  <Accordion title="Part 2: Configure the Connection in Inflection">
    ### Step 5: Open the Databricks Connector in Inflection

    1. Log in to your Inflection workspace.
    2. Navigate to **Connections → Data Connections**.
    3. Click **+** / **Add connection** to open the **Connection Marketplace**.
    4. Under **Data Warehouse**, choose **Databricks**.

       <img alt="Databricks tile under Data Warehouse in the Connection Marketplace" />

    ### Step 6: Choose sync type

    On the **"Setting up Databricks connection"** screen:

    1. Select **Read Databricks Data**
    2. Click **Enter connection details**.

       <img alt="Read Databricks Data option on the Setting up Databricks connection screen" />

       <img alt="Databricks connection details form" />

    ### Step 7: Mapping DW to Inflection Objects

    Use the document below to Map Inflection Tables to Databricks:

    the related Help Center article
  </Accordion>
</AccordionGroup>

And that's it! Once you save the mapping and you connection is active, you can monitor the sync health. If you encounter any issues, reach out to the Inflection team.


# Redshift Setup and Configuration
Source: https://docs.inflection.io/connections/warehouses/redshift

Set up Amazon Redshift as an Inflection data source and export destination.

## Export Inflection Data to Redshift

For information on tables and schemas that Inflection exports to Redshift, please read this

<AccordionGroup>
  <Accordion title="Set up Export to Redshift in Inflection">
    These steps need to be run by someone with access to

    1. Go to **Connections → Data Connections**, then click **Add new connection**.

       <img alt="Add new connection button on the Data Connections page" />

    2. **Choose your platform**: Select **Redshift** as your destination platform.

    3. **Select connection type**: Choose **Export Data to Redshift**.

       <img alt="Choosing Redshift as the platform and Export Data to Redshift as the connection type" />

    4. **Whitelist IPs**

       For Redshift connection, you need to whitelist given IPs in your AWS dashboard before proceeding to setup page

       <img alt="IP addresses to whitelist in your AWS dashboard" />

    5. **Enter your Redshift credentials**

       Give a name for your data warehouse connection and fill in your credentials.

       * Account name - a human-friendly name for this connection
       * Username, password - service account credentials for redshift
       * Database, schema and port - name of the database, schema and port to be used by Inflection.

    6. Click **Create Connection** to set up the connection. Note that syncing will NOT BEGIN and connection will be in INACTIVE state until the credentials and destination tables are validated by your Inflection team.
  </Accordion>

  <Accordion title="Set up Redshift to accept Inflection Data">
    We provide a custom SQL script tailored to your configuration. You'll need to run this script to create the export tables in your DW.

    <img alt="Sample SQL. Do not use this directly. Please refer to the SQL shown on inflection UI for your connection" />

    The script creates tables with the necessary structure and permissions (INSERT, UPDATE, DELETE) for Inflection to write data.
  </Accordion>

  <Accordion title="Submit Setup for Activation">
    Once your credentials are saved and your data team has created the required tables in your warehouse, your setup is complete.

    At this point:

    * Inflection's team will validate the setup and activate the sync for you.
    * No additional steps are required from your side.
      * Optionally, you may test or delete the connection at this stage
    * You will be notified once the sync has started and data is being sent.

    <Info>
      Activation may take up to two business days. Please ensure your data team notifies you once your tables are set up in your data warehouse.
    </Info>
  </Accordion>
</AccordionGroup>

## Import Product Activity from Redshift to Inflection

For information on generic import guidelines, please read this

<AccordionGroup>
  <Accordion title="Set up Inflection to read from Redshift">
    1. In the Inflection UI, select Connections on the left sidebar > "Data Connections" > "Add new Connection". Select Redshift to enter connection details and proceed with the setup workflow.

       <img alt="Add new Connection option under Data Connections in the Inflection UI" />

    2. Copy the IPs to whitelist in your AWS dashboard. Select "I've Whitelisted the IPs" once you have completed that step.

       <img alt="IPs to whitelist with the I've Whitelisted the IPs confirmation" />

    3. Name your connection in the Connection name field, add your Redshift connection details, and save the connection:

       * Host
       * Port
       * Database
       * User
       * Password

       <img alt="Redshift connection details form" />
  </Accordion>

  <Accordion title="Set up Redshift to allow Inflection reads">
    We need specific permissions to be granted for Redshift sync to work:

    1. Create a user to be used by inflection to read and export data. This user should be created with password (Ref: [https://docs.aws.amazon.com/redshift/latest/dg/r\_CREATE\_USER.html](https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_USER.html))

    2. Inflection needs an `inflection` schema to maintain state. Customers can do one of two things for this:

       1. Create a schema named `inflection` within the database that is being connected and then grant all privileges to that schema.

          ```sql theme={null}
          GRANT ALL PRIVILEGES ON SCHEMA inflection TO <inflection_user_name>;
          ```

       2. Grant schema create permission for Inflection to automatically do above

          ```sql theme={null}
          GRANT CREATE ON DATABASE <database_name> TO <inflection_user_name>;
          ```

    3. Grant usage access to the schema being connected to the new user

    ```sql theme={null}
    GRANT USAGE ON SCHEMA <schema_being_connected> TO <inflection_user_name>;
    ```

    4. Grant select privilege on the specific tables being connected or to all the tables in the schema

    ```sql theme={null}
    # Grant select on all tables in schema
    GRANT SELECT ON ALL TABLES IN SCHEMA <schema_being_connected> TO <inflection_user_name>;

    # Grant select on specific tables in the schema
    GRANT SELECT ON TABLE <schema_being_connected>.<table_being_connected> TO <inflection_user_name>;
    ```

    5. Make sure to Whitelist the IPs given from the UI

    Connection creation notes:

    * Use the hostname and port from `endpoint` details in the redshift cluster details

      <img alt="Redshift cluster endpoint details showing hostname and port" />

      * Here, the hostname would be `redshift-cluster-1.cmjhsmtjaqgq.ap-south-1.redshift.amazonaws.com` and the port would be `5439`
      * Use the username and password for the user that was created for the connection
  </Accordion>
</AccordionGroup>


# Snowflake Setup and Configuration (using storage integration)
Source: https://docs.inflection.io/connections/warehouses/snowflake

Set up Snowflake as an Inflection data source and export destination.

## Prerequisites

### For Exporting Data from Inflection to Snowflake

* Admin access to your Inflection account
* Snowflake account credentials
* Service account with appropriate permissions
* Key-pair authentication credentials (recommended) or username and password
* The user running the SQL queries for the setup should have ACCOUNTADMIN role access

### For Importing Data from Snowflake to Inflection

* Admin access to your Inflection account
* Snowflake account with `ACCOUNTADMIN` role or `MANAGE GRANTS` privilege
* Database containing source tables that meet Inflection schema requirements
* Key-pair authentication credentials (recommended) or username and password
* The user running the SQL queries for the setup should have ACCOUNTADMIN role access

<Info>
  **Important:** Snowflake is deprecating single-factor password authentication for service users. By August-October 2026, all service users (TYPE=SERVICE) must use key-pair authentication. Learn more in [Snowflake's Password Deprecation Timeline](https://docs.snowflake.com/en/user-guide/security-mfa-rollout).
</Info>

## Import Snowflake Data to Inflection

### Set Up Import Connection in Inflection

1. Navigate to **Connections → Data Connections**
2. Click **Add new connection**

<img alt="Add new connection button on the Data Connections page" />

1. Enter connection details:

2. Choose your authentication method:

   **Option A: Key-Pair Authentication (Recommended)**:

   * **Account name** - a human-friendly name for this particular Snowflake import
   * **Database** - name of the database where all the Inflection-ready tables are present
   * **Username** - username of the service account
   * **Private key** - RSA private key (2048-bit minimum) in PEM format
   * **Private key passphrase** (if applicable) - for encrypted private keys

   <Tip>
     **Reference:** [Here](https://docs.snowflake.com/en/user-guide/key-pair-auth#generate-the-private-keys) is the document from Snowflake to generate your Private Key
   </Tip>

   <img alt="Key-pair authentication fields for the Snowflake import connection" />

   **Option B: Username & Password Authentication**

   * **Account name** - a human-friendly name for this particular Snowflake import
   * **Database** - name of the database where all the Inflection-ready tables are present
   * **Username, Password** - authentication credentials for the Snowflake service account

3. Integration setup

   1. Run the SQL script provided, get the **STORAGE\_AWS\_IAM\_USER\_ARN** and **STORAGE\_AWS\_EXTERNAL\_ID** values from the query result, provide them in the corresponding text boxes and submit

   <img alt="Storage integration setup showing the SQL script and the STORAGE_AWS_IAM_USER_ARN and STORAGE_AWS_EXTERNAL_ID fields" />

<Accordion title="Set up Snowflake to allow Inflection read">
  You'll need to be logged in as an `ACCOUNTADMIN` or an account that has `MANAGE GRANTS`. Inflection will need access to the Database, Schema, Tables, Views and Warehouse that the data is in. While the below steps defines default resources, you can define any user, role, warehouse you'd like.

  1. Create warehouse

     ```sql theme={null}
     CREATE WAREHOUSE "INFLECTION_WAREHOUSE"
       WITH WAREHOUSE_SIZE = 'XSMALL'
         WAREHOUSE_TYPE = 'STANDARD'
         AUTO_RESUME = TRUE;
     ```

  2. Create Role for Inflection

     ```sql theme={null}
     CREATE ROLE INFLECTION_ROLE
        COMMENT = 'Access on inflection schema to maintain state between syncs';
     ```

  3. Create User for Inflection

     Choose based on your authentication method:

     **For Key-Pair Authentication (Recommended):**

     ```sql theme={null}
     -- Step 1: Create user without password
     CREATE USER INFLECTION_USER
       DEFAULT_ROLE = INFLECTION_ROLE
       DEFAULT_WAREHOUSE = "INFLECTION_WAREHOUSE"
       COMMENT = 'User for inflection operations';

     -- Step 2: Assign public key (replace with your actual public key)
     ALTER USER INFLECTION_USER 
       SET RSA_PUBLIC_KEY='<your_public_key_without_BEGIN_END_delimiters>';
     ```

     <Note>
       **Reference:** [Here](https://docs.snowflake.com/en/user-guide/key-pair-auth#generate-the-private-keys) is the document from Snowflake to generate your Key
     </Note>

     **For Username & Password Authentication:**

     ```sql theme={null}
     CREATE USER INFLECTION_USER
     MUST_CHANGE_PASSWORD = FALSE
     DEFAULT_ROLE = INFLECTION_ROLE
     DEFAULT_WAREHOUSE = "INFLECTION_WAREHOUSE"
     PASSWORD = "my_strong_password"
     COMMENT = 'User for inflection operations';
     ```

  4. Create an `inflection` schema in the database. The database refers to the database where the source data lives. Replace `<DB_NAME>` with the database name.

     ```sql theme={null}
     CREATE SCHEMA <DB_NAME>.INFLECTION
     	COMMENT = 'Schema for Inflection operations';
     ```

  5. Granting permissions and access.

     1. Role to User

        ```sql theme={null}
        GRANT ROLE INFLECTION_ROLE TO USER INFLECTION_USER;
        ```

     2. Warehouse usage to Role

        ```sql theme={null}
        GRANT USAGE ON WAREHOUSE "INFLECTION_WAREHOUSE" TO ROLE "INFLECTION_ROLE";
        ```

     3. Grant access to the `inflection` schema

        ```sql theme={null}
        GRANT USAGE, CREATE TABLE, CREATE VIEW
          ON SCHEMA <DB_NAME>.INFLECTION
          TO ROLE INFLECTION_ROLE;
        GRANT ALL 
        	ON FUTURE TABLES IN SCHEMA INFLECTION 
        	TO ROLE INFLECTION_ROLE;
        ```

     4. Grant access to the source data

        ```sql theme={null}
        #Permission to list schemas in the database (USAGE: Access to USE and SHOW ops)
        GRANT USAGE
        	ON DATABASE <DB_NAME>
        	TO ROLE INFLECTION_ROLE;

        #Permission to list tables and views in the database
        GRANT USAGE
        	ON SCHEMA <DB_NAME>.<SCHEMA_NAME>
        	TO ROLE INFLECTION_ROLE;

        #Permission to read from the table
        GRANT SELECT
          ON TABLE <DB_NAME>.<SCHEMA_NAME>.<TABLE_NAME>
          TO ROLE INFLECTION_ROLE;
        ```

  ### FAQ: My data is in multiple tables. Does Inflection support views?

  **Certainly. You can create the view in any shape and provide access to it to the `inflection user` like any table.**

  ```sql theme={null}
  #Create a view
  CREATE VIEW <DB_NAME>.<SCHEMA_NAME>.<VIEW_NAME> AS
  	SELECT * FROM <DB_NAME>.<SOURCE_SCHEMA_NAME>.<SOURCE_TABLE_NAME>

  #Permission to read from the view
  GRANT SELECT
    ON VIEW <DB_NAME>.<SCHEMA_NAME>.<VIEW_NAME>
    TO ROLE INFLECTION_ROLE;
  ```

  **Keep in mind that any breaking changes from the tables that the view is generated from i.e. deleting a column, will break the view which in turn will break the connection.**
</Accordion>

## Export Inflection Data to Snowflake

### Set up Export Connection in Inflection

1. Navigate to **Connections → Data Connections**
2. Click **Add new connection**

<img alt="Add new connection button on the Data Connections page" />

1. Select **Snowflake** as your destination platform.

2. **Select connection type**: Choose **Export Data to Snowflake**.

   <img alt="Export Data to Snowflake connection type selection" />

3. **Enter your Snowflake credentials**

   * Choose your authentication method.
     * **Key-Pair Authentication (Recommended):**
       * **Connection name:**

       * **Account name:** a human-friendly name for this Snowflake connection

       * **Username**: username of the service account that connects to Snowflake

       * **Private key:** RSA private key (2048-bit minimum) in PEM format

         <Info>
           See [Snowflake's key-pair authentication guide](https://docs.snowflake.com/en/user-guide/key-pair-auth#generate-the-private-keys) to generate your private key.
         </Info>

       * **Private key passphrase** (if applicable): for encrypted private keys

       * **Database** and **Schema:** name of the database and schema where Inflection should write data
     * **Option B: Username & Password Authentication**

       <Info>
         Password authentication will be deprecated by August. Migrate to key-pair authentication before this deadline.
       </Info>

       * **Connection name:**
       * **Account name:** a human-friendly name for this Snowflake connection
       * **Username, Password:** authentication credentials for a service account
       * **Database** and **Schema:** name of the database and schema where Inflection should write data

4. Click **Create Connection**

5. Integration setup

   1. Run the "Storage Setup SQL" script provided in Connection details, get the **STORAGE\_AWS\_IAM\_USER\_ARN** and **STORAGE\_AWS\_EXTERNAL\_ID** values from the query result, provide them in the corresponding text boxes and submit

   <img alt="Storage Setup SQL and integration fields in Connection details" />

The connection will remain in **inactive** state until credentials and destination tables are validated by the Inflection team.

### Create Export Tables in Snowflake

Inflection provides a custom SQL script tailored to your configuration. Run this script to create the export tables in your data warehouse.

1. Navigate to **Connections** → Select the Snowflake Export connection
2. Click **Connection Details**
3. Click **Copy code** in the **Table Creation SQL** section

<img alt="Copy code button in the Table Creation SQL section of Connection Details" />

The script creates tables with the necessary structure and grants required permissions (INSERT, UPDATE, DELETE) for Inflection to write data.

### Activate the Export Connection

Once you have saved credentials and created required tables in Snowflake, your setup is complete.

The Inflection team will validate the setup and activate the sync. You will be notified once the sync has started and data is being sent.

<Info>
  Activation may take up to two business days. Please ensure your data team notifies you once your tables are set up in your data warehouse.
</Info>

<Note>
  ### Changing from Username Password to Key Pair Authentication

  To change your connection :

  1. Go to your snowflake connection (import or export)

  2. Go to "Connection Settings" tab

     1. Snowflake Export

        <img alt="Connection Settings tab for a Snowflake Export connection" />

     2. Snowflake Import

        <img alt="Connection Settings tab for a Snowflake Import connection" />

  3. Click on the "Edit Details" button in top right

  4. Change the "Authentication Type" to "Key "Pair."

     <img alt="Authentication Type set to Key Pair in the Edit Details form" />

  5. Update the following fields

     1. **Private key** - RSA private key (2048-bit minimum) in PEM format
     2. **Private key passphrase** (if applicable) - for encrypted private keys
     3. **Database** and **Schema** - name of the database and schema where Inflection should write data

        <Note>
          **Reference:** [Here](https://docs.snowflake.com/en/user-guide/key-pair-auth#generate-the-private-keys) is the document from Snowflake to generate your Private Key
        </Note>

  6. Click on save

  Your connection will now use key pair for authentication.

  **Follow these steps for both IMPORT and EXPORT connections.**
</Note>


# Web Tracking
Source: https://docs.inflection.io/connections/web-tracking

Configure Inflection web tracking to target contacts based on web browsing activities.

Inflection tracks the page visits of your leads and associates their activities with their contact when they are identified. Website tracking can be used for monitoring visitor data within your marketing webpages.

## Add a domain for tracking on Inflection

1. Go to **Settings > Website Tracking**
2. Click **Add Domain**
3. Type or paste your domain here and click **Proceed**

<Info>
  Only base domains are accepted as input. If you enter a full link, it will be automatically truncated to just the base domain. For example, entering "[https://sub.example.com/page](https://sub.example.com/page)" will simplify to "example.com." This ensures consistency and accuracy in tracking.
</Info>

<Tip>
  Subdomains (such as "**blog.example.com**") can be enabled or disabled separately, after adding the base domain. By default, all subdomains of the added domain are accepted for tracking, provided they have the tracking code installed.
</Tip>

4. Copy the shown tracking code to be installed in the domain you just added. You can also directly send the tracking code as an email to your developer. Click **Proceed**.
5. Your domain may take up to 24 hours to be approved. Meanwhile, you may go ahead and copy and install the tracking code in the pages you wish to track. Once approved, the domain status will be marked as **Active**, and tracking will commence.

### Track only specific subdomains

By default, all subdomains of an added domain is tracked by Inflection. (Given that the tracking code is installed in them).

If you wish to disable tracking for certain subdomains and include only specific ones, you may edit the tracking setup in the domain table.

1. Click on the three dots icon at the end of the domain and click **Edit tracking**
2. Disable **Automatically Track all Subdomains**. This disables tracking for all subdomains under the domain.
3. Domains you wish to track or ignore have to be individually added and enabled/disabled. Click **+ Add another subdomain** to add a subdomain.

   <Info>
     Only subdomains of the added domain are accepted. Full links will be automatically truncated.
   </Info>

## Set up your website for effective tracking

### Add the tracking code

* The tracking code must be added to the \<head> tag of your website. Adding it inside or after the \<body> or \<footer> tag may result in sub-optimal tracking.
* Page visits are tracked only on pages where the tracking code is installed. For example, adding the tracking code to example.com does not automatically track visits to blog.example.com unless the tracking code is also installed on blog.example.com.

### Set up forms for tracking

Properly setting up forms for website tracking is essential for associating tracked browsing activities with contacts. Inflection integrates with two form providers, Formstack and Webflow, to receive submission data effectively.

In order to setup your forms for tracking, you should first create a connection, and complete the setup for the respective form provider that you use, as instructed here.

<Tip>
  You don't necessarily have to complete mapping the form to contact fields in order for website tracking to work. Browsing activities of existing contacts who submitted the form will still be updated.

  However, if a form isn't mapped, all browsing activities of new contacts will remain hidden until the contact is created.
</Tip>

#### Formstack

If you are using embedded Formstack forms in your website to receive form submissions, you'll have to include a custom hidden field in your Formstack builder for Inflection to track.

Follow these instructions from Formstack: [Use Hidden Fields for Admin Purposes](https://help.formstack.com/hc/en-us/articles/44592227869203-Use-Hidden-Fields-for-Admin-Purposes). Create a hidden text field with label `inflection_form_context` and keep the default value blank.

#### Webflow

Webflow forms are tracked automatically. This is done by adding a hidden field when the form first loads on the page.

However, manually adding the hidden field is recommended as a fallback to prevent visual or submission issues. In order to identify anonymous users from your website and associate browsing activity with them, you can embed a custom hidden input in the forms of your website.

Copy the following HTML code into your form element and follow the instructions given [here](https://discourse.webflow.com/t/how-to-add-hidden-form-fields-to-forms/1966) to add a hidden field.

```html theme={null}
<input type="hidden" name="inflection_form_context" value="">
```

#### Other HTML forms

Inflection provides a custom `identify` method which has to be explicitly called by your form's `onsubmit` function in order for Inflection to associate the session activity to an anonymous user.

While full submission data is not received from these forms, the email will be used for tracking.

Include the following line of code in the submit function of your website's forms. Replace '[example@email.com](mailto:example@email.com)' with the email input received from your form.

```javascript theme={null}
window.inflection.identify("example@email.com")
```

**Example usage**

```javascript theme={null}
let newsletter_form = document.getElementsByTagName("form")[0];

newsletter_form.onsubmit = (e) => {
	e.preventDefault();
	let email_input = newsletter_form.querySelector("input[type='email']").value;
	
	window.inflection.identify(email_input);
	
	// Rest of your submission logic
	// ...
	//
}
```

#### Exceptions

* iFrames and lightboxes cannot be tracked
* Inflection does not automatically capture new leads unless they submit their email through a properly set up form, as discussed above.

#### How does Inflection identify contacts for associating browsing activities to?

Assuming that the tracking code is installed and forms configured correctly as mentioned above, contacts are identified when any of these actions are performed:

* Visitor fills a form containing a hidden field
* `window.inflection.identify()` JS function is called from your website.
* Visitor clicks on a link in an email sent via Inflection, landing on a website with the tracking code installed.

<Info>
  Each email has an **Identify visitors on your website** switch in its tracking settings. If this switch is turned off for a specific email, clicks on links in that email do not identify the visitor on your website — even if website tracking is set up and the tracking code is installed. See [Email Settings](/settings/email-settings) for details.
</Info>

### Consent Management

<Info>
  Each email has an **Identify visitors on your website** switch in its tracking settings. If this switch is turned off for a specific email, clicks on links in that email do not identify the visitor on your website — even if website tracking is set up and the tracking code is installed. See [Email Settings](/settings/email-settings) for details.
</Info>

### Consent Management

Inflection's Website Tracking does not include a built-in cookie banner. Instead, we provide a callable function within our tracking code that can disable website tracking. This function (`window.inflection.disableTracking()`) can be integrated into the rejection function of your chosen consent management platformInflection's Website Tracking does not include a built-in cookie banner. Instead, we provide a callable function within our tracking code that can disable website tracking. This function (`window.inflection.disableTracking()`) can be integrated into the rejection function of your chosen consent management platform.

By default, tracking is enabled once the tracking code is installed on your website. However, note that some consent management platforms may block tracking pixels entirely. If a user clicks reject, our tracking service may be disabled as a resultBy default, tracking is enabled once the tracking code is installed on your website. However, note that some consent management platforms may block tracking pixels entirely. If a user clicks reject, our tracking service may be disabled as a result.

As a Marketing Automation Platform (MAP), ensure our cookie is categorized appropriately within your consent management settings. This will help maintain proper tracking functionality while adhering to privacy regulations.

As a Marketing Automation Platform (MAP), ensure our cookie is categorized appropriately within your consent management settings. This will help maintain proper tracking functionality while adhering to privacy regulations.

## Use website tracking in your marketing strategUse website tracking in your marketing strategy

### Marketing Activity

### Marketing Activity

Website activity appears as a marketing activity for individual contacts once their page visits are associated with their email. This association can occur when they submit a form with their email, when an `identify` call is made with their email, or when they click an email link that leads to a tracked websiteWebsite activity appears as a marketing activity for individual contacts once their page visits are associated with their email. This association can occur when they submit a form with their email, when an `identify` call is made with their email, or when they click an email link that leads to a tracked website.

All website activities are grouped per session. A single session may contain multiple page visits.

<img alt="Website session activity shown in a contact's marketing activity timeline" />

### Dynamic list

Website activity can also be used for filtering your contacts as audience in your journeys.

<img alt="Dynamic list builder filtering contacts by website activity" />

## Troubleshoot

<AccordionGroup>
  <Accordion title="My domain's status is shown as 'Inactive'">
    Inactive status is shown when Inflection does not receive any data from the website for the past 48 hours. Ensure that:

    1. You have correctly installed the tracking code. Watch out for typos or accidental spaces.
    2. Your website is loading correctly. Tracking scripts have to be loaded in timely, in order for us to begin tracking.
    3. If you are visiting the website to check it yourself, ensure that you are not using script blocking apps like uBlock Origin, etc and Javascript is enabled in your browser.
  </Accordion>

  <Accordion title="I had added a domain, but I see that it has disappeared from the domains list">
    This could be because the domain was rejected for approval. Please contact our team before attempting to add it again.
  </Accordion>

  <Accordion title="I do not see website activities associated to my contacts">
    Ensure the following are correctly setup:

    * Tracking code is present in the \<head> tag of all the pages you wish to track.
    * All domains or subdomains you wish to track are correctly added and enabled in the settings page.
    * Ensure that your form submissions contain a field called `inflection_form_context`. You can check your submissions in Assets > Forms, for this if you've added the connection.
    * If you're using custom HTML forms, ensure that you've configured the **identify** function to be called correctly.
  </Accordion>
</AccordionGroup>

All website activities are grouped per session. A single session may contain multiple page visits.

<img alt="Website session activity shown in a contact's marketing activity timeline" />

### Dynamic list

Website activity can also be used for filtering your contacts as audience in your journeys.

<img alt="Dynamic list builder filtering contacts by website activity" />

## Troubleshoot

<AccordionGroup>
  <Accordion title="My domain's status is shown as 'Inactive'">
    Inactive status is shown when Inflection does not receive any data from the website for the past 48 hours. Ensure that:

    1. You have correctly installed the tracking code. Watch out for typos or accidental spaces.
    2. Your website is loading correctly. Tracking scripts have to be loaded in timely, in order for us to begin tracking.
    3. If you are visiting the website to check it yourself, ensure that you are not using script blocking apps like uBlock Origin, etc and Javascript is enabled in your browser.
  </Accordion>

  <Accordion title="I had added a domain, but I see that it has disappeared from the domains list">
    This could be because the domain was rejected for approval. Please contact our team before attempting to add it again.
  </Accordion>

  <Accordion title="I do not see website activities associated to my contacts">
    Ensure the following are correctly setup:

    * Tracking code is present in the \<head> tag of all the pages you wish to track.
    * All domains or subdomains you wish to track are correctly added and enabled in the settings page.
    * Ensure that your form submissions contain a field called `inflection_form_context`. You can check your submissions in Assets > Forms, for this if you've added the connection.
    * If you're using custom HTML forms, ensure that you've configured the **identify** function to be called correctly.
  </Accordion>
</AccordionGroup>


# Clay
Source: https://docs.inflection.io/connections/webhooks/clay

Send data from Clay to Inflection using inbound webhooks.

This guide covers two primary workflows:

1. Sending data from Clay into Inflection via an HTTP API webhook
2. Bringing data from Inflection into a Clay table using Outbound webhooks and Journeys

<AccordionGroup>
  <Accordion title="Send Data from Clay into Inflection">
    ### Step 1: Create an Inbound Webhook connection for Clay

    * You can create a new **Inbound Webhook** under:

    * **Assets → Inbound Webhook**

      <img alt="Inbound Webhooks page under Assets in Inflection" />

    * Click **"New Connection"**

    * Provide a connection **name** and an optional **description**

      <img alt="New Connection dialog with name and description fields" />

    * Select an **Authentication Method**: No Auth / Basic Auth / API Key.

    * Enable or disable **"Create New Contact"**:
      * ✅ If enabled, Inflection will create a **new contact** whenever a new email ID is received
      * ❌ If disabled, no new contacts will be created

        <img alt="Connection settings showing authentication method and Create New Contact toggle" />

    * Click **"Generate webhook"** to create connection

    * Copy and configure the **webhook URL** and authentication details (if applicable) in Clay

    ### Step 2: Add the HTTP API Integration in Clay

    1. **Open your Clay workspace** and select the table containing your records (e.g., contacts with email).

    2. Click **Enrichment** in the top toolbar, then select **Integrations**.

    3. Choose the **HTTP API** integration tile.

       <img alt="HTTP API integration tile in Clay's integrations list" />

    4. Click **Add integration** to configure the POST request that will send data to Inflection.

    ### Step 3: Configure the HTTP API Request

    1. In the integration settings:

       * **Method:** `POST`
       * **Endpoint URL:** `Inbound Webhook Endpoint here`

       <img alt="HTTP API request configuration in Clay with method and endpoint URL" />

    2. Define the JSON body to include the fields you want to send. For example:

       ```json theme={null}
       {
         "email": "{{Email}}",
         "firstName": "{{First Name}}",
         "lastName": "{{Last Name}}"
       }
       ```

    3. Click **Save**.

    4. Run the integration for a sample row to verify it returns a **200 OK** response.

    ### Step 4: Verify Incoming Data in Inflection

    1. In Inflection, navigate to **Assets → Inbound Webhooks** and select your webhook.

    2. Go to the **Submissions** tab.

       <img alt="Submissions tab of an inbound webhook showing received payloads" />

    3. Confirm you see the new submission with `email`, `firstName`, and `lastName` recorded.

    ### Step 5: Extend the Payload with Additional Fields

    1. Return to Clay's **HTTP API** integration settings.

    2. Add any new field (e.g., `company`) to the JSON body:

       ```json theme={null}
       {
         "email": "{{Email}}",
         "firstName": "{{First Name}}",
         "lastName": "{{Last Name}}",
         "company": "{{Company}}"
       }
       ```

    3. Save and run the integration again.

    4. In Inflection's webhook **Contact Mappings**, map the new `company` property to the contact's Company field.
  </Accordion>

  <Accordion title="Bring Data from Inflection into Clay">
    ### Step 1: Generate an Outbound Webhook in Inflection for Clay

    1. In Inflection, open **Assets → Webhooks** and create a new webhook

    ### Step 2: Configure Clay to Receive Inflection Data

    1. In your Clay table, go to **Sources → Webhook** and copy the Clay webhook endpoint

       <img alt="Clay Sources panel with the Webhook source and endpoint URL" />

    2. Paste the Clay webhook URL in the Inflection webhook and configure the webhook with the fields you want to send to Clay

       <img alt="Inflection webhook configuration with the Clay webhook URL" />

       <img alt="Webhook field configuration listing the contact fields to send" />

    3. Click **Save**.

    ### Step 3: Configure the Journey to Push Data Outbound to Clay

    1. In Inflection, navigate to **Journeys**, then open (or create) the Journey you'll use.
    2. Define the audience criteria for which records should flow into Clay.
    3. Add an **Webhook** step and selected the above created Webhook
    4. Save your Journey.

    ### Step 4: Run and Verify the Data Sync

    1. In Inflection, **Run** the Journey.

    2. Wait \~1 minute for the webhook to deliver data.

    3. In Clay, **Refresh** your table—you should see new rows for each lead that was sent.

       <img alt="Clay table with new rows synced from Inflection" />

    4. Add columns in Clay (Email, First Name, Last Name, Company, etc.) to surface the synced data.
  </Accordion>

  <Accordion title="Demo Video">
    [Inflection\<>Clay Data Flow](https://www.loom.com/share/bd2d3b7d121740a9bd82b6136b33e007?sid=0bbbf651-b51e-4b63-becf-6303afb6c08e)
  </Accordion>

  <Accordion title="References">
    [Clay Webhooks Guide: Clay Help Center](https://www.clay.com/university/guide/webhook-integration-guide)
  </Accordion>
</AccordionGroup>


# Clearbit
Source: https://docs.inflection.io/connections/webhooks/clearbit

Send data from Clearbit to Inflection using inbound webhooks.

Below triggers are available in clearbit

* **When a company enters the audience**
  * Triggers only when a company/person enters the audience.
* **When a company exists the audience**
  * Triggers only when a company/person exits the audience.
* **On page view**
  * Triggers every time company/person views a page on your site.

[Legacy: Set Up a Webhook Destination](https://help.clearbit.com/hc/en-us/articles/360022031574-Legacy-Set-Up-a-Webhook-Destination)

Follow these steps to set up a webhook in Clearbit:

1. Access Webhook Settings
   * Log in to Clearbit
   * Navigate to API & Webhooks settings
2. Add a Inflection.io Webhook URL
   * Locate the Webhook Destinations section
   * Click "Add Webhook Destination"
   * Enter your Webhook URL (where you want to receive data)
3. Choose Events
   * Select the specific events to trigger the webhook (e.g., `person.created`, `company.updated`)
4. Configure Authentication (Optional)
   * If required, set up authentication using Basic Auth, API Keys, or Bearer Tokens
5. Test the Webhook
   * Click "Test Webhook" to send a sample request
   * Verify the response on your webhook receiver
6. Save & Activate
   * Click Save to activate the webhook
   * Monitor webhook logs in Clearbit to troubleshoot issues

Updating records with information, including industry, company size, social profiles, etc


# Goldcast
Source: https://docs.inflection.io/connections/webhooks/goldcast

Send data from Goldcast to Inflection using inbound webhooks.

This guide covers how you can create inbound webhook connection and configure Goldcast for ingesting events data in Inflection

<AccordionGroup>
  <Accordion title="Creating a Inbound Webhook connection for Goldcast">
    * You can create a new **Inbound Webhook** under:

    * **Assets → Inbound Webhook**

      <img alt="Inbound Webhook section under Assets in Inflection" />

    * Click **"New Connection"**

    * Provide a connection **name** and an optional **description**

      <img alt="New connection form with name and description fields" />

    * Select an **Authentication Method**: No Auth / Basic Auth / API Key.

    * Enable or disable **"Create New Contact"**:

      * ✅ If enabled, Inflection will create a **new contact** whenever a new email ID is received
      * ❌ If disabled, no new contacts will be created

      <img alt="Authentication method and Create New Contact options" />

    * Click **"Generate webhook"** to create connection

    * Copy and configure the **webhook URL** and authentication details (if applicable) in Goldcast

      <img alt="Generated webhook URL shown after creating the connection" />
  </Accordion>

  <Accordion title="Connecting Goldcast events to Inflection">
    ### Step 1: Installing the Webhooks App

    1. **Access the Marketplace:**

       * Go to the [Goldcast Marketplace](https://www.goldcast.io/marketplace) and locate the Webhooks tile.

       <img alt="Webhooks tile in the Goldcast Marketplace" />

    2. **Initiate the Connection:**

       * Click the **Connect App** button to start the installation process.

       <img alt="Connect App button for the Webhooks app in Goldcast" />

    3. **Installation Process:**

       * After clicking, you will be redirected to Goldcast Studio's Integrations page.
       * A pop-up titled **Install Webhooks** will appear—click the **Install** button.

       <img alt="Install Webhooks pop-up in Goldcast Studio" />

    4. **Authentication and Confirmation:**

       * You will see a confirmation pop-up after the installation.
       * Complete the authentication process on the next screen, then click **Finish** to finalise the set

       <img alt="Installation confirmation pop-up in Goldcast" />

       <img alt="Authentication screen with Finish button in Goldcast" />

    ### Step 2: Configuring the Webhook for a Webinar

    1. **Create a Test Webinar:**
       * Log in to Goldcast Studio with your credentials.
       * Navigate to the **Events** tab, create a new test webinar (select any upcoming date and time you prefer), then open that test webinar's Event Dashboard.

    2. **Access the Integrations Section:**
       * Open the **Integrations** tab within the dashboard.

    3. **Go to Webhooks:**

       * On the Integrations page, select the **Webhooks** option.

       <img alt="Integrations tab within the Goldcast event dashboard" />

       <img alt="Webhooks option on the Goldcast Integrations page" />

    4. **Create a New Webhook:**

    * Click the **Create Webhook** button to open the configuration popup.
    * **Name:** Enter a descriptive name (for example, "Inflection\<>Goldcast Webhook").
    * **Webhook URL→** Paste the **Webhook URL** generated from Inflection.
    * **Headers:** Leave this field blank as authentication is not required for this test.
    * **Trigger Activities:** Toggle the options for **Registered** and **Attended** to activate them.
    * Finally, click **Create** to save your new webhook configuration.

      <img alt="Create Webhook configuration popup in Goldcast" />

      <img alt="Newly created webhook listed in Goldcast" />
  </Accordion>

  <Accordion title="Connection details & field mapping">
    When a trigger activity occurs, Goldcast sends the data to Inflection.

    You can view the submission count on the **Connection Details** page.

    <img alt="Submission count on the Connection Details page in Inflection" />

    ### Step 1 - Enable fields for mapping

    * Go to "Submission Fields" tab
    * Enable the required fields and click **Save**.

      <img alt="Submission Fields tab with fields enabled for mapping" />

    ### Step 2 - Mapping fields

    * Go to "Connection mapping" tab and click on "Edit"
    * Here you can define mapping for goldcast submission fields to Inflection contact fields.

    <Tip>
      Mapping the **"Email"** Contact field is required for data to flow into Inflection
    </Tip>

    * Additionally, map other essential fields like `magicLinkUrl`
    * `magicLinkUrl` is the unique invitation link for each user. You can later use it in email campaigns sent via Inflection.

      <img alt="Connection mapping tab showing Goldcast fields mapped to Inflection contact fields" />

    Based on your mapping rules:

    * New contacts will be created in Inflection for each unique email.
    * Contact fields will be updated accordingly.
    * Once the Email field is mapped, you can use submission data for journey targeting.
  </Accordion>

  <Accordion title="Targeting contacts">
    You can use Goldcast submissions within **Journeys** as shown below

    1. Navigate to: **Journeys → Create New Journey**
    2. Add a condition:
       **Performed a Marketing Activity → Inbound Webhook Sync**

    Example: An audience filter for all users who **registered** for the webinar.

    <img alt="Journey audience filter targeting users who registered for the webinar" />

    <Tip>
      See expected `activityType` values in Goldcast's doc: [Goldcast Webhooks Payload Structure](https://help.goldcast.io/en_US/7805597141275-Webhooks/17571696255131-goldcast-webhooks-payload-structure). These are the values you'll need to target **registrants** vs. **attendees**.

      Note that **attended on-demand** will not come over as a separate event; it will come over as **attended** with an `engagementType` that indicates it's on-demand.

      `engagementType` is a property only on the attended event; this means an attended event will need to fire in order to map the field in Inflection.
    </Tip>

    ### Create email with tokens

    You can personalise emails for sending -

    * Registration confirmation
    * Follow-ups
    * Feedback requests
    * And more...

      <img alt="Email editor using mapped Goldcast fields as personalization tokens" />

    You can also use Goldcast submissions in **Branch by Filter** to tailor communications based on attendee status.

    <img alt="Branch by Filter step using Goldcast submission data" />
  </Accordion>

  <Accordion title="References">
    Goldcast Webhooks Integration Help: [Webhooks Integration](https://help.goldcast.io/en_US/7805597141275-Webhooks/16670925425819-webhooks-integration)

    List of events - [Goldcast Event Engagement Activities](https://help.goldcast.io/general-integrations/4404985089691-goldcast-event-engagement-activities)

    All payloads - [Goldcast Webhooks Payload Structure](https://help.goldcast.io/en_US/7805597141275-Webhooks/17571696255131-goldcast-webhooks-payload-structure#1-registration-0)
  </Accordion>
</AccordionGroup>


# Hubspot
Source: https://docs.inflection.io/connections/webhooks/hubspot

Send data from HubSpot to Inflection using inbound webhooks.

Update a contact in Inflection using a hubspot workflow/campaign so that I can get any hubspot specific properties in inflection

* Sending updated PQL scores based on engagement metrics
* Triggering webhooks for changes in a lead's lifecycle stage to ensure real-time updates on our end
* Lead status and unsubscribe from Hubspot

[Use webhooks with HubSpot workflows](https://knowledge.hubspot.com/workflows/how-do-i-use-webhooks-with-hubspot-workflows)

Follow these steps to set up a webhook in Hubspot

1. In your HubSpot account, navigate to **Automations** > **Workflows**
2. To edit an existing workflow, click the **name** of the workflow. Or, [create a new workflow](https://knowledge.hubspot.com/workflows/create-workflows?hubs_content=knowledge.hubspot.com/workflows/add-data-to-google-sheets-with-workflows\&hubs_content-cta=create%20a%20new%20workflow).
3. In the workflow editor, click the **+ plus icon** to add an action.
4. In the left panel, in the *Data ops* section, select **Send a webhook**
5. Click the **Method** dropdown menu and select **POST**.
6. Enter the Inflection **webhook enpoint URL**
7. Set up your authentication type to authenticate requests to your webhook
8. To include all properties, select **Include all \[object] properties** or Select **Customise request body** to include only specific properties
9. Click **Save**.

<img alt="HubSpot workflow editor with the Send a webhook action configured" />


# Linkedin
Source: https://docs.inflection.io/connections/webhooks/linkedin

Send data from LinkedIn to Inflection using inbound webhooks.

<AccordionGroup>
  <Accordion title="Creating an Inbound Webhook Connection for LinkedIn">
    1. Navigate to:
       **Assets → Inbound Webhook**
    2. Click **"New Connection"**
    3. Select **LinkedIn** from the list of connection types
    4. Provide a **Connection Name** and optional **Description**
    5. Choose an **Authentication Method**:
       * **No Auth**
       * **Basic Auth**
       * **API Key**
    6. Enable or disable **"Create New Contact"**:
       * ✅ **Enabled** – Inflection will create a new contact when a new email is received
       * ❌ **Disabled** – Only updates to existing contacts will be allowed
    7. Click **"Generate Webhook"** to finalize the setup
    8. Copy the **Webhook URL** and authentication details (if applicable)
  </Accordion>

  <Accordion title="Configuring LinkedIn Webhook">
    You can integrate LinkedIn Lead Gen Forms with Inflection using **two methods**:

    1. **Via Zapier** – A no-code solution for easy setup
    2. **By Creating a LinkedIn App** – A direct integration for advanced users

    With these options, you can automatically send lead data from LinkedIn to Inflection and use it for **contact updates, audience segmentation, and journey triggers**

    <AccordionGroup>
      <Accordion title="Option 1: Sending Leads from LinkedIn to Inflection via Zapier">
        **Zapier** allows you to connect LinkedIn Lead Gen Forms with Inflection without any coding. Follow these steps:

        ### Step 1: Create a Zap

        1. Log in to your **Zapier** account ([zapier.com](https://zapier.com/)).
        2. Click **"Create Zap"**.
        3. In the **Trigger** section, search for **"LinkedIn Ads"**.
        4. Select **"New Lead Gen Form Response"** as the trigger event.
        5. Click **"Continue"** and connect your **LinkedIn Ads account**.
        6. Choose the **Lead Gen Form** you want to use.

        ### Step 2: Connect Inflection

        1. In the **Action** section, search for **"Webhook by Zapier"**.
        2. Choose **"POST"** as the action event.
        3. Click **"Continue"** and enter the **Inflection Webhook URL** (from your Data Sync Connection in Inflection).
        4. Select **"JSON"** as the payload format.
        5. Map the **LinkedIn lead fields** (e.g., Name, Email, Phone Number) to Inflection's **contact fields**.
        6. Click **"Continue"** and test the Zap.

        ### Step 3: Activate the Zap

        1. Click **"Turn on Zap"** to activate the integration.
        2. Now, every new lead from your LinkedIn Lead Gen Form will be automatically sent to Inflection.
      </Accordion>

      <Accordion title="Option 2: Sending Leads from LinkedIn to Inflection via LinkedIn App">
        ### Step 1: Set Up a LinkedIn App

        1. Go to [LinkedIn Developer Portal](https://www.linkedin.com/developers/)
        2. Create a new app or use an existing one
        3. In the app dashboard:
           * Navigate to **Products** and request access to **Marketing Developer Platform**
           * Ensure you have permission to use the **Lead Gen Forms** API

        ### Step 2: Configure Webhook with Challenge Response

        1. Go to your app's **Webhooks** section
        2. Click **Add Webhook**
        3. Enter:
           * **Webhook URL** – Paste the URL generated in Inflection
           * **Event Type** – Choose `leadGen.formResponse`
           * **Token (optional)** – You can leave this blank if not used

        <Check>
          Inflection automatically handles challenge-response validation required by LinkedIn
        </Check>

        Save the configuration

        LinkedIn will send a test challenge request. Inflection's backend will respond with the challenge token and validate the webhook.
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Connection Details & Field Mapping">
    ### Monitor Webhook Submissions

    * View real-time submission counts on the **Connection Details** page

    ### Step 1: Enable Fields for Mapping

    1. Go to the **Submission Fields** tab
    2. Click **Edit**
    3. Enable required fields for mapping

    <Warning>
      Only enabled fields will be available in dynamic lists and journeys
    </Warning>

    ### Step 2: Map Submission Fields to Contact Properties

    1. Navigate to the **Connection Mapping** tab
    2. Click **Edit**
    3. Map LinkedIn fields to Inflection contact fields:
       * Required: **Email**
       * Recommended: **First Name**, **Last Name**, **Company**, **Job Title**
    4. Choose a mapping rule:
       * **Update if Empty**
       * **Always Overwrite**
  </Accordion>

  <Accordion title="Using LinkedIn Leads in Journeys">
    Once leads are flowing into Inflection:

    ### Target Contacts in Journeys

    1. Navigate to:
       **Journeys → Create New Journey**
    2. Add a condition:
       `Performed a Marketing Activity → Inbound Webhook Sync`
    3. Use filters such as:
       * Campaign Name = "Linkedin\_XYZ"
       * Lead Form ID, etc.

    ### Personalise Emails with Tokens

    Use mapped fields like:

    * `{{firstName}}`
    * `{{company}}`
    * `{{jobTitle}}`

    This allows for personalised confirmation, nurture, or demo follow-up emails.

    ### Segment Based on Status

    Use **Branch by Filter** to route leads:

    * Based on form name
    * Based on custom answers or job title
  </Accordion>

  <Accordion title="References">
    [Linkedin Webhook documentation](https://learn.microsoft.com/en-us/linkedin/shared/api-guide/webhook-validation)
  </Accordion>
</AccordionGroup>


# Marketo
Source: https://docs.inflection.io/connections/webhooks/marketo

Send data from Marketo to Inflection using inbound webhooks.

You can send **contact unsubscribe information** from Marketo to **Inflection.io's generic webhook endpoint** by setting up a **Marketo webhook**, Here's how:

1. **Get the Inflection Webhook URL**
   1. Obtain the **generic webhook endpoint** from Inflection.io where data will be ingested

2. Access Webhook Settings
   1. Log in to Marketo
   2. Go to Admin → Under Integration, select Webhooks
   3. Click "New Webhook".

3. Configure Webhook

   1. Webhook Name: Give it a descriptive name
   2. URL: Enter the inflection.io Webhook URL
   3. Request Type: Select POST
   4. Headers: Add any required headers
   5. Define the JSON payload

      ```json theme={null}
      {
        "email": {{lead.Email Address}},
        "unsubscribe": {{lead.Unsubscribed}}
      }
      ```

      Choose response type as JSON

   <img alt="Marketo webhook configuration with URL, request type, payload template, and response type" />

4. Test the Webhook
   1. Click "Send Test" and verify the response
   2. Adjust if needed based on requirements

5. Activate Webhook in Smart Campaign
   1. Navigate to Marketing Activities → Select a Smart Campaign
   2. Under Flow, click "Call Webhook" and select the newly created webhook
   3. Activate the campaign


# Zapier
Source: https://docs.inflection.io/connections/webhooks/zapier

Send data from Zapier to Inflection using inbound webhooks.

<AccordionGroup>
  <Accordion title="Send webinar/event registration information from Zoom/Luma to Inflection via Zapier">
    <img alt="Zapier flow sending Zoom/Luma registration data to an Inflection webhook" />

    Payload -

    ```json theme={null}
    {
      "duration": "30",
      "email": "zap.zaplar@zapier.com",
      "id": "97561845135",
      "join_time": "2024-04-23T20:39:56Z",
      "participant_id": "12345",
      "participant_user_id": "12345",
      "participant_uuid": "62A78A28-E2ED-9ECA-CFDB-9DC35167E477",
      "start_time": "2024-04-23T20:39:56Z",
      "timezone": "America/Los_Angeles",
      "topic": "Sample meeting",
      "user_id": "12345",
      "user_name": "Jason Kotenko"
    }
    ```
  </Accordion>

  <Accordion title="Send to Inflection when a row gets updated with people info in Google Sheets using Zapier">
    <img alt="Zapier flow sending updated Google Sheets rows to an Inflection webhook" />

    ```plain text theme={null}
    {
      "COL$A": "Sankalp",
      "COL$B": "sankalp@inflection.io",
      "COL$C": "7666066272",
      "id": "2",
      "row": "2"
    }
    ```
  </Accordion>

  <Accordion title="Send meeting bookers from Calendly to Inflection using Zapier">
    <img alt="Zapier flow sending Calendly meeting bookers to an Inflection webhook" />

    ```json theme={null}
    {
      "cancel_url": "https://calendly.com/cancellations/6f8a5007-86cc-4058-8e08-4040f351cfc6",
      "created_at": "2025-01-08T11:20:32.608370Z",
      "email": "abc.sethi@gmail.com",
      "event": "https://api.calendly.com/scheduled_events/5ba532ad-4246-4ecd-aded-14b698f9ce24",
      "event_type": {
        "active": "True",
        "admin_managed": "False",
        "booking_method": "instant",
        "color": "#8247f5",
        "created_at": "2024-12-19T08:45:32.333866Z",
        "custom_questions": "[{'answer_choices': [], 'enabled': True, 'include_other': False, 'name': 'Please share anything that will help prepare for our meeting.', 'position': 0, 'required': False, 'type': 'text'}]",
        "deleted_at": "",
        "description_html": "",
        "description_plain": "",
        "duration": "30",
        "duration_options": "",
        "internal_note": "",
        "kind": "solo",
        "locations": "[{'kind': 'google_conference'}]",
        "name": "30 Minute Meeting",
        "pooling_type": "",
        "position": "0",
        "profile": {
          "name": "Sankalp khot",
          "owner": "https://api.calendly.com/users/4d9bcd69-2160-4517-8aff-cc3cf5b59894",
          "scheduling_url": "https://calendly.com/sankalp-inflection",
          "type": "User"
        }}
      }
    ```
  </Accordion>
</AccordionGroup>

We will be able to support almost all the use cases where Zapier has direct trigger from third party app, you just need to add webhook by Zapier flow step and call our endpoint to post data in JSON format

Follow these steps to set up a webhook in Zapier

1. Create a Zap
   1. Log in to Zapier → Click "Create Zap".
   2. Select a Trigger App (e.g., form submission, CRM update)
   3. Set up the Trigger Event and test it.
2. Add Webhook Action
   1. Click "+" → Search "Webhooks by Zapier" → Select POST
   2. Enter the Inflection.io Webhook URL
3. Configure Request
   1. Payload Type: JSON (Recommended)
   2. Data: Add key-value pairs.
   3. Headers: Include API keys if required.
4. Test & Activate
   1. Click "Test & Review" to send a sample request.
   2. Verify the response & troubleshoot if needed.
   3. Click "Publish Zap" to activate.


# Zoom
Source: https://docs.inflection.io/connections/webhooks/zoom

Send data from Zoom to Inflection using inbound webhooks.

This guide explains how to configure an **Inbound Webhook** in Inflection and connect it to **Zoom** to ingest webinar or meeting activity data. This data can then trigger actions or target users within Inflection journeys.

<AccordionGroup>
  <Accordion title="Creating an Inbound Webhook Connection for Zoom">
    1. Navigate to:
       **Assets → Inbound Webhook**

    2. Click **"New Connection"**

    3. Select **Zoom** from the list

       <img alt="Selecting Zoom from the list of inbound webhook connection types" />

    4. Provide a **Connection Name** and optional **Description**

    5. Copy and paste Webhook Secret Token from Zoom app (app creation steps are detailed below)

       <img alt="Webhook Secret Token field in the Zoom connection setup" />

    6. Choose an **Authentication Method**:
       * **No Auth**
       * **Basic Auth**
       * **API Key**

    7. Enable or disable **"Create New Contact"**:
       * ✅ **Enabled** – A new contact will be created when a new email is received
       * ❌ **Disabled** – Only existing contacts will be updated

    8. Click **"Generate Webhook"** to finalize setup

    9. Copy the **Webhook URL** and authentication details (if applicable) to be used in Zoom

    <Warning>
      Authentication method cannot be changed once the connection is created
    </Warning>
  </Accordion>

  <Accordion title="Zoom Webhook Setup">
    ### Step 1: Create an App

    1. **Log in to Zoom** → Go to **Zoom App Marketplace**
    2. Click **"Develop" → "Build App"**
    3. Select **Webhook Only** as the app type
    4. Fill in **App Name**, select an **Account Type**, and click **Create**
    5. In the **Feature** tab, enable **Event Subscriptions**
    6. Click **"Add Event Subscription"** → Enter a **Subscription Name**
    7. Provide your **Inflection.io** **Webhook URL**
    8. Save and **Activate the App**

    ### Step 2: Configure Event Subscriptions

    1. Navigate to your app's **Event Subscriptions** section
    2. Click **Add Event Subscription**
    3. Name your subscription (e.g., "Inflection Webhook")
    4. Paste the **Webhook URL** from Inflection

    > Zoom will immediately send a url\_validation challenge request — this is handled automatically by Inflection.

    5. Choose the events to track, such as:
       * **Webinar Events:**
         * `webinar.registration_created`
         * `webinar.participant_joined`
         * `webinar.participant_left`
       * **Meeting Events:**
         * `meeting.participant_joined`
         * `meeting.participant_left`
         * `meeting.registration_created`
    6. Save the configuration

    Inflection supports Zoom's **challenge-response** model to verify webhook URLs.

    ### Challenge-Response Support

    When Zoom sends a `url_validation` payload, Inflection will:

    * Automatically extract the `plainToken`
    * Generate the required `encryptedToken`
    * Respond with both, as required by Zoom

    > You don't need to handle this manually — Inflection's backend does it for you.
  </Accordion>

  <Accordion title="Connection Details & Field Mapping">
    ### View Submissions

    * Monitor submission counts and errors from the **Connection Details** page

    ### Step 1: Enable Submission Fields

    1. Go to the **Submission Fields** tab
    2. Click **Edit**
    3. Enable required fields (e.g., `email`, `topic`, `join_time`, etc.)

    <Warning>
      Only enabled fields can be used in dynamic lists or journeys

      Once enabled, fields cannot be disabled
    </Warning>

    ### Step 2: Map Fields to Contact Properties

    1. Open the **Connection Mapping** tab
    2. Click **Edit**
    3. Map fields from Zoom payloads to Inflection contact properties:
       * Required: **Email**
       * Optional: **Topic**, **Join Time**, **Leave Time**, **Duration**
    4. Choose mapping rules:
       * **Update if Empty**
       * **Always Overwrite**
  </Accordion>

  <Accordion title="Using Zoom Data in Journeys">
    ### Target Contacts Based on Zoom Activity

    1. Go to:
       **Journeys → Create New Journey**
    2. Add a condition:
       `Performed a Marketing Activity → Inbound Webhook Sync`
    3. Filter contacts based on:
       * **Webhook name = Zoom**
       * **Event type = joined/left**

    ### Personalise Communication with Tokens

    Use Zoom fields to personalize outreach:

    * `{{topic}}` – Topic of the webinar
    * `{{joinTime}}` – Timestamp
    * `{{duration}}` – Time spent in the session

    Examples:

    * Send follow-ups to attendees
    * Nurture leads who registered but didn't attend
    * Trigger surveys post-meeting

    ### Segment Using Branch by Filter

    * Route users differently based on:
      * Whether they joined a session
      * How long they stayed
      * Session type (internal onboarding vs customer webinar)
  </Accordion>

  <Accordion title="References">
    * [Zoom Webhook Documentation](https://developers.zoom.us/docs/api/webhooks/)
  </Accordion>
</AccordionGroup>


# Account Scoring
Source: https://docs.inflection.io/database/account-scoring

Build models that grade every account from 0 to 100 based on the signals that define a strong fit for your business.

Account Scoring lets you build models that grade every account in your tenant from 0 to 100 based on the signals that define a strong fit for your business. Once a model is active, the score becomes a regular field on the Account object — available immediately in dynamic lists, journey branches, and anywhere else you use account properties.

<Info>
  **Permissions:** Workspace admins can create, edit, and activate scoring models. Anyone in your workspace can use score fields the same way they use any other account property.
</Info>

## Create a Scoring Model

Click **Account Scoring** in the left navigation, then click **New scoring model** in the top right.

<img alt="Account Scoring page with the New scoring model button in the top right" />

A new model starts in **Draft** status. Draft models do not score any accounts and have no effect on your data until you activate them.

### Add Signals

Each model is built from signals: characteristics of an account that indicate fit. Inflection provides a catalog of signals you can browse or search.

1. In the **Available Signals** panel, browse signals by category (**All**, **Profile**, **Org**, **Relevance**, **Stack**) or type into the search field to filter.
2. Drag a signal into **Positive Signals** to count it toward a higher score, or into **Negative Signals** to count it toward a lower score.
3. Adjust the weight on each signal to reflect how much it should influence the score relative to the others.

<img alt="Scoring model builder with Available Signals panel and Positive and Negative Signals sections" />

<Info>
  Positive signals raise an account's score; negative signals lower it. Use negative signals to express what disqualifies an account from being a strong fit.
</Info>

### Save and Activate

Click **Save Model** to keep your changes in Draft. When you're ready to score all accounts in your tenant against the model, change its status to **Active**.

Activating a model immediately triggers a scoring run across every account in your tenant. The page shows a progress indicator while accounts are being scored. Most tenants complete in a few seconds; larger tenants take longer.

## How Scores Appear on the Account

Each active scoring model produces a field on the Account object, named after the model. Scores range from **0 to 100**, where a higher number means a stronger fit.

<img alt="Account record showing a score field produced by an active scoring model" />

Multiple scoring models can be active at the same time. Each model produces its own field on the Account object, so a single account can carry several scores in parallel.

## Use Scores in Audiences and Journeys

Because scores are regular account fields, they work everywhere other account properties do.

### Filter a Dynamic List by Score

In the audience builder, add an **Account members** group, then add a person property of `account.<Model Name>` (for example, `account.Fit Score`). Use any numeric operator — **greater than**, **less than**, **between** — to define your threshold.

<img alt="Dynamic list filter using an account score field with a numeric operator" />

Audiences built this way maintain themselves: as scores update, contacts move in and out of the list automatically. Anything pointed at the list: journeys, segments, exports — becomes score-driven.

### Branch and Trigger Journeys by Score

On the Journey Canvas, use **Branch by Value** to split contacts into paths based on their account's score (for example, one path for scores above 80, another for 50–80, another below 50). For scheduled journeys, use a score-based dynamic list as the entry audience so contacts qualify the moment they cross a threshold.

<Info>
  Learn more about branching: [Journey Flow Steps Reference](/journeys/journey-flow-steps)
</Info>

## When Scores Are Recalculated

Inflection recalculates scores at three times:

1. **On activation:** when you change a model's status from Draft to Active, every account is scored immediately.
2. **On model edit:** saving changes to an active model triggers a full rescore of every account against the updated logic.
3. **Nightly:** Inflection rescores every account against every active model once per day so scores stay current as the underlying account data changes.

## Common Use Cases

* **Maintain a self-updating ICP list.** Build a dynamic list of accounts where `account.Fit Score > 80` and reference it across journeys and segments. As scores change, the list stays current without manual upkeep.
* **Route accounts by tier.** Use **Branch by Value** on the score field to send high-fit accounts down an executive-touch path and lower-fit accounts down a self-serve nurture.
* **Suppress poor-fit accounts.** Add an exclusion filter (`account.Fit Score < 30`) to outbound journeys to keep marketing focused on accounts worth nurturing.
* **Run multiple models in parallel.** Score the same accounts against different fit definitions — for example, a new-logo model and an expansion model — and reference each score independently.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Can I push account scores back to Salesforce?">
    Not in this release. Scores are stored on the Inflection Account object only. Syncing scores back to Salesforce is on the roadmap for a future release.
  </Accordion>

  <Accordion title="Can I sync the underlying signal data from a scoring model to my CRM?">
    Not in this release. The signal data the model evaluates is not exposed as separate account fields and is not synced to external systems. This is planned for a future release.
  </Accordion>

  <Accordion title="Can I backtest a scoring model against historical data?">
    Not in this release. Activating a model scores accounts based on their current state. Applying a model retroactively against historical account states is on the roadmap.
  </Accordion>

  <Accordion title="How many scoring models can I have active at once?">
    You can run multiple active models in parallel. Each active model produces its own field on the Account object, and the fields operate independently.
  </Accordion>

  <Accordion title="What happens to dynamic lists and journeys when I edit an active model?">
    Saving a change to an active model triggers a full rescore. Dynamic lists and journey branches that reference the score field will re-evaluate against the new scores on the next evaluation cycle.
  </Accordion>

  <Accordion title="Why is a Draft model not scoring my accounts?">
    Draft models exist only as configurations — they do not score any accounts. Change the model's status to **Active** to start scoring.
  </Accordion>
</AccordionGroup>


# Building Audiences
Source: https://docs.inflection.io/database/building-audiences

Learn about the many options to build audiences in Inflection, and best practices for structuring queries.

There are three primary ways to build audiences in Inflection:

* Journey audiences
* Dynamic lists
* Segments

Each has considerations, but the blocks (filters) available to create them are the same, as are the best practices we recommend.

## Filters

<AccordionGroup>
  <Accordion title="A person property">
    When targeting contacts or users based on a property value (also called an attribute or field value), select the person property filter. The prefix of the property indicates the Inflection entity the property describes.

    * contact properties have no prefix (e.g., `name`, `email`, `title`)
    * product user properties start with **product user.** (e.g., `product user.role`, `product user.created date`, `product user.last active`)
    * org properties start with **org.** (e.g., `org.plan`, `org.open seats`, `org.credits available`)
    * account properties start with **account.** (e.g., `account.owner`, `account.renewal date`, `account.geo`)

    <Info>
      Read more about these entities and their common use cases: [Common Connections & Use Cases](/connections/common-connections-use-cases)
    </Info>

    <Info>
      After selecting a field, click the data dictionary icon next to the operator dropdown to open **Insights from data dictionary**. The panel shows how the field is populated and what values it contains. For text fields, click values from the list to add them to your filter. Read more: [Data Dictionary](/database/data-dictionary)
    </Info>
  </Accordion>

  <Accordion title="Performed a product event">
    When targeting contacts or users based on an activity they did in your product, select the performed a product event filter. Additional filters include:

    * **Frequency**: How many times a contact or user did the activity
    * **Timeframe**: Within `n` days, weeks, months
      * Note that `in past 1 week` will evaluate the current calendar week; to evaluate a rolling 7-day period, use `in past 7 days`
      * To reference a date in the future, state negative n (`-n`); i.e., `in past -7 days` will evaluate the next 7 days.
    * **Add property group**: Reference activity properties

    **Within an org where…**

    When building user lists or user journeys, product activity conditions have an optional org-awareness toggle: **Within an org where…**. When enabled, only activity that happened inside an org matching the specified org traits is counted.

    For example, to target users who performed a product event in a workspace where **Plan** is **Free**, add the "Within an org where…" condition and set the org trait filter to Plan = Free. This excludes any activity the same user did in a paid workspace.

    Key behaviors:

    * This condition is available on user lists and user journeys only.
    * Activity with no org attached (for example, events received before this feature was enabled, or events where the org could not be resolved) does not match org-requiring conditions.
    * If you do not enable "Within an org where…", the filter counts all activity regardless of org — this is the existing default behavior and is unchanged.
    * The org is determined at ingest from the Segment payload. See [Segment connection settings](/connections/segment) for how to configure which trait supplies the org.

      <img alt="Performed a product event filter with the within an org condition and an org trait filter applied" />
  </Accordion>

  <Accordion title="Performed a marketing activity">
    When targeting contacts or users based on engagement with your marketing materials like an Inflection journey, email, or form, select the performed a marketing activity filter. Additional filters include:

    * **Frequency**: How many times a contact or user did the activity
    * **Timeframe**: Within `n` hours, days, weeks, months
      * Note that `in past 1 week` will evaluate the current calendar week; to evaluate a rolling 7-day period, use `in past 7 days`
      * To reference a date in the future, state negative n (`-n`); i.e., `in past -7 days` will evaluate the next 7 days.

    <Info>
      For the **in past** and **in relative timeframe between (inclusive)** operators, you can choose **hour(s)** alongside **day(s)**, **week(s)**, and **month(s)** as the unit. Hours accepts a value from 1 to 100. This unit is available both in the Dynamic List builder and in a journey or campaign node's **Audience Criteria**. Existing lists built on day, week, or month units are unaffected and need no changes.
    </Info>

    * **Additional details**: additional filters will depend on the event selected: the **qualified for journey** activity will offer journey name; the **submitted webhook** activity will offer submission values; etc.
  </Accordion>

  <Accordion title="Performed a web activity">
    When targeting contacts or users based on engagement with your tracked web property, select the performed a web activity filter. Additional filters include:

    * **Frequency**: How many times a contact or user did the activity
    * **Timeframe**: Within `n` hours, days, weeks, months
      * Note that `in past 1 week` will evaluate the current calendar week; to evaluate a rolling 7-day period, use `in past 7 days`
      * To reference a date in the future, state negative n (`-n`); i.e., `in past -7 days` will evaluate the next 7 days.

    <Info>
      For the **in past** and **in relative timeframe between (inclusive)** operators, you can choose **hour(s)** alongside **day(s)**, **week(s)**, and **month(s)** as the unit. Hours accepts a value from 1 to 100. This unit is available both in the Dynamic List builder and in a journey or campaign node's **Audience Criteria**. Existing lists built on day, week, or month units are unaffected and need no changes.
    </Info>

    * **Source of visit**
    * **Landing Page**, **Page URL**, **Page Title**
    * **Referrer URL**
    * **UTM** or **Custom Parameter**

    <Info>
      Learn more about web tracking: [Web Tracking](/connections/web-tracking)
    </Info>
  </Accordion>

  <Accordion title="List membership">
    When targeting contacts or users based on their membership or lack of membership in a static list, dynamic list, or journey audience, select the list membership filter.
  </Accordion>

  <Accordion title="Salesforce campaign membership">
    When targeting contacts or users based on their membership in a Salesforce campaign, select the Salesforce campaign membership filter. Additional filters include:

    * Campaign Member Status
    * Date Added
    * Has Responded
    * Responded Date
  </Accordion>

  <Accordion title="Salesforce Opportunity">
    When targeting contacts based on their association with a Salesforce Opportunity, select the **Has Salesforce Opportunity** filter. Use this to power deal-aware audiences — segment by Stage, Amount, or Close Date; suppress contacts during active deals; or build expansion lists from recent Closed Won Opportunities.

    Supported field conditions include:

    * **Opportunity Name**
    * **Account ID**
    * **Stage**
    * **Amount**
    * **Close Date**
    * **Type / Record Type**
    * **Is Closed**
    * **Is Won**
    * **Owner**
    * **Custom Opportunity fields** (synced automatically)

    Chain multiple conditions with **AND** / **OR** within the filter. Use the negation form (e.g., "Does NOT have Salesforce Opportunity where Stage IN ...") to exclude contacts associated with active deals.

    <img alt="Has Salesforce Opportunity filter with field conditions" />

    Which contacts a **Has Salesforce Opportunity** filter returns depends on your workspace’s **Opportunity Matching Strategy:** the explicit deal team only, everyone linked to the account in Salesforce, or everyone Inflection matches to the account. Because it is a single workspace-wide setting, the same filter behaves consistently across every Dynamic List, journey audience, and segment. Set or change it in your Salesforce connection’s Opportunity Sync settings.

    <Info>
      For full setup of Opportunity sync, the **Opportunity Matching Strategy** setting, the listing page, and the Salesforce tab on contact profiles, see the **Opportunity Sync** section in [Salesforce](/connections/salesforce).
    </Info>
  </Accordion>

  <Accordion title="Person segmentation">
    When targeting contacts or users based on their membership in a segment, select the Person segmentation filter.

    <Info>
      Read more about segments: [Segments](/database/segments)
    </Info>
  </Accordion>

  <Accordion title="Grouped properties: Account members">
    When targeting **contacts** based on the activity or properties of members within an **account**, select the **Account members filter**.

    When targeting **users** based on the activity or properties of members within an **org**, select the **Org members filter**.
  </Accordion>
</AccordionGroup>

## Contact/User Lists and Journeys

Inflection models people at two grains:

* A **contact** is a person: one record per email address.
* A **product user** is that person's membership in a specific org: One contact can be *many* product users if they belong to multiple orgs. (Thing of orgs as product workspaces or tenants.)

A **contact journey / contact list** enrolls **one row per person** → one email per person.

A **user journey / user list** enrolls **one row per user** → a person with three distinct user IDs is enrolled three times and can receive three emails.

<AccordionGroup>
  <Accordion title="General guidance">
    **Default to contact lists and journeys.** If your environment has people who have multiple user IDs, contact journeys are your safeguard against emailing the same person multiple times. The contact grain naturally collapses to one send per person. Reach for a **user** journey only when you've accounted for the duplicate-send behavior.

    <Info>
      When a **contact with multiple users** qualifies for a **contact journey**, the oldest user will be chosen for personalization (branches or tokens that evaluate based on user or org data).
    </Info>
  </Accordion>

  <Accordion title="When to step up to a user list/journey">
    Choose a **user** grain only when one of these is true:

    * **Grouped org logic:** "users where anyone in their org has \[done X]" uses the **Org members** filter, which targets users. This kind of filter is only possible in a user dynamic list or user journey.
    * **Org- or user-specific personalization or branching:** seats, plan, role, or activity tied to a *specific* org membership — **and** you intentionally want one tailored email per membership.

    Everything else stays at the contact grain:

    * **Targeting** in a contact setting can still include attributes from contacts, accounts, users, and orgs; and activity from marketing/web activities and product activities.
    * **Grouped account logic** — "contacts where anyone in the account has \[done X]" — uses the **Account members** filter and stays at the contact grain.
  </Accordion>

  <Accordion title="When you need user-specific personalization and one email per person">
    This is the common bind: the *content* depends on user/org data, but you don't want to email the same person multiple times. Don't default to a user journey here — use the **stamp-and-hand-off pattern**:

    1. Run a **user journey** to resolve the user-specific value, **write it to a contact field**, and **add the person to a static list.**
    2. The static list collapses to **one row per person.**
    3. Run a **contact journey** off that static list to send — one email per person, personalized from the stamped field.

    <Info>
      If a person belongs to multiple orgs, step 1 stamps them more than once. Decide upfront which value wins (most recent, highest-tier plan, etc.) so the final send is predictable.
    </Info>
  </Accordion>
</AccordionGroup>

## Best Practices

To ensure your list logic applies as-intended, we recommend these best practices.

<AccordionGroup>
  <Accordion title="Use groups to explicitly define list logic.">
    When building list logic in Inflection, groups act as parenthesis — defining the order of operator evaluation (i.e., which AND/OR evaluates when).

    <AccordionGroup>
      <Accordion title="Inner and Outer Groups">
        Inflection supports two levels of operator nesting, which we call Outer Groups and Filter Groups. Filter groups are always nested within outer groups. As you build your list logic, these groupings are visually summarized in the top right corner of the list building UI.

        <img alt="Outer group and filter group summary in the list building UI" />

        The example above has 4 criteria:

        1. Title contains a
        2. Title does not contain b
        3. Title begins with c
        4. Title does not begin with d

        It evaluates to: ((1 AND 2) AND 3) AND 4
      </Accordion>

      <Accordion title="Default Order of Operations">
        When order of operations is not explicitly assigned with groups, logic will evaluate according to Boolean order of operations. This means that unless otherwise specified through grouping, **AND** will evaluate before **OR**.

        <img alt="List logic evaluating with default Boolean order of operations" />

        The example above evaluates to: 1 OR (2 AND 3) OR 4

        Contacts will qualify who meet *any* of the three conditions below:

        * (1) Their title contains `a`
        * (2 AND 3) Their title does not contain `b` and their title begins with `c`
        * (4) Their title does not begin with `d`

        <Tip>
          If in doubt, send a screenshot or asset ID to the Inflection agent and ask the agent to explain the audience in plain language. You can then ask it questions to verify the audience is exactly what you intend it to be.
        </Tip>
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Use filters that are absolutely necessary; delete everything else.">
    * Ideally, a specific filter is only applied to an audience **one** time. If the audience references a dynamic list, evaluate the referenced dynamic list(s) to understand what filters are already applied. Where applicable, simplify so that each filter is only applied to the audience one time.
      * Example: If your audience criteria is `Dynamic List 1` AND `Dynamic List 2` AND `Geo is not EMEA`; check to see if `Geo is not EMEA` is already used as criteria in Dynamic List 1 and 2. If it is, it’s not necessary a third time.
    * Note that exclusion filters for unsubscribes and/or bounces are unnecessary. (Inflection automatically excludes unsubscribes and bounces from marketing sends.)

    <Tip>
      Fewer filters in audience criteria = simpler logic = easier to get it right.

      More filters = more complex logic = more opportunities to get it wrong.
    </Tip>

    <Tip>
      Pro tip: Simplifying your filters will also make your list queries compile faster.
    </Tip>
  </Accordion>

  <Accordion title="Order similar filters together, and in the way that natural language reads.">
    Most Inflection customers have 100s of dynamic lists in their instance. When audience criteria is consistently ordered across journeys, it’s easier for everyone to quickly understand a list *and* spot errors. The cognitive load of reading a list decreases when filters are ordered in a standard way each time.

    A general method of ordering list criteria:

    1. Inclusion criteria
       * Account attributes (enterprise customers; target accounts; churned accounts; etc.)
       * Contact or user attributes (persona; title; user role; last sign-in date; etc.)
       * Activities (filled out form; signed up; visited web page; etc.)
    2. Exclusion criteria
       * Account attributes (not a customer; not in an open opportunity; etc.)
       * Contact or user attributes
       * Activities

    <Tip>
      Example: When a person describes an audience, they might say “Enterprise customers who are VP and above, and signed up but haven’t activated yet.” Corresponding filters in the order described above would be:

      1. Enterprise accounts (Inclusion criteria; account attribute)
      2. VP and above (Inclusion criteria; contact attribute)
      3. Signed up (Inclusion criteria; activity)
      4. Activated never (Exclusion criteria; activity)
    </Tip>
  </Accordion>

  <Accordion title="Use segments to codify commonly-used audiences.">
    If you find that many of your journeys reference the same audience (i.e., free trials; admin users; a specific persona or product; etc.), consider identifying this criteria in a dynamic list or segment one time, and then referencing that dynamic list or segment in all journeys going forward. This helps users avoid rebuilding the same criteria over and over again, reducing room for error and inconsistency.
  </Accordion>

  <Accordion title="Once a list is built, read the filters out loud.">
    As you go, you will naturally evaluate:

    1. Does it make sense?
    2. Does it match the audience you intend to reach?

    If the logic is complex, it can help to visualize rather than verbalize (try sketching the logic with Venn diagrams or similar).

    <Tip>
      If in doubt, send a screenshot or asset ID to the Inflection agent and ask the agent to explain the audience to you in plain language. You can then ask it questions to verify the audience is exactly what you intend it to be.
    </Tip>
  </Accordion>

  <Accordion title="Preview the list and check a few contacts.">
    Preview the list and click into a contact record to check that the contact meets each filter criteria.

    * Does the contact’s attributes match the filter criteria?
    * Does the contact have the included product activity or marketing activity?
    * Does the contact meet the exclusion criteria?

    <Tip>
      In some cases, it can help to export the full dynamic list preview and spot check domains or org IDs.
    </Tip>
  </Accordion>

  <Accordion title="Assess potential risk to deliverability.">
    Depending on the following answers, the send may deserve additional care. How many contacts in the audience:

    * have shown sign-of-life in the last 6 months? (marketing activity or product activity)
    * have been delivered an Inflection email in the past 6 months?
    * are more than 6 months old?

    Sending to a stale list can cause a high bounce rate, low engagement, and a high unsubscribe rate. Steps to take to protect your sender reputation and optimize engagement:

    1. Include activity criteria with a timeframe of 6 months or less.
    2. In the absence of activity criteria, limit the send to contacts created or successfully delivered an email within the last 6 months.
    3. Verify the list with a third-party vendor that will rate the reliability of each email address and check for spam traps.
  </Accordion>
</AccordionGroup>


# Data Dictionary
Source: https://docs.inflection.io/database/data-dictionary

As you build a dynamic list, the data dictionary panel shows population stats, value distributions, and a searchable list of real values for the field you're filtering.

## Demo video

[Watch the demo video on Loom](https://www.loom.com/share/62d2c70f6a8542a88368634355ec3faa)

The Data Dictionary tells you what's in your data before you build with it. As you build a dynamic list, journey branch, or conversion event filter, the insights from data dictionary panel shows population stats, value distributions, and a searchable list of real values for the field you're filtering on. Admins can add descriptions to any field so everyone on the team knows what each field represents.

## Summary

The Data Dictionary surfaces two capabilities:

* **Insights from data dictionary:** a side panel that opens inside the filter row while you build a dynamic list, journey branch, or conversion event.
  * It shows the field's description, how many records have a value for it, and a field specific distribution.
  * For text fields, it includes a searchable list of distinct values sorted by frequency that you can click to add to your filter.
* **Field description:** an inline description on each field row in Unified Mapping that admins can edit. Descriptions appear inside Insights from data dictionary while building filters.

## Insights from Data Dictionary

While building a filter in a dynamic list, click the data dictionary icon next to the operator dropdown. The panel opens to the right of the filter row.

<img alt="Insights from data dictionary panel open beside a filter row in the dynamic list builder" />

### What the Panel Shows

The panel adapts to the field's type:

| **Field type** | **What you see** |
| - | - |
| String | Description, % populated, count of distinct values, and a searchable list of distinct values sorted by frequency. |
| Number | Description, % populated, count of distinct values, minimum, and maximum. |
| Datetime | Description, % populated, count of distinct values, earliest, and latest. |
| Boolean | Description, % populated, count of true values, and count of false values. |

<img alt="Data dictionary panel showing field stats and a searchable list of distinct values" />

### Inserting Values from the List

For text fields, click any value in the list to insert it into the filter. If the operator allows multiple values (for example, **is any of**), click as many values as you need to build up the filter.

For **contains**, **starts with**, and **ends with** operators, you can still type values manually.

## Field Descriptions

Admins can add a plain-English description to any field on the contact, account, product user, or org entity. Descriptions help everyone on your team and Inflection's AI agents understand what each field actually represents.

### Read a Description

Anyone can read descriptions:

* Inside **Insights from data dictionary** while building a filter.
* On the field row in **Unified Mapping:** click **View description** to expand the description inline.

When no description exists, the field row stays silent for non-admins.

### Add or Edit a Description

Only workspace admins can add or edit descriptions.

1. Click **Database** in the left navigation, then click **Contact Fields** or **Account Fields**.
2. Find the field you want to describe.
3. Click **View description** on the field row, then click **Edit**.
4. Enter a plain-text description (up to 300 characters) and save.

<img alt="Editing a field description inline on a field row in Unified Mapping" />

Descriptions are saved immediately to the field's record. They appear in Insights from data dictionary the next time someone opens the panel — no separate sync step is required.

## Where Insights from Data Dictionary Appears

Insights from data dictionary is available everywhere you build field-based filters:

| **Surface** | **Where to find it** |
| - | - |
| Dynamic list builder | Inside any person property filter row. |
| Journey Branch by Filter | Inside any person property filter in the branch step. |
| Journey Branch by Value | Inside the field selector when defining branch values. |
| Conversion event filters | Inside contact, account, product user, or org property filters on a conversion event trigger. |

## What's Excluded

A few internal system columns Inflection uses never appear in Insights from data dictionary or anywhere else in the product. These include `_modified_time`, `_created_time`, `_source`, `_deleted_time`, and `_is_deleted`.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Why don't I see a description for a field?">
    Descriptions are optional and admin-managed. If a field doesn't have a description yet, ask your workspace admin to add one in Unified Mapping. Once saved, the description appears in Insights from data dictionary on the next open.
  </Accordion>

  <Accordion title="Which fields can have a description?">
    Admins can add descriptions to fields on the contact, account, product user, and org entities. Internal system columns (fields starting with an underscore) are excluded.
  </Accordion>

  <Accordion title="Why does the panel show stats that look slightly out of date?">
    Insights data is cached for 2 hours in production. If you've just updated your data and want to see the latest stats, wait for the cache to expire or open the panel for a field that hasn't been opened recently.
  </Accordion>

  <Accordion title="Is there a standalone Data Dictionary page I can browse?">
    Not in this release. Insights from data dictionary is available inline while you build filters. A standalone page that lets you audit your data across all entities is on the roadmap for a future release.
  </Accordion>

  <Accordion title="Can I see what fields are mapped and what's changed over time?">
    Not in this release. A self-serve audit of mappings — including which integration writes to each field and when fields were first or last seen — is on the roadmap for a future release.
  </Accordion>

  <Accordion title="Are descriptions readable by Inflection's AI agents?">
    Yes. Descriptions are made available to Inflection's agents so they can reason about your fields accurately. The more carefully your fields are described, the better the agents can ground their work in your data model.
  </Accordion>
</AccordionGroup>


# Data Normalization
Source: https://docs.inflection.io/database/data-normalization

Data normalization helps you maintain clean, consistent contact data across your organization.

## Overview

Data normalization helps you maintain clean, consistent contact data across your organization. By mapping inconsistent source values (like "US", "United States", "USA", and "U.S.A.") to a single standardized target, you ensure reliable reporting, accurate audience segmentation, and effective personalization - without manual data cleanup.

<Info>
  **Key Concepts**

  * **Source field**: The contact field containing raw, inconsistent data (e.g., `country`).
  * **Output field**: The contact field where normalized values are written. This can be the same as the source field (overwrite), or a different field.
  * **Normalized value**: A clean, standardized value that one or more source values map to (e.g., "United States").
  * **Source value**: A raw value from your data that maps to a normalized value (e.g., "US", "USA", "U.S.A."). Source values are **case-insensitive.** "usa" and "USA" are treated as the same value. Click the **Tt** icon to view all case variants in your data.
  * **Unmapped values**: Source values that have not yet been assigned to any normalized value. Unmapped values are kept as-is, their original value is preserved unchanged
  * **Backfill**: Applying normalization to existing historical records, not just new incoming data.
</Info>

<AccordionGroup>
  <Accordion title="Navigating to Data Normalization">
    Click **Database** in the left sidebar, then select **Data Normalization**. The page has three tabs:

    * **Normalization Configurations:** Shows all fields with existing normalization configurations. Configurations that need review (new unmapped values detected) sort to the top with an indicator. Each row shows the field name, output field, unique value count, record count, status, and last updated time.
    * **Available Field:** Lists all contact string fields that can be normalized. Shows the field name, number of unique values, and number of populated records.
    * **Activity Log:** Chronological record of all normalization configuration changes. Filter by date range (30 days, 90 days).
  </Accordion>

  <Accordion title="Field Eligibility">
    Normalization is available for **contact fields only**. Within the contact entity, only **string fields** can be normalized.

    Certain default fields are restricted from normalization, including `email`, `id`, `first_name`, and `last_name`. Other default string fields like `company_name` and `title` are eligible.

    Navigate to **Database → Data Normalization → Available Fields** to see which fields are eligible. Fields that cannot be normalized display an explanation of why.

    <img alt="Available Fields tab listing contact string fields eligible for normalization" />
  </Accordion>

  <Accordion title="Create a Normalization Configuration">
    <AccordionGroup>
      <Accordion title="Step 1: Mapping Guidance">
        1. Navigate to **Database → Data Normalization → Available Fields**.
        2. Click **Normalize** next to the field you want to configure.
        3. Configure how the AI-powered mapping engine should generate initial mappings. Both options below are optional, can be used independently or together, and the combined input must stay under 10,000 characters.

           * **Let AI decide:** Provide optional instructions to guide the AI (e.g., "Use 2 letter ISO codes for Country"). The AI analyzes your instructions alongside the existing source values and suggests groupings. If you don't provide instructions, the AI generates mappings based on patterns in your data.
           * **Use my own list:** Provide your own target normalized values by typing or pasting them directly, or by uploading a CSV file (max 3 MB). If the source field has a linked **Salesforce picklist**, the picklist values are automatically loaded as your target list. The AI then maps your source values to the values in your list.

           You can use both at the same time, for example, provide a list of target values and add instructions for how the AI should handle edge cases.

           <img alt="Mapping Guidance step with Let AI decide instructions and Use my own list options" />
        4. Click **Generate Mappings** to run the AI mapping.

        <Info>
          AI mapping is non-deterministic. If you are not happy with the initial results, go back, refine your prompt or list, and generate again.
        </Info>

        <Info>
          For fields with a large number of unique values, AI mapping may take longer to process. If you have a high-cardinality fields above 10,000 values, reach out to your Customer Success team, and they can help you plan the best approach and involve the Inflection team if needed.
        </Info>
      </Accordion>

      <Accordion title="Step 2: Mapping Configuration">
        After the AI generates mappings, review the results. The screen shows:

        * A table of **normalized values** (left column) with their **source values** (right column), each showing a record count
        * An **Unmapped Values** section at the bottom showing source values the AI could not confidently assign
        * A header showing total unique values, total records, and a count of values still to review

        #### Review and approve mappings

        Each normalized value group shows a count of values "to review". These are AI-generated mappings that you haven't yet confirmed. Click **Approve** on a group to confirm its mappings, or click **Approve All** in the header to approve every group at once.

        <img alt="Mapping Configuration screen with normalized value groups and Approve buttons" />

        #### Edit mappings

        * **Drag and drop:** Drag a single source value from one group to another, or from the unmapped section into a group.

          <img alt="Dragging a source value between normalized value groups" />
        * **Bulk move from unmapped values:** Use the search bar in the **Unmapped Values** section to filter values (e.g., typing "was" shows all unmapped values containing "was"). A **"Move all (N) to..."** button appears with the count of matching results.

          Click it to see a searchable list of existing normalized value groups, then select a destination, all matching values move to that group at once.

          <img alt="Unmapped Values section with search filter and Move all button" />
        * **Bulk move within a normalized value group:** When a group has more than 3 source values, click **+N MORE** to open the **Source Values** drawer for that group. Use the search bar in the drawer to filter values, then click **"Move all (N) to..."** to select a different normalized value group or **Unmapped** as the destination.

          <img alt="Source Values drawer with search and bulk move options for a group" />
        * **Add a source value to a group:** Click **+ Add** next to any group's source values to manually type in a new source value.
        * **Add a new normalized value:** Use the "Add normalized value..." input at the top of the mapping table and click **+ Add** to create a new empty group, then drag or bulk-move values into it.
        * **View case variants**: Click the **Tt** icon next to a source value to see all the different case variations that exist in your data (e.g., "Google", "google", "GOOGLE"). Source values are still matched case-insensitively, you cannot map different casings to different buckets but this lets you see exactly what forms appear in your raw data.

          <img alt="Case variants popover showing all casings of a source value" />
        * **Remove a source value from a group:** Click the **X** on a source value tag to move it back to unmapped.
        * **Remove an entire group:** Click the **X** on the group row to move all its source values back to unmapped and delete the group.

        #### Handle unmapped values

        Before you can save, all unmapped values must be resolved. Values you don't want to assign to a specific normalized value are automatically **kept as-is** the original value is preserved unchanged in the output field. You can click **Approve** to confirm them in bulk.

        <img alt="Unmapped Values section with values kept as-is and an Approve button" />
      </Accordion>

      <Accordion title="Step 3: Settings">
        Configure the **output field** where normalized values are written:

        * **Overwrite original field:** Replace the source field values with normalized values. Note that this overwrites the raw data; if you want to preserve the original values, use one of the options below instead.
        * **Write to existing field:** Select a different contact field as the output.
        * **Create new field:** Create a new custom contact field directly from this screen. The field is created as a Contact Field in Inflection

          <img alt="Settings step with output field options: overwrite, existing field, or create new field" />

        <Info>
          If you want to preserve your raw data while also sending normalized values to an external system like Salesforce, consider writing to a separate output field. For example, you could keep the source field as read-only (to preserve raw values) and set the output field to two-way sync so normalized data flows to Salesforce.
        </Info>
      </Accordion>

      <Accordion title="Step 4: Review & Save">
        Review a summary of your configuration:

        * Total normalized values and source values
        * Output field selection
        * Count of Unmapped values kept as-is

        Click **Save & Apply**. You'll be asked how to apply the configuration:

        * **Apply going forward only:** Only normalize new incoming data. Existing records remain unchanged.
        * **Backfill historic values:** Apply normalization to all existing records. This runs in the background and may take some time. You'll see a "backfill started" entry in the Normalization Activity Log, and a "backfill completed" entry when it finishes.
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Manage Existing Configurations">
    <AccordionGroup>
      <Accordion title="Handle New Unmapped Values">
        When new source values appear in your data that don't match any existing mapping, they surface in the **Normalization Configurations** tab with an 'unmapped' status indicator showing the count of new unmapped values.

        <img alt="Normalization Configurations tab with an unmapped status indicator on a configuration" />

        To resolve them:

        1. Click on the configuration with unmapped values.
        2. Review the new unmapped values in the Mapping Configuration step.
        3. Drag them into existing groups, create new normalized values, bulk-move them, or keep them as-is.
        4. Save your changes.
      </Accordion>

      <Accordion title="Edit a Configuration">
        1. Navigate to **Database → Data Normalization → Normalization Configurations**.
        2. Click on the configuration you want to edit.
        3. The edit flow has three steps: **Mapping Configuration**, **Settings**, and **Review & Save** (the Mapping Guidance step is skipped since mappings already exist).
        4. Modify mappings as needed: add new normalized values, reassign source values, or approve new mappings.
        5. Click **Save & Apply** and choose your backfill preference.

        Existing approved mappings are preserved when you edit. Only new or changed mappings are applied.
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Normalization Activity Log">
    The **Normalization Activity Log** tab records all configuration-level changes:

    * **Configuration created:** Logged when a new normalization configuration is saved.
    * **Configuration updated:** Logged with the source and output field names and details of what changed.
    * **Backfill started:** Logged when a backfill process begins.
    * **Backfill completed:** Logged when the backfill process finishes.

    Each log entry includes:

    * **Timestamp** (date and time)
    * **Actor** (user name or "System" for automated changes)

    Filter logs by **date range** (30 days, 90 days, or custom) to find specific entries.
  </Accordion>

  <Accordion title="Contact Activity Log">
    When normalization modifies a contact's field value, either through real-time normalization of new data or through a backfill, an entry is recorded in that individual contact's **Activity Log**. This lets you trace exactly when and how a specific contact's data was changed by normalization.

    To view these entries, navigate to a contact's profile and open their Activity Log.

    <img alt="Contact Activity Log entries showing field value changes made by normalization" />
  </Accordion>

  <Accordion title="Best Practices">
    * **Start with high-impact fields:** Focus on fields used in reporting and segmentation first, like job title, company name, or industry.
    * **Leverage Salesforce picklists** for fields synced from Salesforce to keep both systems aligned.
    * **Review new unmapped values regularly:** New source values appear as your data grows. Periodic review ensures your normalization stays current.
    * **Iterate on your prompt:** AI mapping is non-deterministic. If the initial results aren't right, go back and refine your prompt or add more specific instructions, then regenerate.
    * **Preserve raw data when needed:** If you want to keep the original source values intact, write normalized values to a separate output field rather than overwriting the source field.
    * **Reach out for high-cardinality fields:** If your field has a very large number of unique values, contact your Customer Success team for guidance. They can involve the Inflection team to help plan the best approach.
  </Accordion>
</AccordionGroup>

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Which fields can I normalize?">
    Only string fields on the Contact entity are eligible. Certain default fields like `email`, `id`, `first_name`, and `last_name` are restricted. Other default string fields like `company_name` and `title` can be normalized.
  </Accordion>

  <Accordion title="Are source values case-sensitive?">
    No. Source value matching is **case-insensitive** "United States", "united states", and "UNITED STATES" are all treated as the same source value. However, the casing of the normalized value you define is preserved exactly as you enter it. You can click the **Tt** icon next to any source value to see all the case variations that exist in your data.
  </Accordion>

  <Accordion title="Can I normalize a field to itself?">
    Yes. Select **Overwrite original field** in the Settings step. The raw value is replaced with the normalized value. Keep in mind this overwrites the original data.
  </Accordion>

  <Accordion title="Can two configurations share the same source field?">
    Yes. Two separate normalization configurations can use the same source field, as long as each has a different output field.
  </Accordion>

  <Accordion title="What happens if I try to move a normalized value into another group?">
    This creates a circular mapping and is not allowed. The system prevents you from moving a value that is already a normalized value for another group.
  </Accordion>

  <Accordion title="What is the maximum file size for CSV uploads?">
    CSV files used for list-based mapping are limited to **3 MB**.
  </Accordion>

  <Accordion title="What happens to existing data when I create a new configuration?">
    It depends on your choice at save time. If you select **Backfill historic values**, all existing records are updated asynchronously in the background. If you select **Apply going forward only**, existing records remain unchanged.
  </Accordion>

  <Accordion title="Can I undo normalization?">
    Configurations can be edited at any time. However, if you backfilled historical records and used the **Overwrite original field** option, the original raw values have been replaced. If you wrote to a **different output field**, your original source field data is untouched.
  </Accordion>

  <Accordion title="What if the AI mapping doesn't look right?">
    AI mapping is non-deterministic, running it again with the same prompt may produce different results. Go back to the Mapping Guidance step, refine your prompt or adjust your target value list, and click **Generate Mappings** again. You can iterate as many times as needed before saving.
  </Accordion>

  <Accordion title="Can I bulk-move unmapped values?">
    Yes. In the **Unmapped Values** section, use the search bar to filter values, then click **"Move all (N) to..."** to select a target normalized value group. All matching values move at once. You can also drag and drop individual values. For normalized value groups with more than 3 source values, click **+N MORE** to open the drawer, where the same search and bulk move functionality is available.
  </Accordion>

  <Accordion title="My field has a lot of unique values. What should I do?">
    For high-cardinality fields, AI mapping may take longer and require more manual review. Reach out to your Customer Success team, they can help you plan the best approach and involve the Inflection team if needed.
  </Accordion>

  <Accordion title="How quickly are new incoming values normalized?">
    New values matching an existing normalization configuration are normalized immediately upon ingestion.
  </Accordion>

  <Accordion title="Can other entities besides Contact be normalized?">
    Currently, normalization is available for the **Contact** entity only.
  </Accordion>

  <Accordion title="Can I add a source value to a group manually?">
    Yes. Click **+ Add** next to any group's source values to type in a value that may not be in the current dataset yet.
  </Accordion>

  <Accordion title="How do I know when a backfill is done?">
    Check the **Normalization Activity Log**. You'll see a "backfill started" entry when the process begins and a "backfill completed" entry when it finishes.
  </Accordion>

  <Accordion title="Where can I see normalization changes on a specific contact?">
    Individual contact-level normalization changes appear in that contact's **Activity Log** on their profile page, not in the Normalization Activity Log.
  </Accordion>
</AccordionGroup>


# Importing Contacts
Source: https://docs.inflection.io/database/importing-contacts

Populate your database with existing contact lists while maintaining full control over field mapping and list organization.

Importing contacts via CSV enables you to efficiently populate your database with existing contact lists while maintaining full control over field mapping and list organization. Use CSV imports to create new contacts, update existing records, or both—streamlining your data management and ensuring your contact database stays current.

## CSV Minimum Requirements

* A column with at least one valid email ID
* A complete header row
* \< 500 MB file size

<Info>
  By importing contacts via CSV or any other means into Inflection, you agree to our anti-spam policy
</Info>

## Upload Contacts Using CSV Files

1. Navigate to **Static Lists** from the sidebar.

   <img alt="Static Lists in the sidebar" />

2. Click **New static list** in the top right corner or select an existing static list. Select **Actions** > **From a CSV file**.

   <img alt="Actions menu with From a CSV file option" />

3. In the modal that appears, browse or drag-and-drop the CSV file you wish to upload.

   <img alt="CSV upload modal with drag-and-drop area" />

4. Map your CSV columns to existing Contact fields in Inflection. Proceed with the suggested mapping or adjust the columns as needed.

   <img alt="Column mapping screen for CSV import" />

   A checkmark appears next to each mapped column when the data matches the contact field data type. Preview the first few rows of your CSV file to verify your field content.

   Filter column names by searching or by selecting unmapped/mapped options.

   <img alt="Filter columns by mapped or unmapped status" />

5. Review the summary page showing total entries, new contacts, and errors in your file.

   <img alt="Import summary page with entry counts and errors" />

   Download the error report for detailed insights into any errors in your CSV file.

   Adjust your import settings and choose to upload contacts to a new or existing static list.

   Click **Import** when satisfied with your configuration.

6. Click **Import Contacts** on the final confirmation page to complete the import.

## Import Options

Control how CSV data updates your contact database by selecting one of three import behaviors:

* **Only Create New Contacts:** Creates new contacts from email IDs not found in your Contact database. Ignores existing email IDs.
* **Only Update Existing Contacts:** Updates existing contacts with new data from your CSV. Only non-blank CSV cells update existing values.
* **Create and Update Existing Contacts:** Combines both behaviors above. Updates existing email ID contacts with non-blank values and creates new contacts from new email IDs.

Override the default update behavior with these options:

* **Update Empty Fields Only:** Update only empty contact fields during the import process, leaving populated fields unchanged.
* **Overwrite with Blank Values:** Replace existing Inflection data with blank values from the CSV.

<Warning>
  **Warning:** Enabling this option will result in the removal of existing contact properties if they are left blank in the CSV. Please exercise caution when enabling this option.
</Warning>

<img alt="Import options for creating and updating contacts" />

## Troubleshoot Upload Errors

### Encoding Error

Upload UTF-8 encoded CSV files only. Ensure your file uses UTF-8 encoding before uploading.

### Upload Failed

Retry the upload if it fails due to network or backend issues.

### File Size Limit Exceeded

Split files larger than 500MB into smaller files and upload them separately.

### Column Header Missing

Add headers to all columns in your CSV file before uploading.

## Understand Error Reports

When Inflection processes your CSV file, invalid or error-prone fields are marked with error notes directly in the file. Download this error report to make corrections and re-upload your file.

### Invalid Email

Invalid email addresses are flagged in the error report. Correct these addresses and re-upload the file.

### Mismatched Data Types

Fields that do not match the expected Inflection property data type are flagged. Correct these fields according to Inflection data type requirements.

### Duplicate Entries

Duplicate entries based on the email field are ignored and flagged in the error report.

### Invalid Enumeration Option

Values that do not match existing options in a standard picklist or boolean field are flagged.

Download the error report—a copy of your original CSV file with an added column specifying the error per row—make corrections, and re-upload the file.


# Segments
Source: https://docs.inflection.io/database/segments

Organize and manage audiences using agentic intelligence; with complete review/edit controls via the UI.

Inflection Segments lets you organize and manage audiences. Segments contain multiple sub-segments that are mutually exclusive Dynamic Lists that automatically update based on the defined criteria. Segments can be used to target the right people in your journeys.

<AccordionGroup>
  <Accordion title="Accessing Segments">
    To access segments in Inflection, navigate to **Database > Segments** from the main menu. You'll see a list of all your segments with their descriptions, last refreshed dates, and last updated dates.

    <img alt="Segments listing page with descriptions and refresh dates" />
  </Accordion>

  <Accordion title="How to use Segments in Dynamic Lists">
    Segments can be used as filters in Dynamic Lists throughout Inflection, including in journey audiences.

    To use a segment in a Dynamic List:

    1. Open the Dynamic List editor (e.g., when defining a journey audience)
    2. Click **Add condition**
    3. Select **Person segmentation**
    4. Choose the segment you want to use from the dropdown (e.g., "Target User Personas")
    5. Select the specific sub-segment (e.g., "Marketing Operations Professionals at PLG Companies")
    6. The Dynamic List will now filter to include only contacts matching that segment

       <img alt="Person segmentation filter in the Dynamic List editor" />
  </Accordion>

  <Accordion title="How to create a new segment">
    Currently, Segments can only be created using AI Chat (requires AI features to be enabled in your instance).

    If you have AI features enabled, you can create segments using natural language:

    1. Use the AI to describe your desired audience in plain language (e.g., "Create a segment of customers who logged in the last 30 days")
    2. The AI will generate a segment
    3. Ask AI to save the segment in Inflection

    <Tip>
      **Tip:** Start by creating a initial segment with AI, then refine it through the UI for precision.
    </Tip>

    <Note>
      **Note:** Manual segment creation via the UI will be available in the future.
    </Note>

    <img alt="Creating a segment with AI Chat" />

    <img alt="AI-generated segment saved in Inflection" />
  </Accordion>

  <Accordion title="How to edit a segment">
    All users and admins can edit existing segments, regardless of whether they have AI features enabled.

    1. Navigate to **Database > Segments**
    2. Click on the segment you want to edit
    3. Click on the specific sub-segment you want to edit (if applicable)
    4. In the Dynamic List view, you can:
       * Edit the segment name and description
       * Modify criteria and conditions
       * Reorder segment conditions by dragging and dropping
       * Add conditions to reference other segments (e.g., filter by "where segment category is... Target User Personas")
       * View the current segment count
       * See **Last Updated** timestamp (when the segment configuration was last changed)
       * See **Last Refresh** timestamp (when the segment data was last refreshed)
    5. Click '**Save changes**'

       <img alt="Editing a sub-segment in the Dynamic List view" />

    Any journeys using this segment will automatically reflect the updated criteria.

    <Tip>
      **Important:** After editing a segment, it takes approximately **10 minutes** for the changes to fully reflect and for the segment data to refresh.
    </Tip>

    <Note>
      **Note:** While only users with AI enabled can create segments via chat, all users can view, edit, and manage existing segments through the Dynamic List interface.
    </Note>
  </Accordion>

  <Accordion title="How to delete a segment">
    To delete a segment, please reach out to the Inflection team

    <Note>
      **Note:** Deleting a segment will remove it from any journeys currently using it.
    </Note>

    <Tip>
      **Coming soon:** The ability to delete segments directly via the UI will be available in the future.
    </Tip>
  </Accordion>

  <Accordion title="Understanding segment exclusivity and order">
    A contact can only exist in **one sub-segment** within a segment at a time. If a contact qualifies for multiple sub-segments, **order** determines which sub-segment they belong to.

    **How ordering works:**

    * Sub-segments are evaluated from **top to bottom**
    * Once a contact matches a sub-segment, they are assigned to it and evaluation stops
    * Contacts are not evaluated against sub-segments below their match
    * The order of sub-segments is critical - place your most specific or high-priority segments at the top

      <img alt="Ordered sub-segments within a segment" />

    **Example:**

    If you have a "Target User Personas" segment with sub-segments ordered as:

    1. VP of Marketing at Enterprise Companies
    2. Marketing Managers at SaaS Companies
    3. Other Marketing Professionals

    A contact who is a "VP of Marketing at a SaaS Company" would be assigned to sub-segment #1 (VP of Marketing at Enterprise Companies) if they meet that criteria first, even though they might also qualify for #2.

    Use the drag-and-drop functionality to reorder sub-segments and ensure the most important or specific segments are prioritized at the top.
  </Accordion>

  <Accordion title="Understanding segment metadata">
    When viewing a segment, you'll see two important timestamps:

    * **Last Updated**: Shows when the segment configuration was last modified (e.g., criteria changed, conditions added/removed)
    * **Last Refresh**: Shows when the segment data was last refreshed to reflect current contact information

    These timestamps help you understand the current state and accuracy of your segment data.

    <Note>
      Note that segments will automatically refresh once daily, or within 10 minutes of an update.
    </Note>
  </Accordion>
</AccordionGroup>


# Account Provisioning
Source: https://docs.inflection.io/getting-started/account-provisioning

Provision your Inflection account, sign in for the first time, and invite new users to join.

## Provision your Inflection account

The account provisioning process establishes and activates your Inflection account.

The primary administrator of the account will receive an invitation email from the Inflection team to join the account. The admin will establish a user password and sign in to the Inflection account for the first time. Note that an Inflection team member will be an admin in the account to facilitate set up.

## Access your Inflection account

To sign in to your Inflection account, visit [https://app.inflection.io](https://app.inflection.io) and log in.

## Invite new users to your Inflection account

To add new users:

1. Navigate to **Settings > Users**
2. Click the **Invite Users** button in the top right corner
3. Enter user name and email address for the user you are inviting
4. Indicate user role from the dropdown
5. Click **Send Invite**

The user will receive an email invitation to join the account. Note that the invitation expires after a 3 days.


# Domain Authentication
Source: https://docs.inflection.io/getting-started/domain-authentication

Enable sending emails from your Inflection account.

## Authenticate your sending domain

Domain authentication is the process of verifying that an email is sent from the sender they claim to be. It is an important process in blocking harmful content such as phishing scams. Most commonly used email authentication standards are SPF, DKIM, and DMARC. Domain authentication is required in order to send email from your Inflection account.

## What is SPF, DKIM, and DMARC?

These three are email authentication standards for the reduction of spam.

* **SPF** helps verify whether the sender’s IP address is allowed to send on behalf of the sender’s domain.
* **DKIM** helps to confirm that the email message was not altered during the sending process.
* **DMARC** establishes a method that allow domain owners to state what actions that should be handled when the email fails on authorization test.

## Set up domain authentication

To set up domain authentication, you must install DNS records provided by Inflection (via SendGrid) to your DNS or hosting provider:

1. Determine who your hosting provider is and make sure you have access required to install DNS records.
2. If you don’t have access to your DNS or hosting provider, determine who in your company is able to make DNS modifications for your domain. A good place to start is with your IT organization.
3. Add DNS records provided by Inflection (via SendGrid) to your DNS host. Once added, click **I’m Done button** on the email sent by Inflection (via SendGrid).
4. For additional instruction and troubleshooting tips, visit [Sendgrid’s doc on troubleshooting sender authentication](https://docs.sendgrid.com/ui/account-and-settings/troubleshooting-sender-authentication).


# MMCs (Monthly Marketed Contacts)
Source: https://docs.inflection.io/getting-started/mmcs

Understand Inflection pricing.

## What is an MMC?

Inflection pricing is based on MMCs, or Monthly Marketed Contacts.

* MMCs are unique contacts (unique by email address) who route through one or more Inflection journeys in a given calendar month (i.e. August 1-August 31).
* Inflection does not charge for contact database volume, marketable contacts, seats or data volumes.
* Non-personalized batch journeys (i.e. Newsletters) do not count against MMC cap, provided there are no MMC-triggering elements in the batch journey.

## MMC Journeys

A journey's contacts will be MMC-qualifying if **ANY** of the following criteria is met:

### Journey Settings

* Journey schedule is set to `Recurring` or `High frequency`.
* Journey settings contain `Exit criteria`.

### Email Action Flow Steps

* Journey has a `Send email` flow step or `Send internal email alert` flow step where the email includes a `Token`, `Column Accessor Token` or `Jinja` templating.

### Journey Control Flow Steps

* Journey canvas contains `Branch by value` flow step.
* Journey canvas contains `Branch by token` flow step.
  * **Note**: `abSplit()` and `randint()` tokens are **exceptions** and are not MMC-qualifying.
* Journey canvas contains `Branch by filter` flow step.
* Journey canvas contains `Nested journey` flow step.

### Integration Flow Steps

* Journey canvas contains `Run outbound webhook` flow step.
* Journey canvas contains `Add to Salesforce Campaign` flow step.

### List Action Flow Steps

* Journey canvas contains `Add to static list` or `Remove from static list` flow steps.

### Data Action Flow Steps

* Journey canvas contains `Update value` flow step.

### Trigger Journeys

Every contact who enters a Trigger Journey counts toward your MMC for that month. Unlike Scheduled Journeys — which are MMC-qualifying only when they include one of the elements above — Trigger Journeys are always MMC-qualifying, because they deliver personalized, real-time follow-up to individual contacts.

* A contact is counted as one MMC per calendar month (unique by email), even if they trigger the journey multiple times.
* The contact is counted in the month they are enrolled, when the trigger fires.

<Info>
  Learn more about real-time enrollment: [Trigger Journeys](/journeys/trigger-journeys)
</Info>

## Non-MMC Journeys

Journeys that do not meet the criteria above are non-MMC batch journeys.

* If a contact is **only** in non-MMC batch journeys, the contact will not count as an MMC.
* Inflection applies a high ceiling for non-MMC batch contacts. It is typically a multiplier of your MMC cap (see your contract for details).
* The intention is to allow you to consolidate your email communications in one place, while only paying for your highest-value (personalized) emails.


# Data Warehouse Questionnaire
Source: https://docs.inflection.io/getting-started/onboarding/data-warehouse-questionnaire

Onboarding questionnaire to prepare your data warehouse connection to Inflection.

Complete this document and share with your Inflection team and data warehouse administrator.

`This document has generic placeholder information. Replace it with information relevant to your business.`

## Scope of Sync

1. Who is your data warehouse provider? `BigQuery / Snowflake / Redshift`
2. Which tables will you sync? How many records are in each, how many fields, and what volume of updates should we expect?
   1. `Product Users`
      1. `1M records`
      2. `10 fields`
      3. `10K updates/day`
   2. `Product Orgs`
      1. `200K records`
      2. `5 fields`
      3. `2K updates/day`
   3. `Product Activities`
      1. `100M records`
      2. `average of 5 attributes per event`
      3. `1M updates/day`
   4. Add/edit as necessary
3. What fields and/or events does Inflection need to support your Inflection journeys? This list should include any event or property that will be used in targeting, segmentation, dynamic content, or other personalization; and success criteria or exit criteria.
   1. `Product Users` (delete section if not appliable)
      * `Email Address (required)`
      * `User ID`
      * `Persona`
   2. `Product Orgs` (delete section if not appliable)
      * `Workspace ID`
      * `Plan`
   3. `Product Activities` (delete section if not appliable)
      * `Signed Up`
      * `Created Item`
      * `Activated Item`
      * `Exported Item`
4. How many product users do you have?
   1. Daily active users: `#`
   2. Monthly active users: `#`
5. How frequently will you sync to Inflection? (Common frequencies are every 4h, 8h, or 24h) `# hours`
6. Will you sync tables or views?

### Next Steps

Share this with your Inflection team and your data warehouse administrator as part of the integration request.

Read and share with your data warehouse administrator our [data warehouse connection documentation](/connections/import-from-data-warehouse).


# Journey Brief & Data Requirements
Source: https://docs.inflection.io/getting-started/onboarding/journey-brief-data-requirements

Onboarding template for defining your first journeys and the data they require.

## Journey Brief

`This document has generic placeholder information. Replace it with information relevant to your business.`

### Goal

What business metric will this journey impact? `Free-paid conversion`

### Audience

Who will this journey target? Describe the audience in plain language. `Members of our free plan.`

### Journey Steps

What will the audience experience be? Describe the overall flow in plain language.

* `A new journey member will receive a welcome email personalized by Persona.`
* `The next few emails will encourage free plan members to create an item in the product.`
* `Once they reach that milestone, they should receive the next few emails encouraging them to reach the next milestone: activate the item.`
* `Once they reach that milestone, they should receive the next few emails, encouraging them to reach the next milestone.`
* `If at any point the user upgrades to a paid workspace, they should be dropped from the flow.`

Number of emails in journey: `10`

Personalization:

* `Each persona will receive messaging tailored to the persona. Our personas are:`
* `When a milestone behavior is completed, users should move to the next milestone emails.` `Our milestone behaviors are:`

Follow-up: Describe the ideal experience a user will have after completing this journey.

* `If the user upgrades to paid, they will receive onboarding emails from their account CSM. These are sent from another system.`
* `If the user does not upgrade to paid, they will receive ongoing newsletters and product release announcements. These are sent from another system.`

### Other Specs

* My journey will be `recurring` / `only run one time`.
* If a contact has more than one user who qualifies for my journey, they should only be added to the journey one time. `T/F`

## Data Requirements

### Data points

What data points are needed to identify your audience? Indicate their source systems as well.

| Data Point | Description | Reason | System |
| - | - | - | - |
| `Plan` | `which tier of our product they pay for (free, enterprise, etc.)` | `Audience targeting` | `BigQuery` |
| `Sign-up Date` | `when they signed up for our product` | `Audience targeting` | `Segment` |
| `Persona` | `marketing, operations, sales, etc.` | `Personalization` | `BigQuery` |
| `Behavior Milestones` | `like whether they created an item, activated an item, exported an item, etc.` | `Personalization` | `Segment` |

### Systems

Who owns the systems mentioned above?

`Segment: Marketing Operations`

`BigQuery: Our Data Team`

## Next Steps

1. Share this with your Inflection customer success team.
2. Once finalized with them, you will move onto defining the scope of data needed from your connections via the following questionnaire(s):
   * [Salesforce Questionnaire](/getting-started/onboarding/salesforce-questionnaire)
   * [Segment Questionnaire](/getting-started/onboarding/segment-questionnaire)
   * [Data Warehouse Questionnaire](/getting-started/onboarding/data-warehouse-questionnaire)


# Onboarding Checklist
Source: https://docs.inflection.io/getting-started/onboarding/onboarding-checklist

The technical, communication, and staffing requirements to unlock the full potential of Inflection.

Inflection.io allows companies to activate their product data, sales data, and marketing data to drive more pipeline, product adoption, and revenue expansion.

The following checklist will help you unlock the full potential of the platform.

## Technical Implementation

### Sending Domain

* [ ] Align on the sending domain(s) that will be used for Inflection emails.
* [ ] Connect with IT to make sure they can provide a timely response to authenticate the sending domain. If your IT process requires a ticket to be submitted, submit early to ensure no undue delays.

### CRM

* [ ] Connect with your CRM administrator to ensure support for an integration with Inflection. Understand their process and timelines around supporting the integration. Share [our documentation](https://inflectionio.notion.site/Salesforce-Setup-Sync-73bfaadcccf448afa29b75798bcf36b0) and [use cases](https://inflectionio.notion.site/Connections-High-level-Use-Cases-24eaf642a4dd8055a5bae716aec53e58) with them.
* [ ] Complete [our Salesforce Questionnaire](/getting-started/onboarding/salesforce-questionnaire) and share with your Inflection team and your CRM administrator (as part of the request to support the integration).

### Segment

* [ ] Connect with the Segment administrator to make sure to support an integration with Inflection. Share [our documentation](https://inflectionio.notion.site/Segment-Connection-0fe6a33aaec14d98ab295bdc13b4f894) and [use cases](https://inflectionio.notion.site/Connections-High-level-Use-Cases-24eaf642a4dd8055a5bae716aec53e58) with them. Understand their process and timelines around supporting the integration.
* [ ] Complete [our Segment Questionnaire](/getting-started/onboarding/segment-questionnaire) and share with your Inflection team and your Segment administrator (as part of the request to support the integration).

### Data Warehouse

* [ ] Connect with your data warehouse administrator to make sure they can support an integration with Inflection. Share [our documentation](https://inflectionio.notion.site/Connecting-a-Data-Warehouse-fc87a2b283774b5391456c9c43e02403) and [use cases](https://inflectionio.notion.site/Connections-High-level-Use-Cases-24eaf642a4dd8055a5bae716aec53e58) with them. Understand their process and timelines around supporting the integration.
* [ ] Complete [our Data Warehouse Questionnaire](/getting-started/onboarding/data-warehouse-questionnaire) and share with your Inflection team and your Data Warehouse administrator (as part of the request to support the integration).

### Web

* [ ] Connect with your website administrator and make sure they can add an Inflection tracking script to your website. Share [our documentation](https://inflectionio.notion.site/Website-Tracking-1f8bb00462604f65aeec1538fb6b0e9d) and [use cases](https://inflectionio.notion.site/Connections-High-level-Use-Cases-24eaf642a4dd8055a5bae716aec53e58) with them. Understand their process and timelines around supporting the integration.

## Communication

* [ ] Connect with your security team to make sure you can join a Slack channel with your Inflection team. This is how we collaborate with you on support tickets, coordinate meetings, and share release notes.
* [ ] Be ready to work with your Inflection team to find a weekly time to set aside and meet. This will initially be used to work through implementation, and eventually get converted to an ongoing channel for support and partnership.

## Execution & Support Roles

* [ ] Identify who on your team will be responsible for creating emails in Inflection. This person should be able to support your team's unique needs (whether you use the WYSIWYG editor or HTML).
* [ ] Identify who on your team will be responsible for overall governance of Inflection, including compliance and data integrity.
* [ ] Identify who on your team will be responsible for understanding your new Marketing data model; this person will enable your team to understand how to build your audiences and personalize your communications.
* [ ] Identify who on your team will be an Inflection power user. This person will build audiences and journeys frequently. They often become your team's first line of defense for how-to questions and will likely develop your internal best practices and guidance on your specific implementation.


# Onboarding Center of Excellence
Source: https://docs.inflection.io/getting-started/onboarding/overview

Everything needed to hit the ground running and get the most out of Inflection.

These worksheets help define priorities and requirements for your Inflection implementation. Use them to collaboratively align internal teams on expectations for onboarding.

* [Journey Brief & Data Requirements](/getting-started/onboarding/journey-brief-data-requirements)
* [Onboarding Checklist](/getting-started/onboarding/onboarding-checklist)
* [Segment: Questionnaire](/getting-started/onboarding/segment-questionnaire)
* [Salesforce: Questionnaire](/getting-started/onboarding/salesforce-questionnaire)
* [Data Warehouse: Questionnaire](/getting-started/onboarding/data-warehouse-questionnaire)


# Salesforce Questionnaire
Source: https://docs.inflection.io/getting-started/onboarding/salesforce-questionnaire

Onboarding questionnaire to prepare your Salesforce connection to Inflection.

Complete this document and share with your Inflection team and Salesforce administrator.

`This document has generic placeholder information. Replace it with information relevant to your business.`

## Scope of Sync

### Salesforce > Inflection

1. Which will you sync to Inflection?
   1. Leads: `Y/N`
   2. Contacts: `Y/N`
   3. Accounts: `Y/N`
2. How many fields will you sync for each object:
   1. Leads: `# records; # fields`
   2. Contacts: `# records; # fields`
   3. Accounts: `# records; # fields`
3. Will you sync **all** leads/contacts from Salesforce? `Y/N`
   1. If not, note that a selective sync from Salesforce to Inflection requires a Boolean field in Salesforce as a sync filter (example: **Sync to Inflection** = **True**).
4. When leads/contacts are created in Salesforce, should an Inflection contact be created? (This is recommended.) `Y/N`
5. When leads/contacts are deleted in Salesforce, should the related Inflection contact be deleted as well? `Y/N`

### Inflection > Salesforce

1. Will Inflection **create** and **update** lead/contact records? (Will this be a bidirectional sync?) `Y/N`
2. Will you sync **all** Inflection contacts to Salesforce? `Y/N`
3. What are the minimum required fields to create a new lead/contact in Salesforce?
   1. `Email`
   2. `Last Name`
   3. `Company`
   4. Add more as applicable

### Field Mapping

1. Do you have standard or custom fields on lead, contact, or account records that are **not** on the auto-map list below? If yes, custom field mapping will be required (this is likely). `Y/N`
   1. Email
   2. Name
   3. First Name
   4. Last Name
   5. Company Name
   6. Title
   7. Unsubscribed
   8. Phone Number
   9. Person Created Time
   10. Account ID
   11. SFDC ID

### Next Steps

Share this with your Inflection team and your Salesforce administrator as part of the integration request.

Read and share with your Salesforce administrator our [Salesforce documentation](/connections/salesforce).


# Segment Questionnaire
Source: https://docs.inflection.io/getting-started/onboarding/segment-questionnaire

Onboarding questionnaire to prepare your Segment connection to Inflection.

Complete this document and share with your Inflection team and Segment administrator.

`This document has generic placeholder information. Replace it with information relevant to your business.`

## Segment as a Source

1. What events and properties does Inflection need to support your Inflection journeys? This should include any event or property that will be used in targeting, segmentation, dynamic content, or other personalization; and success criteria or exit criteria.
   1. User Properties (attributes on identify calls)
      * `Email Address` (required - do not remove)
      * `User ID` (required - do not remove)
      * Add as applicable
   2. Org Properties (attributes on group calls)
      * `Org ID` (required - do not remove)
      * `Workspace Name`
      * Add/edit more as applicable
   3. Product Activities (track calls)
      * `Signed Up`
      * `Created Item`
      * `Activated Item`
      * `Exported Item`
      * Edit/add more as applicable
2. What are the average number of calls made in a month? Try to include only sources you plan to connect to Inflection.
   1. Identify calls: `#`
   2. Group calls: `#`
   3. Track calls: `#`
3. How many users do you have?
   1. Daily active users: `#`
   2. Monthly active users: `#`

### Next Steps

Share this with your Inflection team and your Segment administrator as part of the integration request.

Read and share with your Segment administrator our [Segment documentation](/connections/segment).


# Inflection Password Policy
Source: https://docs.inflection.io/getting-started/password-policy

Non-SSO users will need to follow this policy for their Inflection password.

<img alt="Inflection set password screen showing the password complexity requirements" />

As a way to enhance your account’s security, non-SSO users will need to follow this policy for their Inflection password.

## Password Complexity

Passwords must meet all of the following requirements:

* Minimum length of 10 characters
* At least one uppercase letter
* At least one lowercase letter
* At least one number
* At least one special character


# Single Sign-on
Source: https://docs.inflection.io/getting-started/single-sign-on

Google and Okta users can set up SSO for Inflection.

## Google SSO

This guide provides step-by-step instructions for Google Workspace administrators to enable Google Single Sign-On (SSO) for access to Inflection’s web portal.

<AccordionGroup>
  <Accordion title="Part 1: Set up Google workspace for SAML">
    <AccordionGroup>
      <Accordion title="Prerequisites">
        * Google Workspace administrator account with super admin privileges
        * A verified domain in Google Workspace
        * User accounts set up in Google Workspace
      </Accordion>

      <Accordion title="Add SAML app">
        1. **Open Google Admin console** ([https://admin.google.com](https://admin.google.com)) → *Apps* → *Web and mobile apps* → **Add app** → **Add custom SAML app**

        2. **App details**
           * Name: **Inflection**
           * (Optional) Description and logo
           * Click **Continue**

        3. **Download IdP info** (from the *Google IdP Information* step)
           * Either **Download Metadata** or copy:
             * **SSO URL** (a URL like `https://accounts.google.com/o/saml2/idp?idpid=...`).
             * **Entity ID / Issuer** (Google shows a similar URL).
             * **Certificate** (X.509). You will paste this in Inflection later.
           * Click **Continue**

        4. **Service provider details**
           * **ACS URL:** `https://auth.inflection.io/api/v1/saml/sso2`
           * **Entity ID:** `https://auth.inflection.io`
           * **Start URL:** *(leave blank)*
           * **Signed response:** **Checked**
           * **Name ID format:** **Email**
           * **Name ID:** **Basic Information → Primary email**
           * Click **Continue**

        5. **Attribute mapping** (Add Mapping)

           | Google Directory attribute | App attribute |
           | - | - |
           | Primary email | `email` |
           | First name | `name` |

        6. **Save**

        7. **Turn on for users**
           * On the app’s main page, click **User access** and turn **ON for everyone** or for specific **users/Groups**.
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Part 2: Enable SSO Login in Inflection">
    In Inflection, navigate to **Settings** > **Single Sign-on**.

    In the **Single Sign-on** section, enable SAML. Then enter:

    * **Single sign-on URL:** This is the SSO URL from the google admin page, typically of the form `https://accounts.google.com/o/saml2/idp?idpid=xxxxxxxxx`
    * **Issuer:** This is the Entity ID entry from the google admin page, typically of the form accounts.google.com
    * **Certificate:** Paste the contents of the certificate downloaded from google. Note: Ensure that the contents start with `---BEGIN CERTIFICATE---` and end with `--END CERTIFICATE--` for it to be parsed properly
    * Click **Save**

      <img alt="Inflection Single Sign-on settings with SAML enabled, showing the single sign-on URL, issuer, and certificate fields" />
  </Accordion>

  <Accordion title="Part 3: Test the setup">
    #### Step 1: Set Access Controls

    1. Specify which user groups can access the application in Google admin console
    2. Define role-based access if applicable

    #### Step 2: Test the Configuration

    1. Test the SSO setup with a test user account before rolling it out to all users
    2. Verify that the user can use sign-up with Google on app.inflection.io, log in with their google credentials and see a fully populated inflection homepage on successful login

    #### Step 3: Deploy to Users

    1. Once testing is successful, deploy the SSO configuration to all intended users
    2. Monitor for any authentication issues during the initial rollout
  </Accordion>

  <Accordion title="Additional Resources">
    * [Google Workspace Admin Help: Set up SSO](https://support.google.com/a/answer/60224)
    * [Google Workspace Admin Help: Manage SSO certificates](https://support.google.com/a/answer/6087519)
    * [Google Workspace Admin Help: Troubleshoot SSO issues](https://support.google.com/a/answer/6348528)
  </Accordion>

  <Accordion title="Common issues & quick fixes">
    * **`app_not_configured_for_user`**
      * The user isn’t assigned to the SAML app. Turn the app **ON** for that user’s Organizational Unit or group.
    * **Audience / Entity ID mismatch**
      * Ensure **Entity ID** in Google is **exactly** `https://auth.inflection.io` (no trailing slash). Re‑save and try again.
    * **Recipient / ACS mismatch**
      * Ensure **ACS URL** is **exactly** `https://auth.inflection.io/api/v1/saml/sso2`.
    * **`Response is not signed`**
      * In the SAML app → *Service provider details*, ensure **Signed response** is **checked** (this guide assumes it is ON).
    * **Attribute issues**
      * Attribute mappings must include: Primary email → `email`, First name → `name`.
    * **Clock/time errors (rare scenario)**
      * Ensure devices and IdP time are in sync.

    ***

    ### What Inflection receives

    * **NameID**: the user’s primary email
    * **Attributes**:
      * `email`: user’s primary email
      * `name`: user’s first name
  </Accordion>
</AccordionGroup>

## Okta SSO

This guide provides step-by-step instructions for Google Workspace administrators to enable Okta Single Sign-On (SSO) for access to Inflection’s web portal.

<Info>
  This setup might fail without parameter values that are customized for your organization. Please use the Okta Administrator Dashboard to add an application and view the values that are specific for your organization.
</Info>

<Info>
  Enabling SAML will affect all users who use this application, which means that users will not be able to sign in through their regular sign-in page. They will be able to access the app through the Okta service.

  Inflection.io doesn't provide a backup sign-in URL where users can sign in using their regular username and password. You can contact Inflection.io Support ([team@inflection.io](mailto:team@inflection.io)) to turn off SAML, if necessary.
</Info>

<AccordionGroup>
  <Accordion title="Supported Features">
    The Okta/Inflection.io SAML integration currently supports the following features:

    * SP-initiated SSO
    * IdP-initiated SSO
    * JIT (Just In Time) Provisioning

    For more information on the listed features, visit the [Okta Glossary](https://help.okta.com/en/prod/Content/Topics/Reference/glossary.htm).

    The following SAML attributes are supported:

    | Name | Value |
    | - | - |
    | email | user.email |
    | name | user.displayName |
  </Accordion>

  <Accordion title="Configuration Steps">
    <AccordionGroup>
      <Accordion title="Okta Admins">
        1. From the Okta Admin dashboard, click **Admin** button

        2. Click **Applications** > **Applications**

        3. Click **Browse App Catalog**

        4. Search for and Select **Inflection** in Browse App Integration Catalog

        5. Click **Add Integration** and Click **Done**

        6. Under Assign tab, add the Okta users that must be granted access to Inflection and Save

        7. Click Sign On tab, then click **Edit**.

        8. **Encryption Certificate**: Save the following encryption certificate as **encryption.crt** then upload it to Okta.

           ```text theme={null}
           -----BEGIN CERTIFICATE-----
           MIIF/TCCA+WgAwIBAgIUCwZHNy+d3MJEls0OwP4iEYjIIrwwDQYJKoZIhvcNAQEL
           BQAwgY0xCzAJBgNVBAYTAlVTMRkwFwYDVQQIDBBXYXNoaW5ndG9uIFN0YXRlMRAw
           DgYDVQQHDAdTZWF0dGxlMRYwFAYDVQQKDA1JbmZsZWN0aW9uLmlvMRYwFAYDVQQD
           DA1JbmZsZWN0aW9uLmlvMSEwHwYJKoZIhvcNAQkBFhJ0ZWFtQGluZmxlY3Rpb24u
           aW8wHhcNMjYwOTA5MDcyNjQwWhcNMjkwOTA4MDcyNjQwWjCBjTELMAkGA1UEBhMC
           VVMxGTAXBgNVBAgMEFdhc2hpbmd0b24gU3RhdGUxEDAOBgNVBAcMB1NlYXR0bGUx
           FjAUBgNVBAoMDUluZmxlY3Rpb24uaW8xFjAUBgNVBAMMDUluZmxlY3Rpb24uaW8x
           ITAfBgkqhkiG9w0BCQEWEnRlYW1AaW5mbGVjdGlvbi5pbzCCAiIwDQYJKoZIhvcN
           AQEBBQADggIPADCCAgoCggIBAKifVjFZm+JYrRnSOg9uyKKx31v7ZY5nOR5J0H3q
           9JJ6XpIIgblaqV+SG4On4ywBetQYZvzlTdfb+WnsLy8zyv60RCdioBPH0ng20p6g
           9Yr8m/4zLbEWw8dZI9qQidTtqAwQNtimckakiasHAap1vGdN0Kzu0jA5BG4P+yCe
           qgFgE7zxk9n5p5AcJ+aiBCpau1Fb5XR+cVfoJG52KrwPsnFXtB9ne1kXAbQGNVCt
           05q1gHlyNRnM8WIo4Lr573JatL6XzyQWUbdgOow+ja5rQvUcvmHWyOxi6OPw8O/q
           r+zIM1bTvEvzNf9EzpaIuG5LkU11eXf/t7B0fOKiiVctyYShUlwYmFnmb7bqk3D1
           XbwVwnxPrV2nfn3zcJobSVNKRh354KxrDvoLD1GsKsH2WgZhsSDOmmIjGz6F196j
           XxjvkTy3jLRldpxkmzUdiDpcqfWE7lg8nzqpoIVoFqcphx/8HFpVs+3vxkcufNS8
           yyU4yMB4M553pnbE9h3ajg1hFX+U+VY7nWX2m1u0sVxnsM1+n/lgq4ZDzlTs67Sw
           avWoaPM8a53SEo2M9DwOSkVa8tmnp+ag0AnGp0fcRJ8zySsmcI+ev3S4bTT4qNrn
           5+YhBDpIPz0dYNNWm3r2Q88fT9a3NoYFhjgkMlkpPU5Oh5BBvX6Cwf4aNIoMvHNV
           Xk2ZAgMBAAGjUzBRMB0GA1UdDgQWBBQ/u2XCxrHkFwBwwSUodd/pspwTuTAfBgNV
           HSMEGDAWgBQ/u2XCxrHkFwBwwSUodd/pspwTuTAPBgNVHRMBAf8EBTADAQH/MA0G
           CSqGSIb3DQEBCwUAA4ICAQCSyWIKVyR81uv8WOWLdllzXWAtAIzWOlLLH0BchAW5
           e81VkR06/dTEwOXDhhzdUR+TUewx/uXed2s6IhSI0ruzZYfcMmS/QFcHPCdxoyg0
           Mir8b8YXud+IY5x18UZMcMEXkTlBGou8IhISBwmp2sE+GnacXGtb90LbKS97Y2Li
           wRlzliUuFB+N1UFwa49nQ75dQ86yM2c5xBP6qjbuwNjneKAFSHbMOHaS456dyXaJ
           C1Kk5SJcg4FCNNEQj8fT7VHklO2/uXUGvWluNq67zZNQUCdBNNkmwSUHWf9maSWl
           rV33Qps+N1hT3n8Ce6vFhgWk0metQEBWpi9guMdfbyDglNzyox1Dfijv4RR9dmao
           TvkGAlNC7Bzf+7b0A80tfGEpT6AQwSD0fKK8VvJfc2vRAUgds6RU+KjWGYM48Y4E
           iKY7fZWJ3Ewa2qay+k1Eckc5miZM/rgdT6V0EdKUIHI0K5UyjLsQkEx+LAzUXOBO
           qixiIXdmb2fLfDhnV8D9sng0S1ieDsM8CVO+9lyQwnDaep0bN0b3twgdw2qB55P3
           NK1gIwjuHhaoZGuixr9AhtfCtNy8nGSGzcsWZXf6uqdmbmFKGlvsFNkU+M+9iDoW
           j7SuOfD9Ra+6NrhLaoIYKpBQrzGQSzGtQcaIAJwrCoJvUIt3dvT0YD5EsYRVB96d
           Fw==
           -----END CERTIFICATE-----
           ```

        9. Scroll down to **Advanced Sign-on Settings**.

        10. Enter your **Organisation Slug** (Get it from inflection app → Settings page → Single Sign-on) into the corresponding field.

        11. **Application username format**: Select **Email**.

        12. Click **Save**.

        13. Done!
      </Accordion>

      <Accordion title="Inflection Admins">
        1. Login to inflection account
        2. Navigate to Settings
        3. Choose Single Sign-on

        The values for the following settings can be found on the Sign On tab of the Inflection Okta Application under "Metadata Details"

        * Single Sign-On URL

        * IDP Issuer

        * Certificate

          <img alt="Inflection Single Sign-on settings showing the single sign-on URL, IDP issuer, and certificate fields" />

        * **Single Sign-On URL**: Copy and paste the following:<br />*Sign On tab of the Inflection Okta Application under "Metadata Details" >> Sign on URL*

        * **IDP Issuer**: Copy and paste the following:<br />*Sign On tab of the Inflection Okta Application under "Metadata Details" >> Issuer*

        * **Certificate**: Copy and paste the following:<br />*Sign On tab of the Inflection Okta Application under "Metadata Details" >> Signing Certificate*

        * Click **Save Changes**.

        * Logout

        * And log back In. This time Okta SSO login will be prompted
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="SP-initiated SSO">
    1. Go to: [https://app.inflection.io/login/start](https://app.inflection.io/login/start)
    2. Enter your email, then click **Continue**
  </Accordion>
</AccordionGroup>


# Inflection Help Center
Source: https://docs.inflection.io/index

Everything you need to set up, connect, and grow with Inflection — the B2B marketing automation platform built on your product and sales data.

## Welcome

Find guides for every part of Inflection, from first sign-in to advanced journey orchestration and AI agents.

<CardGroup>
  <Card title="Getting Started" icon="rocket" href="/getting-started/account-provisioning">
    Provision your account, authenticate your domain, set up SSO, and understand pricing.
  </Card>

  <Card title="Settings" icon="gear" href="/settings/email-settings">
    Configure email limits, unsubscribe behavior, UTM tracking, users, and privacy requests.
  </Card>

  <Card title="Connections" icon="plug" href="/connections/common-connections-use-cases">
    Connect Salesforce, Segment, Amplitude, your data warehouse, forms, and webhooks.
  </Card>

  <Card title="Database & Audiences" icon="database" href="/database/importing-contacts">
    Import contacts, build audiences, manage segments, and keep data clean.
  </Card>

  <Card title="Journeys & Assets" icon="route" href="/journeys/journey-canvas">
    Build and manage customer journeys, emails, tokens, conversions, and reports.
  </Card>

  <Card title="MCP and Agents" icon="robot" href="/agents/inflection-agents">
    Work with Inflection's AI agents in-app, in Claude, ChatGPT, and Slack via MCP.
  </Card>
</CardGroup>

## Popular articles

* [Building Audiences](/database/building-audiences): options and best practices for structuring queries
* [Salesforce](/connections/salesforce): bidirectional, native Salesforce integration
* [Journey Flow Steps Reference](/journeys/journey-flow-steps): every step available on the journey canvas
* [Inflection Agents](/agents/inflection-agents): AI agents that work across in-app, Claude, ChatGPT, and Slack

## Need help?

Email [support@inflection.io](mailto:support@inflection.io) and we'll get back to you quickly.


# Conversions
Source: https://docs.inflection.io/journeys/conversions

Configure conversions to track how your journeys influenced business outcomes.

Conversions help you answer a simple question:

> "Did this journey actually drive the outcome I care about?"

With **Conversions**, you can:

* Define **conversion events** (marketing, product, or data changes)
* Set an **attribution window** (e.g. 7, 14, 30 days)
* Link those conversions to **journeys**
* See how many people from a journey **converted** within the set window

## What is a Conversion Event?

A **Conversion** is any important action or state change you want to optimize journeys for, such as:

* **Marketing actions**
  * Submitted demo form
  * Registered for a webinar
  * Downloaded an ebook
* **Product actions**
  * Signed up for a trial
  * Activated a feature
  * Completed onboarding checklist
* **Contact field value changes**
  * Lifecycle stage → *Customer*
  * User Adoption Stage changed from *Hobby* → *Pro*

<Note>
  Only **contact record field changes** are supported for conversion triggers. User record value changes and Account value changes are not currently supported.
</Note>

You define these once as **Conversion Events** and then reuse them across journeys.

***

## How Attribution Works

1. Define a **Conversion Event** (e.g. "Lifecycle Stage = Customer") along with an **Attribution Window** (e.g. 30 days).
2. **Attach** that conversion to one or more journeys.
3. If a person performs the conversion event **after entering the journey** or **within X days (your attribution window) of exiting the journey**, they are attributed as converted for that journey.

***

## Creating a Conversion Event

### 1. Go to Conversions

* In the left navigation, go to **Conversions**
* Click **"+ New Conversion"**

<img alt="Conversions page with the + New Conversion button" />

### 2. Name & Describe

* **Event Name**: Use a clear, reusable name, e.g.:
  * `Signed Up for free trial`
  * `Registered for a webinar`
  * `Converted to opportunity`
* **Event Description** (optional but recommended): Explain what this conversion represents and how it's used.
  * Example: "Primary success metric for top-of-funnel nurture journeys. Triggered when Lifecycle Stage = MQL."

<img alt="New conversion form with event name and description fields" />

### 3. Set the Attribution Window

Set **how long** you want to give a journey credit for driving the conversion.

* Common choices:
  * **7 days** – very fast, reactive outcomes (e.g., ebook downloads after a campaign)
  * **14–30 days** – typical for nurture programs and product activation
  * **60–90 days** – longer sales cycles or multi-step onboarding

**What the window means:**

<Tip>
  The attribution window spans from when a person **enters the journey** to **X days after they exit the journey**. If the person performs the conversion event anytime within this window, they are attributed as converted for that journey.
</Tip>

Click **Save** to create the Conversion.

<Warning>
  **Note:** Conversion events cannot be edited once created. To make changes, you'll need to delete the conversion and create a new one.
</Warning>

### 4. Define the Conversion Trigger

You can base your conversion on:

1. **Events** (marketing or product)
   * Example: `marketing event = "demo_form_submitted"`
   * Example: `product_event = "project_created"`
2. **Contact Field value changes**
   * Example: `is_engaged_customer changes to "true"`
   * Example: `status changes to "MQL"`

<img alt="Conversion trigger configuration with event and contact field options" />

<Info>
  When configuring a **Contact Field value changes** trigger, click the data dictionary icon next to the operator dropdown on the field filter to open **Insights from data dictionary**. The panel shows how the field is populated and what values it contains. Read more: [Data Dictionary](/database/data-dictionary)
</Info>

***

## Linking Conversions to a Journey

Once you've defined conversions, you can attach them to journeys you want to measure.

### 1. Open the Journey

* Go to **Journeys**.
* Open the journey you want to track
* In the left sidebar, find the **Conversions** section and click **"Click to set up conversions"**

<img alt="Journey sidebar showing the Conversions section setup link" />

### 2. Add Conversions to the Journey

In the **Manage Conversions** modal:

* Search or browse the list of conversion events you created earlier.
* Check the box next to each conversion event you want to track for this journey.
* Each conversion shows its attribution window (e.g. "1d window", "2d window").
* Click **"Save changes"** to apply.

> Example:
>
> For a "Welcome Nurture" journey, you might add:
>
> * Primary: `Signed Up for Free Trial (30-day window)`
> * Secondary: `Activated Feature X (30-day window)`

Once attached, Inflection will start attributing conversions to this journey as people flow through it.

<Note>
  Note that a "Conversion Event" happens when a contact does any one of the selected events
</Note>

<Info>
  **Note:** Conversions are tracked only from the point they are linked to a journey. Historical data before the conversion was linked will not be counted.
</Info>

<Info>
  **Note:** Conversions do not clone with journeys. If you clone a journey, you will need to manually link conversion events to the new journey.
</Info>

***

### 3. Reading Conversion Metrics on a Journey

After your journey runs, you'll see conversion data appear in the Email Report overview.

<Info>
  **Note:** Conversion reporting is calculated **once a day at approximately 2:00 AM PST.** If a conversion event happens today (prior to 2:00 AM PST), it will reflect in reporting tomorrow.
</Info>

Typical metrics you'll see:

* **Total Conversions**

  Number of contacts who converted while in the journey and within the window.

* **Conversion Rate**

  `% of people in the journey who converted`

  ```javascript theme={null}
  (Total Conversions / Total people who entered the journey) × 100
  ```

<img alt="Journey report showing total conversions and conversion rate" />

> **Example**
>
> * Journey: `Free Trial Onboarding`
> * Conversion: `Upgraded to Paid Plan (30-day window)`
> * 1,000 people entered the journey.
> * 150 people upgraded while in the journey and within 30 days.
>
> You would see:
>
> * **Total conversions:** 150
> * **Conversion rate:** 15%
>
> You can compare this against:
>
> * Previous versions of the journey
> * Other journeys targeting the same audience

***

## Common Questions

### What happens if a person is in multiple journeys that share the same conversion?

* **Multi-journey credit** (conversion is attributed to all journeys the person is in that meet the window criteria).

### What if a contact converts multiple times?

* A contact can perform a conversion event multiple times.
* The conversion event of a contact can be attributed to the same journey multiple times if they enter the journey multiple times

### Can I change the attribution window or the conversion event later?

You currently cannot edit the attribution window or the details of a conversion event. You can however link or unlink a conversion event against a journey at any point

### Do I need a separate conversion for every journey?

No. In fact, it's better to **reuse** the same conversion across multiple journeys so you can compare:

### Can I attach multiple conversions to one journey?

Yes. Common pattern:

* 1 **Primary Conversion** (main business outcome).
* 1–3 **Secondary Conversions** (supporting outcomes you care about).

Example:

* Primary: `Webinar attended`
* Secondary: `Recording viewed`, `Logged into App`

### How does attribution work differently for Contact Journeys vs User Journeys?

Attribution behavior depends on the **type of journey** and the **type of conversion event** you're tracking. **When attribution works seamlessly:**

* **Contact Journey + Contact-level conversion** (e.g., contact field change, marketing activity) Works as expected, since the conversion happens at the contact level, there's no ambiguity.
* **User Journey + User-level conversion** (e.g., product activity performed by a specific user) Works as expected, the journey tracks specific users, and conversions are attributed to those same users.

**When attribution can be problematic:**

* **Contact Journey + User-level conversion** (e.g., product activity) This combination can cause missed or misattributed conversions. Here's why:

A single contact can have **multiple users** linked to it. When a Contact Journey runs, it qualifies the contact, but if the conversion event is a user-level activity, the system attributes it to the **most recently linked user**. This means:

* If **User A** is in the journey and performs the conversion activity, but **User B** was linked to the contact more recently, the conversion may not be counted correctly.
* You could miss conversions or see them attributed to the wrong user.

<Tip>
  **Tip:** To avoid attribution issues, match your journey type with your conversion type. Use Contact Journeys with contact-level conversions, and User Journeys with user-level conversions.

  **Recommendation:**

  | Journey Type | Best Conversion Types |
  | - | - |
  | Contact Journey | Contact field changes, Marketing activities |
  | User Journey | Product activities |
</Tip>


# Emails
Source: https://docs.inflection.io/journeys/emails

Steps and considerations when building an email in Inflection.

Inflection's email editor is built with [BeeFree.io](https://beefree.io/). This article will walk through the steps and considerations when building an email in Inflection.

## Create a new email

1. Navigate to **Emails** on the left panel.

<img alt="Emails section in the left navigation panel" />

2. Click **New email.**

<img alt="New email button on the Emails page" />

3. Name the email, select the appropriate editor, and categorize the email (Marketing or Transactional).

<img alt="Dialog for naming the email, selecting an editor, and choosing a category" />

<Info>
  Note that email category cannot be updated once the email is created.
</Info>

<Note>
  Read more about transactional emails: [Transactional Emails](/journeys/transactional-emails)
</Note>

4. Choose to create an email from scratch (**Start from scratch**) or select an existing template.

## Asset Settings

### Email Settings

When an email is created, **Email settings** will slide out on the right.

<img alt="Email settings panel sliding out on the right" />

Here you can:

* Add/edit subject line, sender name
* Add/edit pre-header
* Update sender details like name, email, and reply to email
* Add/edit Cc and Bcc contacts
* See the email category (marketing or transactional)
* Select to ignore communications limits
* **Tracking settings** — Control which engagement data is collected for this email. Three switches are available: **Track opens**, **Track link clicks**, and **Identify visitors on your website**. All default to on. See [Email Settings](/settings/email-settings) for details.

<Info>
  Note that sender name, send from and reply to will be pre-populated with information from Email Settings.
</Info>

<Warning>
  Use Cc and Bcc fields responsibly to protect email privacy and comply with regulations. Misuse may lead to privacy violations and negative impacts on your email campaigns, email metrics, and sender reputation.
</Warning>

Click **Done** after entering all the information.

To view or update these settings, select **Email settings** in the top navigation of your email asset.

<img alt="Email settings option in the top navigation of the email asset" />

#### Tracking column

The Emails list shows a **Tracking** column that displays the tracking state of each email:

* **Full** — All tracking is on
* **Partial** — Some tracking is on
* **None** — All tracking is off

### UTM Parameters

Select **UTM parameters** in the top navigation of your email asset to view and/or update UTM parameters.

<img alt="UTM parameters option in the top navigation of the email asset" />

<Info>
  Note that UTM parameters will be pre-populated with default information configured in **Global UTM Parameters** within **Admin Settings**. Talk to your instance administrator to update global settings.
</Info>

<img alt="UTM parameters panel with global defaults and custom parameters" />

Here you can:

* Overwrite global default parameters
* Add/edit custom parameters

### Mark as template

To make the email asset available as a template (for others to use as a starting point in their email builds), select **Mark as template**. The template will retain all current content and email settings.

<img alt="Mark as template option in the email asset menu" />

Once marked, the tag `Template` will be shown next to the email name in the Emails list.

Templates are just regular emails that happen to be reusable. You can:

* Open the template from the Emails list.
* Modify its content or settings.
* These changes will update the template and affect any future emails created from it.
* Editing a template will not affect any emails already created from the template.

#### Template Tips & Best Practices

* Name templates clearly so they're easily discoverable (e.g., "Promo Template – Summer 2025").
* Use templates for:
  * Recurring campaign formats
  * Product updates
  * Onboarding flows

## Build with Visual Editor

<Tip>
  Check out [Mastering the Beefree builder](https://academy.beefree.io/course/finding-your-way-around-the-builder) for a tutorial. Note that some capabilities may have a slightly different UI in the Inflection builder.
</Tip>

## Preview, Export, and Test

### Preview

Preview email designs on **desktop** and **mobile** devices:

1. Click the ellipsis icon on the top right of the page.
2. Select **Preview** from the drop down.

<img alt="Preview option in the ellipsis drop down menu" />

3. Update the menu options to preview the email:
   1. In light and dark mode
   2. On a desktop, tablet and mobile
   3. In custom dimensions

<img alt="Preview mode options for theme, device, and custom dimensions" />

4. Click the back arrow (top left) or exit icon (top right) to exit preview mode.

<img alt="Back arrow and exit icon for leaving preview mode" />

### Export as HTML

To export an email as an HTML file:

1. Click the ellipsis icon on the top right side of the email editor page.
2. Select **Export html**.

An HTML file will download to your device.

<img alt="Export html option in the ellipsis menu" />

### Send test email

Send a test email to yourself, a colleague, or to your team:

1. Click on the ellipsis icon on the top right side.
2. Select **Send test email**.
3. In **Send to**, enter the email(s) to send the test email to.
4. In **Preview as a specific user**, enter the email address of an Inflection contact or user.
5. Click **Send preview**.

<img alt="Send test email option in the ellipsis menu" />

<img alt="Send test email dialog with Send to and Preview as a specific user fields" />

<Info>
  The preview user must exist as a contact or user in the Inflection database. A checkmark indicates that the contact exists in your contact database. If the email address you entered is not in the database, an error is displayed.
</Info>

## Create an Unsubscribe link

To configure an unsubscribe link in your emails:

1. Select the text you want to link.

<img alt="Selecting the text to turn into an unsubscribe link" />

2. Select the **Special links** option on the tool bar that appears.

<img alt="Special links option on the text toolbar" />

3. Select **unsubscribe** and select the token that slides out. The link is now configured.

<img alt="Unsubscribe token selection in the Special links menu" />

## Build with HTML Editor (Advanced)

If you selected the **HTML editor (Advanced)** option when creating the email, you get a raw HTML code editor instead of the visual builder. Paste your HTML, including any personalization tokens, into the code editor, then click **Save**.

### Preview Your HTML Email

After saving, you can preview how the HTML renders as an email:

1. Click **Preview email** in the top-right toolbar.
2. The **Email preview** drawer opens and renders your HTML, including externally-hosted images. It opens in **Desktop** view by default; toggle between **Desktop** and **mobile** to check how the email renders on each.

<img alt="Email preview drawer rendering an HTML email with the Preview as contact field" />

3. To see the email as a specific contact would, enter the contact's email in the **Preview as contact (email)** field and click **Preview** (or press Enter). Personalization tokens resolve to that contact's real values.
4. Click the clear (✕) control to return to the unpersonalized template view.

# Common Questions

## Avoiding lost or overwritten edits

The email editor can silently lose your in-progress edits if the same email is open in more than one place at once.

### What causes it

* Having the same email open in **multiple browser tabs or windows** at the same time.
* Having the same email open by **more than one person** at the same time.
* Opening several email templates in quick succession, before each one has fully finished loading.

Any of these can cause a refresh or auto-save to overwrite your latest changes with an older saved version, or — in some cases — sign you out of the editor entirely.

### How to avoid it

1. Open only one email template at a time, and let it fully finish loading before opening another.
2. Don't co-edit the same email or journey in a second tab, a second browser window, or with a teammate at the same time. Coordinate with your team so only one person edits a given email at a time.
3. Save frequently rather than leaving large batches of unsaved changes open.

> **Note:** If you open several templates back-to-back without waiting for each to load, you may be logged out of Inflection unexpectedly. Opening one template at a time, letting it load, and then opening the next avoids this.

### If a template's formatting corrupts and won't fix in place

Occasionally a template's formatting (for example, list numbering) can become corrupted in a way that doesn't fix itself no matter what you edit. If this happens and troubleshooting the original doesn't resolve it:

1. Clone the template to a fresh copy.
2. Continue your edits in the clone rather than the original.

This is a faster path to a working email than continuing to debug a corrupted original.

## Test-send delays and throttling

If test emails are arriving late (delays of up to \~10 minutes) or not arriving at all, this is usually a throttling issue rather than a platform outage.

### Why it happens

Sending a **high volume of test emails concentrated on one recipient** (for example, several team members each sending multiple test versions to the same inbox) can cause that recipient's mail server to throttle or defer delivery.

### How to avoid or work around it

* **Rotate recipients** when sending a batch of test emails rather than concentrating them on one address.
* If you need a test to go through immediately and suspect a provider-side throttle, try sending to a **non-Google address** to sidestep a Google-specific throttle.

## Hosting images

### Images

* **SVG images don't render in some email clients.** If an image or icon isn't displaying (particularly on desktop), check whether it's an SVG file. Convert it to PNG or JPEG and re-upload.
* **Broken images after switching from another platform.** If images (like a logo or social icons in your footer) stop rendering with no changes made on your end, check whether those image URLs still point to a previous email platform's asset host. If you've migrated from another ESP, re-upload those images to Inflection (or another live image host) rather than linking to the old platform's URLs, which may go stale or become unavailable.

## HTML, CSS, and formatting quirks

### Responsive / plain-text emails

If a plain-text email's layout (for example, a table) renders wider than expected:

* Table width may be defined at the template level.
* You may be able to influence it by adding CSS through an HTML code block.

Since Inflection's email editor is built on BeeFree, BeeFree's own help center is a useful secondary resource for raw CSS/HTML customization questions that go beyond Inflection-specific settings.

### Sender name and preheader text

* Special characters in your sender name (commas, periods, and other symbols — for example `Smith, Jane` or `Company, Inc.`) can cause some email clients to wrap the sender name in quotation marks in the inbox view. This behavior varies by email client.
* If you disable preheader text, most email clients will automatically pull the first visible text from your email body to fill that preview space instead.

## Testing links in preview mode

If a link in your email appears broken specifically when you click it **inside the editor's preview mode** (for example, showing an `ERR_BLOCKED_BY_RESPONSE` error), but you haven't tested it from an actual inbox yet:

* Some third-party sites (Facebook is a known example) intentionally block their pages from loading inside embedded preview contexts like Inflection's builder preview, as a security measure — even though the same link works normally when clicked from a real inbox.
* **Always confirm link behavior with a real test-send to your own inbox**, not just the in-editor preview, before concluding a link is broken.


# The New Journey Canvas
Source: https://docs.inflection.io/journeys/journey-canvas

The journey canvas is where you build and arrange your customer journeys.

The journey canvas is where you build and arrange your customer journeys. This article covers how to work *on* the canvas itself: adding, connecting, moving, duplicating, and deleting steps. For what each individual flow step does, see the [Journey Canvas flow-steps reference](/journeys/journey-flow-steps).

## The Canvas at a Glance

When you open a journey, you see the canvas with a few persistent controls:

* **Add step** panel (right) — the palette of flow steps, grouped by category (Email, Timing, Branching, Integrations, Lists, Data, Salesforce, Structure).
* **Canvas toolbar** (bottom center) — **Undo**, **Redo**, **Tidy Up**, **Add note**, and zoom controls.
* **Mini map** (bottom right) — a zoomed-out overview for navigating large journeys.
* **Step toolbar** — appears beside a step when you hover over it, with edit, duplicate, and delete actions.

<img alt="Journey canvas overview showing the Add step panel, canvas toolbar, and mini map" />

<Info>
  You can edit the canvas only while a journey is unpublished or paused. Published, running journeys open in read-only mode — you can pan, zoom, and copy steps, but not change them. To edit a live journey, pause it first (see **Pausing and Editing Active Journeys**).
</Info>

## Add a Flow Step

1. Open the **Add step** panel on the right.
2. **Drag** a step from the panel onto the canvas and drop it where you want it. Or **click** a step in the panel to drop it at the center of the view.
3. The new step appears on the canvas, ready to configure.

<img alt="Dragging a step from the Add step panel and dropping it on the canvas" />

## Connect Flow Steps

Connections define the order contacts move through your journey.

1. Hover over the step you want to connect *from*. A small round **handle** appears at the bottom of the step.
2. **Drag** from that handle to the **handle at the top** of the step you want to connect *to*.
3. Release to create the connection. The cursor shows a crosshair while you drag.

Branching steps (such as **Branch by filter**) have a separate handle for each path, so you can wire each branch to a different next step.

<Info>
  Connections can't cross a nested-journey boundary. To connect a step inside a container to one outside it, wire the container's exit handle to the outer step instead.
</Info>

<img alt="Dragging from a step's handle to another step to create a connection" />

## Select and Move Steps

* **Select** a step by clicking it. A colored ring shows it's selected.
* **Select multiple** steps by holding **Shift** and clicking each one, or by dragging a selection box (marquee) across the canvas.
* **Move** selected steps by dragging any one of them — the whole selection moves together — or by **nudging with the arrow keys**.
* **Deselect** everything by pressing **Esc**.

When one or more steps are selected, a small toolbar appears at the bottom center showing the count (for example, **3 nodes**) with quick **Copy** and **Delete** actions.

<img alt="Selecting multiple steps and moving them together on the canvas" />

## Duplicate a Step

1. Hover over the step you want to copy.
2. In the step toolbar that appears, click the **duplicate** icon.
3. A copy appears just below and to the right of the original, with the same configuration.

<img alt="Duplicating a step using the duplicate icon in the step toolbar" />

## Copy and Paste Steps

Copy and paste lets you reuse one or many steps — even across different journeys.

1. Select one or more steps.
2. Press **Cmd+C** (Mac) or **Ctrl+C** (Windows) to copy.
3. Press **Cmd+V** / **Ctrl+V** to paste. Pasted steps appear slightly offset from the originals.

When you copy multiple steps, the connections *between* them are copied too, so a pasted group keeps its internal structure. To move a group of steps into another journey, copy them in one journey and paste them into another.

<img alt="Copying steps and pasting them elsewhere on the canvas" />

## Undo and Redo

Every canvas change can be undone.

* Click **Undo** in the toolbar, or press **Cmd+Z** / **Ctrl+Z**.
* Click **Redo**, or press **Cmd+Shift+Z** / **Ctrl+Shift+Z**.

<Info>
  If the journey changed since your last action (for example, another editor made an edit), undo may not apply. You'll see a brief message and the canvas will refresh to the latest saved state.
</Info>

<img alt="Undoing and redoing changes with the canvas toolbar" />

## Tidy Up (Auto-Arrange)

Click **Tidy Up** or Align actions in the toolbar to automatically arrange your steps into a clean, readable layout. Tidy up re-flows the whole canvas — including the contents of any nested journeys — and recenters the view. Align is applied only on selected nodes

<img alt="Using Tidy Up and Align actions to auto-arrange steps" />

## Add a Sticky Note

Sticky notes let you leave context for yourself and your teammates on the canvas. They don't affect how the journey runs.

1. Click **Add note** in the toolbar. A note appears at the center of the view.
2. **Double-click** the note to type. Click away to save.
3. Drag the note's corners to resize it.

<img alt="Adding and editing a sticky note on the canvas" />

## Delete Steps and Connectors

You can delete a single step, a connector, or several steps at once:

* **A step:** hover over it and click the **delete** icon in its toolbar, or select it and press **Delete** / **Backspace**.
* **A connector:** select it and press **Delete** / **Backspace**. Connectors delete without a prompt — undo with **Cmd+Z** if needed.
* **Multiple steps:** select them and press **Delete** / **Backspace**.

Deleting a step opens a confirmation. If contacts are currently sitting at that step, the confirmation warns you how many — deleting may cause those contacts not to complete the journey.

<Info>
  Deleting a step can leave the steps that followed it disconnected ("orphaned"). Reconnect them after deleting. You can undo a delete with **Cmd+Z**.
</Info>

<img alt="Deleting a step with a confirmation dialog" />

## Keyboard Shortcuts

| Action | Mac | Windows |
| - | - | - |
| Delete selected steps or connectors | Delete or Backspace | Delete or Backspace |
| Undo | Cmd+Z | Ctrl+Z |
| Redo | Cmd+Shift+Z | Ctrl+Shift+Z |
| Copy | Cmd+C | Ctrl+C |
| Paste | Cmd+V | Ctrl+V |
| Move selected steps | Arrow keys | Arrow keys |
| Deselect all | Esc | Esc |

<Info>
  **Additional resources**

  * [Journey Canvas](/journeys/journey-flow-steps)
</Info>


# Journey Flow Steps Reference
Source: https://docs.inflection.io/journeys/journey-flow-steps

Build personalized, responsive customer experiences or operational workflows.

## Building On The Canvas

Flow steps are the building blocks of the canvas. Combine them to create sophisticated customer experiences using all the contact, behavioral, and organizational data in your Inflection account. Branch contacts into different paths, merge them back together, and repeat as needed to deliver the right message at the right time to each recipient.

<Info>
  To edit a journey, it must be unpublished or paused. Published journeys are read-only.
</Info>

### Adding A Step

Open the **Add step** panel on the right to browse the flow-step palette. To place a step, **drag** it from the palette onto the canvas, or **click** it to drop it at the center of the canvas.

<img alt="Dragging a step from the Add step panel onto the canvas" />

### Connecting Steps

Drag from a step's bottom handle to the next step's top handle to connect them. Branching steps expose one output handle per path, so you can wire each branch to its own next step.

To merge paths, point any branch to a shared forward step — multiple branches can lead into the same step to bring contacts back together. Inflection prevents circular logic, so contacts always move forward through the journey.

<Info>
  Connections cannot cross a nested-journey boundary. To continue a journey after a nested journey, wire the container's exit handle instead.
</Info>

<img alt="Connecting two steps by dragging between their handles" />

## Email

### Send Email

<img alt="Configuring a Send email step on the canvas" />

The **Send email** step sends an email to journey members. When you add this step to the canvas, select an email from your asset library.

Create and design emails separately in Inflection's email builder. This step references pre-built email assets, allowing you to reuse templates across multiple journeys.

After selecting an email, configure the following options:

* **Change the email asset**: Swap to a different email from your library
* **Edit the email configuration**: Override the email's subject line, reply-to address, from address, and sender name
* **Communications limits**: Choose to ignore or apply global sending limits
* **Link parameters**: Override default UTM or tracking parameters

<Info>
  Learn more about creating emails: Emails
</Info>

### Send Internal Email Alert

<img alt="Configuring a Send internal email alert step" />

The **Send internal email alert** step sends email notifications to your team members. Use this step to notify colleagues when contacts reach specific points in a journey.

When you add this step to the canvas, select an email template and enter the recipient email address. Enter a static email address that remains the same for all contacts who reach this step.

Common use cases include:

* Alerting sales owners when contacts reach a high-intent stage
* Notifying customer success teams when users trigger specific behaviors
* Informing marketing teams when contacts complete key milestones

The **Send internal email alert** step uses email templates from your asset library, allowing you to maintain consistent formatting for internal notifications.

<Info>
  Use this step on low-volume branches or journeys with limited membership. Every journey member who reaches this step triggers an email alert to the configured recipients, which can result in alert fatigue if used on high-volume journeys.
</Info>

## Timing

### Add Delay

<img alt="Add delay step configuration options" />

The **Add delay** step holds contacts at a point in the journey before moving them forward. Configure the step to:

* Delay by a fixed interval (a number of minutes, hours, or days)
* Delay until a specific time
  * Time of day
  * Specific date and time
  * Time in week (select one or multiple days in the week)
  * First day of month
  * Last day of month

<Info>
  Delay until a specific time offers an option to schedule according to the recipient's time zone. Inflection infers recipient time zone based on their country and state values (in default Inflection contact fields).
</Info>

## Branching

Branching steps split one path into multiple paths based on specific criteria. Use branching to create personalized experiences that adapt to contact attributes, behaviors, or data values. Combined with merging and nested journeys, branching lets you create multiple paths, bring them back together, and listen for product- or marketing-triggered actions that route contacts to different parts of the journey — all on a single canvas.

### Branch By Filter

<img alt="Branch by filter step configuration" />

The **Branch by filter** step splits contacts into two paths based on dynamic list criteria. Contacts who meet your filter conditions follow one path, while all others follow a separate path.

This step uses the same audience-building functionality as journey entry filters, enabling you to create precise branching logic based on:

* **Person properties**: Contact attributes like title, location, or custom fields
* **Product events**: User actions and behaviors in your product
* **Marketing activity**: Email engagement, form submissions, or campaign interactions
* **Web activity**: Page visits, content downloads, or site behavior
* **List memberships**: Static or dynamic list inclusion
* **Salesforce campaign membership**: Membership in specific Salesforce campaigns
* **Segmentation**: Pre-built audience segments
* **Account org level grouped properties**: Organization-level attributes and aggregated data

Inflection evaluates filters in real time as contacts reach the branch step, ensuring contacts always follow the path that matches their current state.

<Info>
  Select **Branch by filter** for two-way splits that require concise, detailed filter logic.
</Info>

<Info>
  After selecting a field, click the data dictionary icon next to the operator dropdown to open **Insights from data dictionary**. The panel shows how the field is populated and what values it contains. For text fields, click values from the list to add them to your filter. Read more: [Data Dictionary](/database/data-dictionary)
</Info>

### Branch By Token

<img alt="Branch by token step configuration" />

The **Branch by token** step splits contacts into multiple paths based on token values. Select any token from your Inflection account, and contacts will follow different branches depending on their token value.

When you add this step to the canvas, select a token from the token library. Inflection adjusts the available branch options based on the token's output type. For example, a token that outputs a numerical score could be branched into ≤50, between 50 and 75, and >75.

Unlike **Branch by filter**, **Branch by token** supports unlimited branches. Each unique token value can follow its own path, enabling highly personalized journeys based on contact attributes, behavioral data, or calculated values.

<Info>
  Select **Branch by token** for unlimited branching based on the output of a token.
</Info>

<Info>
  Learn more about creating tokens: Tokens
</Info>

### Branch By Value

<img alt="Branch by value step configuration" />

The **Branch by value** step splits contacts into multiple paths based on contact or account field values. Select any field from the contact or account object, and contacts will follow different branches depending on their field value.

This step evaluates the direct value stored in contact or account fields. For example, branching by the Industry field on an account might create separate paths for Technology, Healthcare, Financial Services, and Retail.

**Branch by value** supports unlimited branches. Each unique field value can follow its own path, making it ideal for creating personalized experiences based on firmographic or demographic data.

## Integrations

### Run Outbound Webhook

<img alt="Run outbound webhook step configuration" />

The **Run outbound webhook** step calls third-party services as part of the journey. Use this step to trigger actions in external systems when contacts reach specific points in their journey.

Configure the webhook by providing the endpoint URL, request method, headers, and payload. Inflection sends the webhook request when each contact reaches the step, enabling real-time integrations with your tech stack.

Common use cases include notifying sales teams in Slack when target accounts reach high-intent stages, updating records, or triggering custom workflows in external systems.

<Info>
  Read [Custom Forms](/connections/custom-forms) to learn more about sending and receiving calls from other systems in Inflection.
</Info>

## Lists

### Add To Static List And Remove From Static List

<img alt="Add to static list step configuration" />

Use the **Add to static list** step to add contacts to a static list, and the **Remove from static list** step to remove contacts from a static list. When you add either step to the canvas, select the static list to update.

## Data

### Update Value

<img alt="Update value step configuration" />

The **Update value** step writes data to a contact field. Choose a contact field to update, then set a static value or select a token to populate the field.

### Delete Contacts

<img alt="Delete contacts step on the journey canvas" />

The **Delete contacts** step is a terminal step that permanently deletes any contact who reaches it. This step is available in both scheduled journeys and trigger journeys.

Place the step from the **Add step** panel. Because it is a terminal step, no other step can connect after it - the node has no outgoing connector.

When you add this step to the canvas, its configuration drawer shows the following warning: "Contacts that reach this step will be permanently deleted from all campaigns and lists. This cannot be undone."

Configure the step, then click **Save**:

* **Allow recreate**: checked by default.

<Info>
  **Allow recreate** - if checked, allows the contact to be re-created later by future data (for example, a new form submission or sync), while unchecking prevents re-creation.
</Info>

<img alt="Delete contacts configuration drawer with the Allow recreate option" />

After the step runs, the node footer shows two counts: **Deleted** and **In progress**. Click the footer to open a report drawer listing deleted contacts, with **Email** and **Deleted at** columns, a search box, and an **Export** button.

<Warning>
  Deleting a contact removes them from the contacts database and from all lists and campaigns. This action cannot be undone.
</Warning>

<Warning>
  Avoid placing a **Send email** step immediately before **Delete contacts**. Because the contact and their related data are deleted, the email report will not show data for that contact.
</Warning>

## Salesforce

### Add To Salesforce Campaign

<img alt="Add to Salesforce Campaign step configuration" />

The **Add to Salesforce Campaign** step adds contacts to a Salesforce campaign. Select the Salesforce campaign to add contacts to and select the campaign member status.

You can also configure the step to add contacts to a Salesforce campaign dynamically. If the Salesforce campaign ID is saved to the contact, select **Get ID from a contact field**. This is a scale-friendly way to process forms and other events that you might want to store in a Salesforce campaign.

<img alt="Selecting Get ID from a contact field for dynamic campaign assignment" />

### Wait For Salesforce Sync

<img alt="Wait for Salesforce Sync step on the canvas" />

The **Wait for Salesforce Sync** step pauses a journey until the next Salesforce sync run completes. Use this step when downstream actions in your journey depend on data that has been written back to Salesforce.

When a contact reaches the **Wait for Salesforce Sync** step:

1. The journey registers a callback with the Salesforce sync service, requesting notification when the next sync run completes.
2. The contact is held at this step while the sync runs on its normal schedule.
3. Once the Salesforce sync run finishes and all pending data has been written, the sync service notifies the journey.
4. The journey marks the step as complete and moves the contact to the next step.

<Info>
  This step does **not** trigger an additional sync run. It waits for the next regularly scheduled sync to complete. This preserves your Salesforce API limits and respects existing sync intervals.
</Info>

Use the **Wait for Salesforce Sync** step when your journey performs an action that changes contact data, and a later step depends on that data being reflected in Salesforce.

**Example 1: Update value → Wait for Salesforce Sync → Run outbound webhook**

You update a contact field in Inflection (for example, setting a lifecycle stage), and a downstream webhook calls an external system that reads from Salesforce. Without the wait step, the webhook fires before the updated value has synced.

1. **Update value** — Set the contact's lifecycle stage
2. **Wait for Salesforce Sync** — Pause until data syncs to Salesforce
3. **Run outbound webhook** — Call an external system that relies on Salesforce data

**Example 2: Inclusion list → Wait for Salesforce Sync → Add to Salesforce Campaign**

A contact becomes eligible for the Salesforce inclusion list through a value change, meaning they will be created as a lead or contact in Salesforce on the next sync. You want to add them to a Salesforce campaign, but the contact doesn't exist in Salesforce yet.

1. **Update value** — Make the contact eligible for the inclusion list
2. **Wait for Salesforce Sync** — Pause until the contact is created in Salesforce
3. **Add to Salesforce Campaign** — Add the newly created Salesforce record to a campaign

## Structure

### Nested Journey

<img alt="Nested journey container on the canvas" />

The **Nested journey** step creates a container for multiple steps with unique exit criteria. Use nested journeys to listen for specific behaviors or milestones and route contacts to different parts of the journey when those conditions are met.

As contacts progress through steps inside a nested journey, Inflection evaluates them against the nested journey's exit criteria. When a contact meets the exit criteria, they skip the remaining steps in the nested journey and continue on the defined exit path. This enables responsive journeys that adapt to contact behavior in real time, such as moving activated users out of an onboarding sequence or routing event registrants away from promotional emails.

Connections cannot cross a nested-journey boundary. To continue the journey after a nested journey, wire the container's exit handle to the next step.


# Journey Settings
Source: https://docs.inflection.io/journeys/journey-settings

Configure journey settings and understand journey statuses.

Journey settings give you precise control over who enters a journey, when they qualify, how often they requalify, and how emails are delivered. Use these settings to match each journey to its goal, from a one-time send to an always-on recurring program. This article covers journey statuses, audiences, exit criteria, the settings control panel, and tags.

## Journey Statuses

Inflection journeys can be in one of the following statuses:

* **Draft**: when creating a new journey or cloning an existing journey, the new journey is in a draft status. Draft journeys do not qualify contacts or send emails.
* **Published as Inactive**: publish a journey as inactive to reference it in another journey, for example to use the qualify-for-journey audience criteria or exit criteria, or to reference the journey audience.
* **Published as Active**: publish a journey as active to qualify contacts who meet the audience criteria, according to the schedule and frequency set in the journey's settings.

<img alt="Journey status options: Draft, Published as Inactive, and Published as Active" />

<Info>
  Read about the considerations and steps when pausing or editing active journeys: [Pausing/Editing Active Journeys](/journeys/pausing-editing-active-journeys)
</Info>

## Journey Audiences

Inflection users have a few options to build an audience for targeting in a journey:

* Dynamic lists
* Segments
* Journey audiences
* Static lists

<Info>
  For more detail on audience filters and logic: [Building Audiences](/database/building-audiences)
</Info>

## Journey Exit Criteria

Exit criteria can remove a contact from a journey before the contact completes the journey flow.

To configure or edit exit criteria, select **Click to set up exit criteria** in the side panel of any journey.

<img alt="Setting up exit criteria from the journey side panel" />

Exit criteria can be any marketing event or product event. Each event evaluates independently, meaning when a contact meets any one criteria (performs any one event included as exit criteria), they are exited from the journey.

## Journey Settings

Use the side panel in any journey to control when and how frequently your audience qualifies for your journey. Select **Edit >** next to **Journey settings** to open the control panel.

<img alt="Opening the Journey settings control panel from the side panel" />

### Schedule

Inflection users have four options to schedule:

* **Start immediately to run once**: immediately publishes the journey as active, qualifies the audience, and moves them through the flow one time. After running once, the journey reverts to a published-as-inactive state.
* **Schedule to run once**: select a date and time in the future to publish the journey as active, qualify the audience, and move them through the flow one time. After running once, the journey reverts to a published-as-inactive state.
* **Schedule a recurring journey**: select a date and time in the future to publish the journey as active, and a frequency at which to run the journey (every X days, day of week, day of month, or day of year).
* **Schedule a high frequency journey**: select a date and time in the future to publish the journey as active, and a frequency at which to run the journey (every X minutes or hours).

### Journey Qualification

Choose how frequently a contact can qualify for the journey:

* **Qualify only once**: a contact qualifies for the journey when it first meets the journey audience criteria. After the contact qualifies the first time, it does not qualify again, even if it continues to meet the audience criteria.
* **Qualify once every**: a contact qualifies for the journey when it first meets the journey audience criteria. After the contact qualifies the first time, it is eligible for requalification according to the frequency set. The contact must meet the audience criteria each time in order to qualify.
* **Qualify always**: every time the contact meets the audience criteria, it qualifies for the journey. Note that a contact can be in a journey multiple times.

<img alt="Journey qualification frequency options" />

<Info>
  Qualify only once is appropriate for most journeys.
</Info>

### Email Delivery Control

Inflection users can choose to override, or ignore, globally set communications limits for an individual journey. This setting applies to all emails within the journey.

<Info>
  Learn more about global communications limits here: [Email Settings](/settings/email-settings)
</Info>

## Pausing/Editing Active Journeys

### Pausing a Journey

When a journey is paused:

* Contacts in the journey will freeze where they are in the journey canvas.
* No additional contacts will qualify for the journey.
* No emails will send from the journey.

<Info>
  Note that any email send flow step **already in process** at time of pausing will complete and emails will be sent.
</Info>

### Delay Flow Steps

When a journey is paused and a contact is in a delay flow step, the contact will delay for the amount of time configured when they entered the delay flow step.

* If a contact enters a delay step set to `1 hour`, and during that hour the journey is paused and the delay step is updated to `2 days`, the contact will wait 1 hour before moving to the next step. Contacts that enter the delay step after it's set to 2 days, will wait 2 days.

The delay step timer continues to count down while the journey is paused. Contacts will move to the next step at the time indicated by the delay step, and pause there until the journey is republished as active.

* If a contact enters a delay flow step set to `1 hour` at 9AM, and at 9:30AM the journey is paused -- the contact will still move to the next step at 10AM. They'll wait there and not process further until the journey is republished as active. (If the next step is an email flow step, they will not be sent the email. They'll wait on that step and get sent the email when the journey is republished as active.)

### Deleted Flow Steps

If a contact enters a flow step, the journey is paused, and that flow step is deleted: the contact will not move forward in the canvas. The contacts in the deleted flow step will be deleted from the journey along with the flow step.

If constructing a journey where an email is sent after a delay step, and you know you may need to shorten the delay step later — rather than inserting a delay step, try adding the contacts to a static list. This way, you can target the static list with an email send when the time is right.

## Journey Tags

Tag journeys to streamline search on the journeys page. Each journey can have multiple tags.

<img alt="Adding tags to a journey on the journeys page" />


# Nested Journeys
Source: https://docs.inflection.io/journeys/nested-journeys

How and when to use nested journeys.

On the journey canvas, nested journeys act like containers for a set of flow steps — like a journey within a journey. Users can configure unique exit criteria for each nested journey.

As contacts progress through the flow steps in a nested journey, they are evaluated for the nested journey's exit criteria. Once a contact meets the nested journey's exit criteria, the contact exits the nested journey, skips over the remaining flow steps in the nested journey, and continues on the defined path.

## Common Use Cases

### Behavior-based Onboarding

In onboarding journeys, nested journeys can be used to send relevant, behavior-based communications. for each onboarding milestone. The exit criteria for each nested journey are milestones along the onboarding and adoption path. When a contact completes a milestone action, they are moved to communications about the next milestone, in the next nested journey.

### Single-canvas Event Execution

In event journeys, nested journeys can be used to remove event registrations from a stream of promotion emails, and route them to a delay flow step where they wait for a reminder about the upcoming event.

### Multi-email Nudges

In a journey encouraging a specific behavior (like feature adoption, or reactivation), a nested journey can listen for contacts who complete the desired action, remove those contacts from the communications stream, and re-route those contacts to a more relevant communication, given their behavior.

<img alt="In this reactivation journey, emails 1-3 are wrapped in a nested journey. They encourage users to log back into the product. The nested journey exit criteria is a user logging in. When a contact completes this desired action, they exit the flow of emails 1-3, and jump to the final email in the series, where a CSM offers a calendar link to meet." />

## Using Nested Journeys

From the **Flow step** panel, select **Nested journey**.

<img alt="Flow step panel with the Nested journey option" />

Add flow steps to the nested journey container.

<img alt="Nested journey container on the canvas with flow steps added inside" />

Nested journey exit criteria can be configured once:

1. The nested journey has at least one flow step inside of it
2. A destination flow step has been created (Where will contacts who meet the exit criteria flow?)

<img alt="Exit criteria configuration for a nested journey named Milestone 1" />

<Tip>
  Hover over **Nested journey** in the top left of the nested journey to edit the name of the container. In the screenshot above, the name of this nested journey is **Milestone 1**.
</Tip>

## Exit Criteria Evaluation

Contacts are evaluated for exit criteria when they move from one flow step to the next. If a contact enters a 2-day delay step and immediately qualifies for the exit criteria, they will complete the delay step before the exit criteria takes effect. This means they will wait 2 days, and then get removed from the nested journey and follow the path configured by the user.


# Pausing/Editing Active Journeys
Source: https://docs.inflection.io/journeys/pausing-editing-active-journeys

Steps and considerations when editing active journeys.

## Pausing a Journey

When a journey is paused:

* Contacts in the journey will freeze where they are in the journey canvas.
* No additional contacts will qualify for the journey.
* No emails will send from the journey.

<Info>
  Note that any email send flow step **already in process** at time of pausing will complete and those emails will be sent.
</Info>

## Delay Flow Steps

When a journey is paused and a contact is in a delay flow step, the contact will delay for the amount of time configured when they entered the delay flow step.

<Info>
  Example: If a contact enters a delay step that is set to `1 hour`, and during that hour the journey is paused and the delay step is updated to `2 days`: the contact will wait 1 hour before moving to the next step. Contacts that enter the delay step **after** it's set to 2 days, will wait 2 days.
</Info>

The delay step timer continues to count down while the journey is paused. Contacts will move to the next step at the time indicated by the delay step, and pause there until the journey is republished as active.

<Info>
  Example: If a contact enters a delay flow step set to `1 hour` at 9AM, and at 9:30AM the journey is paused -- the contact will still move to the next step at 10AM. They'll wait there and not process further until the journey is republished as active. (If the next step is an email flow step, they will not be sent the email while the journey is paused. They'll wait on that step and get sent the email when the journey is republished as active.)
</Info>

## Deleted Flow Steps

If a contact enters a flow step, the journey is paused, and that flow step is deleted: the contact will not move forward in the canvas. The contacts in the deleted flow step will be deleted from the journey along with the flow step.

If constructing a journey where an email is sent after a delay step, and you know you may need to shorten the delay step later — rather than inserting a delay step, try adding the contacts to a static list. This way, you can target the static list with an email send when the time is right.


# Reports
Source: https://docs.inflection.io/journeys/reports

Report on email performance in Inflection or in your own analytics environment.

## Bring Your Own Analytics

Export marketing activity data—including email interactions, form submissions, and inbound webhook submissions—directly to your CDP or data warehouse. From there, use your analytics or business intelligence tool to analyze and report on the influence marketing activities have on down-funnel conversions like product activation, free to paid conversion, and/or closed-won opportunities.

Read more about configuration details in our docs:

[Export to Data Warehouse](/connections/export-to-data-warehouse)

[Segment](/connections/segment) (Segment as a destination)

## In-App Reporting

In the top right-hand corner of every journey canvas is a drop-down menu **Reports**. This contains two options.

<img alt="Reports drop-down menu in the journey canvas" />

### Journey Email Report

The Journey Email Report summarizes email performance for the entire journey for a given time period (defined in the top right corner).

<img alt="Journey Email Report showing delivery stats for the journey" />

<Tip>
  The timeframe (top right corner) will default to the **Last one month**. To view metrics for the complete life of the journey, update the timeframe to **All time**.
</Tip>

There are two tabs in the Journey Email Report.

1. **Overview**

   <Info>
     Note that the **Overview** tab describes metrics across all emails and contacts (or users) in the journey. (If 50 contacts qualify for a journey and there are 2 emails in the journey, the Overview tab will show up to 100 emails processed, opened, clicked, etc.)
   </Info>

   * **Delivery Stats** summarizes email metrics such as sent, delivered, bounced, unsubscribed, opened, clicked. etc.
     * These numbers reflect email sends, not unique contacts or users. If a single contact or user is sent 2 emails, they (and their relevant activity) will be counted for each email sent.
     * Opens are counted once per contact per email. If a contact opens the same email several times in a short window, it counts as one open.
     * **Untracked metrics**: If tracking was disabled for an email, the corresponding metric tile displays **Not tracked** instead of a count or rate. If **Track opens** is off, the open count and open rate show *Not tracked*. If **Track link clicks** is off, the click count and click rate show *Not tracked*.
   * **Top Links** displays the most frequently clicked links across all emails. Click to **View all links** for a complete list.
   * **Email Clients** shows what share of opens and clicks come from which email client.
   * **Past journey runs**: each row represents a cohort of users or contacts who qualified for the journey on that journey run.
     * Like the overall delivery stats, each row reflects all emails sent to the cohort and activity related to those emails; rows do not represent unique contacts or users.
     * In multi-email journeys, each row will update as the cohort is sent and interacts with additional emails from the journey.

   <img alt="Past journey runs table with cohort rows and their statuses" />

   In the above example: contacts added to the journey on August 18 were sent 9,433 emails. As there are multiple emails in this journey, this number is **not** an indication of the unique contacts added to the journey on this day. Instead, it represents the total number of emails sent to the cohort of contacts who entered the canvas on August 18. **FINISHED** indicates all contacts have exited the journey. **IN PROGRESS** (on the August 19 row) indicates all contacts have not yet exited the journey.

   <Info>
     Note that if the journey starts with a delay step that is 1+ days, the first rows may show 0 emails processed. This is because the most recent cohort who entered the canvas will not receive emails until after the delay step.
   </Info>

   <Info>
     To understand how many emails were sent in a given day, return to the top of the report (**Delivery stats**) and filter the time period to the date.
   </Info>

   <Info>
     When a journey contains a mix of tracked and untracked emails, blended rates (open rate, click rate) are calculated using only the emails that have tracking enabled for that dimension. Untracked emails are excluded from the rate calculation, not counted as zero.
   </Info>

   <img alt="Past journey runs table showing Not tracked in the Opened column for runs where open tracking was disabled" />

2. **Recipients**

   * **All**: lists all contacts evaluated for a send.
   * **Not sent**: lists contacts who were evaluated, but not sent to, and the not sent reason (typically due to unsubscribe, communications limits, or past bounces).
   * Tabs **Open**, **Click**, **Bounce**, **Unsub**, and **Spam** list the contacts relevant to these activities.

### Filter Out Bot Activity

Security scanners, link checkers, and other automated tools can open emails and click links. This inflates open and click counts. Inflection detects this activity and flags it as bot activity.

Every open and click is evaluated against several independent signals. No single signal decides the outcome; they are weighed together, and each event is either **flagged as a bot or left unflagged** - a single yes/no marker.

**Signals we use:**

* **Datacenter-origin IPs.** Genuine human engagement almost always originates from residential or mobile networks. Requests coming from datacenter IP ranges (where proxies, scanners, and bots run) are a strong automated-activity signal.
* **Repeated-link scanning.** A person typically clicks one, maybe two links in an email. An actor that follows many distinct links from the same message in a rapid burst is a security/link-protection scanner, not a reader.
* **Multi-recipient IP fan-out.** When a single IP fetches tracking content for a large number of different recipients, it is acting as a shared proxy or scanner rather than an individual.
* **Client identity.** The mail client / user agent distinguishes real interactive clients from scripted fetchers and known proxy services (e.g. Apple Mail Privacy Protection, Gmail image proxy).

To hide flagged activity, click **Exclude bots** next to **Bot filter** at the top of the Email Report. **Off** is the default and shows all recorded opens and clicks. The filter applies to opens and clicks together across the report.

<img alt="Email Report with the Bot filter set to Exclude bots" />

### Journey Member Report

<img alt="Journey Member Report listing contacts with entry date, exit date, and status" />

This report lists all contacts or users who entered the journey, with the following details:

* **Entry date**
* **Exit date**
* **Status**

Search for specific contacts or users to understand when the person entered, exited and their current status in the journey.

Export the report to analyze details in a spreadsheet.

In the case the journey is set to qualify contacts or users more than once, select **Show unique entries** to only display the most recent run of a user or contact.


# Tokens
Source: https://docs.inflection.io/journeys/tokens

Personalize journeys and emails with tokens that reference and calculate based on attributes and activities.

In Inflection, tokens are elements that reference an attribute or calculation related to a contact, user, org, or account. They are used to personalize journeys and emails.

## Token categories & examples

We think of tokens in 3 categories:

<AccordionGroup>
  <Accordion title="(1) Fields in Inflection">
    * On the contact: `first name`, `company name`, `lead score`, `email address`, `job title`, `phone number`, etc.
    * On the user: `role`, `last login date`, `user ID`, `permissions level`, etc.
    * On the org (or workspace): `plan`, `workspace created date`, `feature enabled`, `organization ID`, `subscription tier`, `billing status`, etc.
    * On the account: `AE`, `CSM`, `renewal date`, `contract value`, `health score`, `onboarding status`, etc.
  </Accordion>

  <Accordion title="(2) Simple calculations">
    * **Sums**: like summed intent and fit scores (`+`)
    * **Concatenations**: like full name concatenation; first name & last name (`concat()`)
    * **If statements**: if user role = "Admin", show admin-specific content; if login count > 10, return "Active User"; etc. (`if()`)
    * For a full list, visit our tokens glossary
  </Accordion>

  <Accordion title="(3) Advanced functions">
    * **User-level aggregations**:
      * Number of times a user has completed a specific event (`countIf`)
      * User's most recent product events (`getMostRecentProductEventUser`)
      * Top event properties for a specific user (`topEventPropertyValuesUser`)
      * For a full list, visit our tokens glossary
    * **Workspace-level aggregations**:
      * Number of times a specific event has occurred in a workspace (`countIfPersonsGroup`)
      * Top users by events in a workspace (`topEventPropertyValuesOrg`)
      * Whether any user in the workspace has performed specific actions (`countIfPersonsGroupPersonField`)
      * For a full list, visit our tokens glossary
  </Accordion>
</AccordionGroup>

Similar to Excel formulas, calculations and advanced functions can be nested. More on syntax and use of tokens, below.

## Where to use tokens

Tokens are used to personalize journeys and emails.

<Tip>
  Tip: To use token values as audience criteria, leverage a journey that sorts contacts into static lists, based on the token value. (1) Build a journey that branches users or contacts by token (note: this will count as an MMC journey); (2) Add users or contacts to static lists based on their token values; (3) Reference the static lists in the dynamic list.
</Tip>

### Tokens in emails

Once you've created your token, follow the following methods to use the token in an email.

<AccordionGroup>
  <Accordion title="As email copy">
    To include a token in email copy:

    1. In a text content block, select **Tokens** in the menu.

       <img alt="Tokens option in the text content block menu" />

    2. Search for and select the token to include.

       <img alt="Token search dropdown for selecting a token" />

    3. Once selected, the token will appear in the email as below. Note that the token will take on the formatting of the text block its in.

       <img alt="Token displayed inline in the email copy" />
  </Accordion>

  <Accordion title="In the subject line">
    To include a token in the subject line of the email, begin typing the field or token you wish to include.

    <img alt="Token suggestions appearing while typing in the subject line" />

    Once selected, the token will appear in the subject line as below.

    <img alt="Token displayed in the email subject line" />
  </Accordion>

  <Accordion title="As an image">
    To use a token to display a dynamic image in an email, drag an image block onto the email and enable Dynamic image. Then copy/paste the token into the **Dynamic Url** editor.

    <img alt="Dynamic Url editor with a token pasted in" />

    <Tip>
      Tip: To ensure the correct syntax, follow the steps to insert the token in the subject line. Copy the token and paste it into the **Dynamic Url** editor.
    </Tip>
  </Accordion>

  <Accordion title="As a link">
    To use a token to create a personalized link, copy/paste the token in the **Url** editor. Note that the syntax is slightly different (single quotes rather than double).

    <img alt="Url editor with a token using single-quote syntax" />

    <Tip>
      Tip: To ensure the correct syntax, follow the steps to insert the token in the subject line. Copy the token and paste it into the **Url** editor. Replace the double quotes with single quotes.
    </Tip>
  </Accordion>
</AccordionGroup>

### Tokens in journeys

To use a token to determine the path of a journey, use the **Branch by token** flow step.

## Testing

<AccordionGroup>
  <Accordion title="In the token editor">
    Test token values directly in the editor. Add a contact to the preview table and click **Add to preview**.

    <img alt="Token editor preview table with the Add to preview button" />

    Once added, view the token output value and variables used to calculate it. The variables visible in the preview editor will change depending on the variables used in the token calculation.

    <img alt="Token preview showing the output value and calculation variables" />

    <Tip>
      Note that the token must be saved to test it.
    </Tip>
  </Accordion>

  <Accordion title="In the email editor">
    To test a token in an email, follow the testing steps detailed in the Visual Email Editor doc. Note that when sending an email test where the email contains a token, a contact with a token value is required to send the test email.
  </Accordion>

  <Accordion title="In a journey canvas">
    To test a token in a journey, clone the journey and replace all actions in journey paths with an **add to static list** flow step. This will provide a preview for how pathing will behave in the actual journey.

    <img alt="Cloned journey using add to static list flow steps to preview token pathing" />
  </Accordion>
</AccordionGroup>

## Tokens glossary

<AccordionGroup>
  <Accordion title="Simple calculations">
    #### abSplit(n)

    **Formula:** `abSplit(2)`

    **Components:** `n` = number of splits for A/B testing

    **Use Case:** Randomly assign users to different test groups for A/B testing campaigns

    **Example:** `abSplit(3)` assigns users to groups 1, 2, or 3 for testing three email variants

    #### add (+)

    **Formula:** `value1 + value2`

    **Components:** `value1` and `value2` = numbers to add or strings to concatenate

    **Use Case:** Calculate totals or combine text fields

    **Example:** `column("deal_value") + column("upsell_value")` to get total opportunity value

    #### and

    **Formula:** `condition1 and condition2`

    **Components:** `condition1` and `condition2` = Boolean expressions

    **Use Case:** Combine multiple conditions for complex logic

    **Example:** `column("status") == "Active" and column("last_login") >= now()-30` for active recent users

    #### capitalize()

    **Formula:** `capitalize(string)`

    **Components:** `string` = text to capitalize

    **Use Case:** Format names with proper capitalization

    **Example:** `capitalize(column("first_name"))` converts "john" to "John"

    #### column()

    **Formula:** `column("field_name")`

    **Components:** `field_name` = name of the data field to reference

    **Use Case:** Reference contact, user, org, or account fields in calculations

    **Example:** `column("company_name")` retrieves the company name field

    #### concat()

    **Formula:** `concat(string1, string2, ...string_n)`

    **Components:** `string1, string2, etc.` = text values to combine

    **Use Case:** Combine multiple fields into a single text value

    **Example:** `concat(column("first_name"), " ", column("last_name"))` creates full name

    #### concatWithSpace()

    **Formula:** `concatWithSpace(string1, string2, ...string_n)`

    **Components:** `string1, string2, etc.` = text values to combine with spaces

    **Use Case:** Combine text fields with automatic spacing

    **Example:** `concatWithSpace(column("first_name"), column("last_name"))` creates "John Smith"

    #### contains()

    **Formula:** `contains(text, search_value)`

    **Components:** `text` = text to search in, `search_value` = text to find

    **Use Case:** Check if a field contains specific text

    **Example:** `contains(column("job_title"), "Manager")` returns true if title contains "Manager"

    #### dateTimeFormat()

    **Formula:** `dateTimeFormat(date_time, format_string)`

    **Components:** `date_time` = date field, `format_string` = desired format pattern

    **Use Case:** Format dates for display in emails

    **Example:** `dateTimeFormat(column("renewal_date"), "%m/%d/%y")` formats as "12/15/24"

    #### divide (/)

    **Formula:** `value1 / value2`

    **Components:** `value1` = dividend, `value2` = divisor

    **Use Case:** Calculate percentages or ratios

    **Example:** `column("closed_deals") / column("total_leads")` for conversion rate

    #### endsWith()

    **Formula:** `endsWith(text, suffix)`

    **Components:** `text` = text to check, `suffix` = ending text to match

    **Use Case:** Filter records based on text endings

    **Example:** `endsWith(column("email"), ".edu")` identifies educational email addresses

    #### equal (==)

    **Formula:** `value1 == value2`

    **Components:** `value1` and `value2` = values to compare

    **Use Case:** Compare field values for conditional logic

    **Example:** `column("plan_type") == "Enterprise"` checks for enterprise customers

    #### greater\_than (>)

    **Formula:** `value1 > value2`

    **Components:** `value1` and `value2` = values to compare

    **Use Case:** Compare numeric values or dates

    **Example:** `column("deal_size") > 10000` identifies large deals

    #### greater\_than\_or\_equal (>=)

    **Formula:** `value1 >= value2`

    **Components:** `value1` and `value2` = values to compare

    **Use Case:** Set minimum thresholds

    **Example:** `column("lead_score") >= 80` for high-quality leads

    #### hash()

    **Formula:** `hash(string, seed)`

    **Components:** `string` = text to hash, `seed` = number for randomization

    **Use Case:** Create consistent random assignments based on user data

    **Example:** `hash(column("email"), 0)` creates consistent hash for email personalization

    #### if()

    **Formula:** `if(condition, value_if_true, value_if_false)`

    **Components:** `condition` = boolean test, `value_if_true` = result when true, `value_if_false` = result when false

    **Use Case:** Conditional content or calculations

    **Example:** `if(column("plan") == "Pro", "Premium Features", "Standard Features")` for plan-specific messaging

    #### isEmpty()

    **Formula:** `isEmpty(value)`

    **Components:** `value` = field or expression to test

    **Use Case:** Check for empty or null fields

    **Example:** `isEmpty(column("phone_number"))` returns true if phone is blank

    #### isNotEmpty()

    **Formula:** `isNotEmpty(value)`

    **Components:** `value` = field or expression to test

    **Use Case:** Verify required fields have values

    **Example:** `isNotEmpty(column("company_name"))` confirms company name exists

    #### join()

    **Formula:** `join(separator, string1, ...string_n)`

    **Components:** `separator` = text between values, `string1, etc.` = values to join

    **Use Case:** Combine multiple values with custom separators

    **Example:** `join(", ", column("city"), column("state"))` creates "Austin, TX"

    #### length()

    **Formula:** `length(value)`

    **Components:** `value` = text or array to measure

    **Use Case:** Count characters in text or items in lists

    **Example:** `length(column("description"))` returns character count

    #### lesser\_than (\<)

    **Formula:** `value1 < value2`

    **Components:** `value1` and `value2` = values to compare

    **Use Case:** Find values below thresholds

    **Example:** `column("days_since_login") < 7` for recently active users

    #### lesser\_than\_or\_equal (\<=)

    **Formula:** `value1 <= value2`

    **Components:** `value1` and `value2` = values to compare

    **Use Case:** Set maximum limits

    **Example:** `column("team_size") <= 50` for small to medium teams

    #### mod (%)

    **Formula:** `value1 % value2`

    **Components:** `value1` = dividend, `value2` = divisor

    **Use Case:** Create patterns or cycles

    **Example:** `hash(column("email"), 0) % 2` for even/odd splitting

    #### multiply (\*)

    **Formula:** `value1 * value2`

    **Components:** `value1` and `value2` = numbers to multiply

    **Use Case:** Calculate totals or scale values

    **Example:** `column("seat_count") * column("price_per_seat")` for total cost

    #### not()

    **Formula:** `not(boolean_value)`

    **Components:** `boolean_value` = true/false expression to reverse

    **Use Case:** Invert boolean conditions

    **Example:** `not(column("unsubscribed"))` to find subscribed users

    #### not\_equal (!=)

    **Formula:** `value1 != value2`

    **Components:** `value1` and `value2` = values to compare

    **Use Case:** Exclude specific values

    **Example:** `column("status") != "Canceled"` for active accounts

    #### now()

    **Formula:** `now()`

    **Components:** None

    **Use Case:** Get current date/time for calculations

    **Example:** `now() - column("created_date")` for account age

    #### or

    **Formula:** `condition1 or condition2`

    **Components:** `condition1` and `condition2` = boolean expressions

    **Use Case:** Create inclusive conditions

    **Example:** `column("source") == "Website" or column("source") == "Referral"` for organic leads

    #### randint()

    **Formula:** `randint(start, end)`

    **Components:** `start` = minimum value, `end` = maximum value

    **Use Case:** Generate random numbers for testing or sampling

    **Example:** `randint(1, 100)` creates random number between 1 and 100

    #### replace()

    **Formula:** `replace(text, old_value, new_value)`

    **Components:** `text` = original text, `old_value` = text to replace, `new_value` = replacement text

    **Use Case:** Clean or standardize text data

    **Example:** `replace(column("phone"), "-", "")` removes dashes from phone numbers

    #### round()

    **Formula:** `round(number, digits)`

    **Components:** `number` = value to round, `digits` = decimal places

    **Use Case:** Format numeric values for display

    **Example:** `round(column("conversion_rate"), 2)` shows percentage with 2 decimal places

    #### startsWith()

    **Formula:** `startsWith(text, prefix)`

    **Components:** `text` = text to check, `prefix` = beginning text to match

    **Use Case:** Filter records based on text beginnings

    **Example:** `startsWith(column("phone"), "+1")` identifies US phone numbers

    #### stringToDateTime()

    **Formula:** `stringToDateTime(time_string)`

    **Components:** `time_string` = date in text format

    **Use Case:** Convert text dates to datetime for calculations

    **Example:** `stringToDateTime("2024-12-31")` converts text to date object

    #### subString()

    **Formula:** `subString(text, separator, position)`

    **Components:** `text` = original text, `separator` = split character, `position` = which part to return

    **Use Case:** Extract parts of text fields

    **Example:** `subString(column("full_name"), " ", 1)` extracts first name

    #### subtract (-)

    **Formula:** `value1 - value2`

    **Components:** `value1` = starting value, `value2` = value to subtract

    **Use Case:** Calculate differences or time spans

    **Example:** `column("renewal_date") - now()` for days until renewal

    #### title()

    **Formula:** `title(string)`

    **Components:** `string` = text to format

    **Use Case:** Format text with proper title case

    **Example:** `title(column("job_title"))` converts "product manager" to "Product Manager"

    #### toLower()

    **Formula:** `toLower(string)`

    **Components:** `string` = text to convert

    **Use Case:** Standardize text for comparisons

    **Example:** `toLower(column("industry"))` converts all industry names to lowercase

    #### toUpper()

    **Formula:** `toUpper(string)`

    **Components:** `string` = text to convert

    **Use Case:** Format text for emphasis or standardization

    **Example:** `toUpper(column("state"))` converts state abbreviations to uppercase
  </Accordion>

  <Accordion title="Advanced functions">
    <Accordion title="Available operators">
      #### String Operators

      * `=` or `is_one_of` - **equal to** (accepts multiple values)
      * `!=` or `is_not_one_of` - **not equal to** (accepts multiple values)
      * `contains` - **contains** (accepts multiple values)
      * `not_contains` - **does not contain** (accepts multiple values)
      * `begins_with` - **begins with**
      * `not_begin_with` - **does not begin with**
      * `ends_with` - **ends with**
      * `not_ends_with` - **does not end with**
      * `is_blank` - **blank** (no arguments)
      * `is_not_blank` - **not blank** (no arguments)

      #### Integer/Number Operators

      * `=` or `is_one_of` - **equal to** (accepts multiple values)
      * `!=` or `is_not_one_of` - **not equal to** (accepts multiple values)
      * `>` or `greater_than` - **greater than**
      * `>=` or `greater_or_equal` - **greater than or equal to**
      * `<` or `less_than` - **less than**
      * `<=` or `lesser_or_equal` - **less than or equal to**
      * `between` - **between (inclusive)** (requires 2 values)
      * `number_not_between_includes_null` - **not between** (requires 2 values)
      * `number_is_null` - **blank** (no arguments)
      * `number_is_not_null` - **not blank** (no arguments)
      * `is_zero_or_blank` - **zero or blank** (no arguments)

      #### Boolean Operators

      * `is_true` - **true** (no arguments)
      * `is_false` - **false** (no arguments)

      #### Date Operators

      * `is_on` - **on** (specific date)
      * `not_on` - **not on** (specific date)
      * `before` - **before**
      * `after` - **after**
      * `on_or_before` - **on or before**
      * `on_or_after` - **on or after**
      * `date_between` - **between (inclusive)** (requires 2 dates)
      * `date_not_between` - **not between** (requires 2 dates)
      * `relative_in_past` - **in past** (e.g., "in past 30 days")
      * `relative_timeframe` - **in relative timeframe between (inclusive)**
      * `date_is_null` - **blank** (no arguments)
      * `is_not_blank` - **not blank** (no arguments)
    </Accordion>

    <Info>
      Note: When referencing a product event in a token formula, write the event as it is recorded in Inflection, including spaces and capital letters as relevant.
    </Info>

    #### allOrgs()

    **Formula:** `allOrgs()`

    **Components:** None

    **Use Case:** Get list of all organizations in the tenant for cross-org analysis

    **Example:** `allOrgs()` returns array of all organization data

    #### countIf()

    **Formula:** `countIf("product_activity", column, operator, value, [connector, column2, operator2, value2])`

    **Components:** `"product_activity"` = table referenced, `column` = field to filter, `operator` = comparison type, `value` = filter value

    **Use Case:** Count user-specific product events

    **Example:** `countIf("product_activity", "event_name", =, "campaign_published")` counts campaigns published by user

    **Example filtered by date:** `countIf("product_activity", "event_name", =, "campaign_published", and, "event_date", >=, "2025-01-01")` counts campaigns published by user after January 1, 2025

    #### countIfPersonsGroup()

    **Formula:** `countIfPersonsGroup("product_activity", org_field, column, operator, value, [conditions])`

    **Components:** `"product_activity"` = table referenced, `org_field` = organization identifier, `column` = field to filter, `operator` = comparison, `value` = filter value

    **Use Case:** Count events across all users in an organization

    **Example:** `countIfPersonsGroup("product_activity", "User.org_id", "event_name", =, "user_login")` counts all logins in workspace

    #### countIfPersonsGroupPersonField()

    **Formula:** `countIfPersonsGroupPersonField("product_activity", column, operator, value, [conditions])`

    **Components:** `"product_activity"` = table referenced, `column` = field to filter, `operator` = comparison, `value` = filter value

    **Use Case:** Check if anyone in organization has performed an action

    **Example:** `countIfPersonsGroupPersonField("product_activity", "event_name", =, "integration_connected")` checks if org has any integrations

    #### getMostRecentProductEventAllUsers()

    **Formula:** `getMostRecentProductEventAllUsers(event_name, [properties], [filters], time_frame)`

    **Components:** `event_name` = product event type, `properties` = fields to return, `filters` = conditions, `time_frame` = days to look back

    **Use Case:** Find the latest occurrence of an event across all users

    **Example:** `getMostRecentProductEventAllUsers("campaign_published", ["campaign_name"], [], 30)` gets most recent campaign published anywhere

    #### getMostRecentProductEventOrg()

    **Formula:** `getMostRecentProductEventOrg(event_name, [properties], [filters], time_frame)`

    **Components:** `event_name` = product event type, `properties` = fields to return, `filters` = conditions, `time_frame` = days to look back

    **Use Case:** Find the latest event within user's organization

    **Example:** `getMostRecentProductEventOrg("template_created", ["template_name"], [], 7)` gets org's most recent template

    #### getMostRecentProductEventUser()

    **Formula:** `getMostRecentProductEventUser(event_name, [properties], [filters], time_frame)`

    **Components:** `event_name` = product event type, `properties` = fields to return, `filters` = conditions, `time_frame` = days to look back

    **Use Case:** Find user's most recent activity of a specific type

    **Example:** `getMostRecentProductEventUser("login", ["login_time"], [], 10)` gets user's last login details

    #### getProductEventByAllUsers()

    **Formula:** `getProductEventByAllUsers(event_name, [properties], [filters], sort_field, sort_order, time_frame, limit)`

    **Components:** `event_name` = event type, `properties` = fields to return, `filters` = conditions, `sort_field` = field to sort by, `sort_order` = asc/desc, `time_frame` = days, `limit` = max results

    **Use Case:** Retrieve events across all users with specific criteria

    **Example:** `getProductEventByAllUsers("campaign_created", ["campaign_name"], [], "event_date", desc, 30, 10)` gets recent campaigns from all users

    #### getProductEventByOrg()

    **Formula:** `getProductEventByOrg(event_name, [properties], [filters], sort_field, sort_order, time_frame, limit)`

    **Components:** `event_name` = event type, `properties` = fields to return, `filters` = conditions, `sort_field` = sort field, `sort_order` = asc/desc, `time_frame` = days, `limit` = max results

    **Use Case:** Get organization-specific events with sorting and filtering

    **Example:** `getProductEventByOrg("user_invited", ["invitee_email"], [], "event_date", desc, 7, 5)` gets recent invitations in org

    #### getProductEventByUser()

    **Formula:** `getProductEventByUser(event_name, [properties], [filters], sort_field, sort_order, time_frame, limit)`

    **Components:** `event_name` = event type, `properties` = fields to return, `filters` = conditions, `sort_field` = sort field, `sort_order` = asc/desc, `time_frame` = days, `limit` = max results

    **Use Case:** Retrieve user's events with specific parameters

    **Example:** `getProductEventByUser("template_used", ["template_name"], [], "event_date", desc, 30, 5)` gets user's recent template usage

    #### orgCount()

    **Formula:** `orgCount()`

    **Components:** None

    **Use Case:** Count how many organizations a user belongs to

    **Example:** `orgCount()` returns number of orgs for multi-org users

    #### topEventPropertyValuesAllUsers()

    **Formula:** `topEventPropertyValuesAllUsers(N, event_name, [properties], [filters], group_field, sort_order, time_frame)`

    **Components:** `N` = number of results, `event_name` = event type, `properties` = fields to return, `filters` = conditions, `group_field` = grouping field, `sort_order` = asc/desc, `time_frame` = days

    **Use Case:** Find top values across all users for analytics

    **Example:** `topEventPropertyValuesAllUsers(5, "page_viewed", ["page_name"], [], "page_name", desc, 30)` gets most viewed pages

    #### topEventPropertyValuesOrg()

    **Formula:** `topEventPropertyValuesOrg(N, event_name, [properties], [filters], group_field, sort_order, time_frame)`

    **Components:** `N` = number of results, `event_name` = event type, `properties` = fields to return, `filters` = conditions, `group_field` = grouping field, `sort_order` = asc/desc, `time_frame` = days

    **Use Case:** Identify top activity within an organization

    **Example:** `topEventPropertyValuesOrg(10, "feature_used", ["feature_name"], [], "feature_name", desc, 7)` gets org's most used features

    #### topEventPropertyValuesUser()

    **Formula:** `topEventPropertyValuesUser(N, event_name, [properties], [filters], group_field, sort_order, time_frame)`

    **Components:** `N` = number of results, `event_name` = event type, `properties` = fields to return, `filters` = conditions, `group_field` = grouping field, `sort_order` = asc/desc, `time_frame` = days

    **Use Case:** Analyze user's top activities or preferences

    **Example:** `topEventPropertyValuesUser(3, "email_clicked", ["link_url"], [], "link_url", desc, 14)` gets user's most clicked links

    #### countPageVisits()

    **Formula:** `countPageVisits([condition], window)`

    **Components:** `condition` (optional) = a web condition helper, or `allOf()`/`anyOf()`, to filter which page visits count; `window` = a number of rolling days, or a `between()` date range, to look back

    **Use Case:** Personalize based on how many times a contact visited a specific page or set of pages

    **Example:** `countPageVisits(urlContains("/pricing"), 30)` → number of pricing-page visits in the last 30 days; **Fallback:** `0`

    #### lastPageVisitAt()

    **Formula:** `lastPageVisitAt([condition])`

    **Components:** `condition` (optional) = a web condition helper to filter which page visit to match (no window - always returns the most recent match)

    **Use Case:** Trigger content based on when a contact last visited a page

    **Example:** `lastPageVisitAt(urlContains("/pricing"))` → date/time of the contact's most recent pricing-page visit; **Fallback:** `2000-01-01`

    #### lastPageVisit()

    **Formula:** `lastPageVisit(property, [condition])`

    **Components:** `property` = one of `url`, `page_title`, `referrer`, `utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`; `condition` (optional) = a web condition helper to filter which page visit to match

    **Use Case:** Reference the specific page a contact last viewed in email copy

    **Example:** `lastPageVisit("url", urlContains("/pricing"))` → URL of the contact's most recent pricing-page visit; **Fallback:** `there`

    #### countEmailEvents()

    **Formula:** `countEmailEvents(action, window)`

    **Components:** `action` = one of `delivered`, `blocked`, `open`, `click`, `bounced`, `spam_reported`, `unsubscribed`; `window` = a number of rolling days, or a `between()` date range, to look back (no condition helper for email events)

    **Use Case:** Personalize based on how engaged a contact has been with past emails

    **Example:** `countEmailEvents("click", 30)` → number of email clicks in the last 30 days; **Fallback:** `0`

    #### lastEmailEventAt()

    **Formula:** `lastEmailEventAt(action)`

    **Components:** `action` = one of `delivered`, `blocked`, `open`, `click`, `bounced`, `spam_reported`, `unsubscribed` (no window - always returns the most recent match)

    **Use Case:** Time a follow-up based on a contact's most recent email activity

    **Example:** `lastEmailEventAt("open")` → date/time of the contact's most recent email open; **Fallback:** `2000-01-01`

    #### lastClickedUrl()

    **Formula:** `lastClickedUrl()`

    **Components:** None

    **Use Case:** Reference the last link a contact clicked to follow up on their interest

    **Example:** `lastClickedUrl()` → the URL the contact most recently clicked in an email; **Fallback:** `there`

    #### countFormSubmissions()

    **Formula:** `countFormSubmissions([condition], window)`

    **Components:** `condition` (optional) = `formName` or `formNameContains`; `window` = a number of rolling days, or a `between()` date range, to look back

    **Use Case:** Personalize based on how many times a contact submitted a given form

    **Example:** `countFormSubmissions(formName("Demo Request"), 30)` → number of "Demo Request" form submissions in the last 30 days; **Fallback:** `0`

    #### lastFormSubmissionAt()

    **Formula:** `lastFormSubmissionAt([condition])`

    **Components:** `condition` (optional) = `formName` or `formNameContains` (no window - always returns the most recent match)

    **Use Case:** Time a follow-up based on when a contact last submitted a form

    **Example:** `lastFormSubmissionAt(formName("Demo Request"))` → date/time of the contact's most recent "Demo Request" form submission; **Fallback:** `2000-01-01`

    #### countWebhookSubmissions()

    **Formula:** `countWebhookSubmissions([condition], window)`

    **Components:** `condition` (optional) = `webhookName` or `webhookNameContains`; `window` = a number of rolling days, or a `between()` date range, to look back

    **Use Case:** Personalize based on how many times a contact triggered a given webhook

    **Example:** `countWebhookSubmissions(webhookName("Intent Feed"), 30)` → number of "Intent Feed" webhook submissions in the last 30 days; **Fallback:** `0`

    #### lastWebhookSubmissionAt()

    **Formula:** `lastWebhookSubmissionAt([condition])`

    **Components:** `condition` (optional) = `webhookName` or `webhookNameContains` (no window - always returns the most recent match)

    **Use Case:** Time a follow-up based on when a contact last triggered a webhook

    **Example:** `lastWebhookSubmissionAt(webhookName("Intent Feed"))` → date/time of the contact's most recent "Intent Feed" webhook submission; **Fallback:** `2000-01-01`

    #### countCampaignMemberships()

    **Formula:** `countCampaignMemberships([condition], window)`

    **Components:** `condition` (optional) = `campaignType`, `campaignNameContains`, `memberStatus`, or `hasResponded`; `window` = a number of rolling days, or a `between()` date range, to look back, measured against the member-added date

    **Use Case:** Personalize based on a contact's Salesforce campaign membership history

    **Example:** `countCampaignMemberships(campaignType("tradeshow"), 90)` → number of tradeshow campaign memberships added in the last 90 days; **Fallback:** `0`

    #### lastCampaignMembershipAt()

    **Formula:** `lastCampaignMembershipAt([condition])`

    **Components:** `condition` (optional) = `campaignType`, `campaignNameContains`, `memberStatus`, or `hasResponded` (no window - always returns the most recent match)

    **Use Case:** Time a follow-up based on when a contact was last added to a Salesforce campaign

    **Example:** `lastCampaignMembershipAt(campaignType("tradeshow"))` → date/time the contact was most recently added to a tradeshow campaign; **Fallback:** `2000-01-01`

    #### Condition helpers

    **Formula:** `helper(value)` - used inside the count or accessor function for its source

    **Components:** `value` = a single string, or a list of strings (a list matches if **any** value matches, e.g. `urlContains(["/pricing", "/plans"])`); helpers ending in `Contains` match on a partial/substring basis, all others require an exact, whole-value match

    **Use Case:** Narrow down which page visit, form, webhook, or campaign activity a function counts or matches

    **Example:**

    | Helper | Source | Match type | Example |
    | - | - | - | - |
    | `urlContains` | Page visits | Substring | `urlContains("/pricing")` |
    | `pageTitleContains` | Page visits | Substring | `pageTitleContains("Pricing")` |
    | `referrerContains` | Page visits | Substring | `referrerContains("google.com")` |
    | `utmSource` | Page visits | Exact | `utmSource("newsletter")` |
    | `utmMedium` | Page visits | Exact | `utmMedium("email")` |
    | `utmCampaign` | Page visits | Exact | `utmCampaign("q3_launch")` |
    | `utmTerm` | Page visits | Exact | `utmTerm("crm")` |
    | `utmContent` | Page visits | Exact | `utmContent("hero_cta")` |
    | `formName` | Form submissions | Exact | `formName("Demo Request")` |
    | `formNameContains` | Form submissions | Substring | `formNameContains("Demo")` |
    | `webhookName` | Webhook submissions | Exact | `webhookName("Intent Feed")` |
    | `webhookNameContains` | Webhook submissions | Substring | `webhookNameContains("Intent")` |
    | `campaignType` | Salesforce campaign memberships | Exact | `campaignType("tradeshow")` |
    | `campaignNameContains` | Salesforce campaign memberships | Substring | `campaignNameContains("Summit")` |
    | `memberStatus` | Salesforce campaign memberships | Exact | `memberStatus("Responded")` |
    | `hasResponded` | Salesforce campaign memberships | Exact (`true`/`false`) | `hasResponded(true)` |

    #### allOf()

    **Formula:** `allOf(conditionA, conditionB, ...)`

    **Components:** `conditionA, conditionB, etc.` = condition helpers to combine, all from the same source; nesting is capped at 3 levels

    **Use Case:** Require multiple criteria to match at once, like a page visit that also came from a specific UTM source

    **Example:** `countPageVisits(allOf(urlContains("/pricing"), utmSource("google")), 30)` → counts pricing-page visits that came from Google in the last 30 days

    #### anyOf()

    **Formula:** `anyOf(conditionA, conditionB, ...)`

    **Components:** `conditionA, conditionB, etc.` = condition helpers to combine; matches if **any** one of them matches

    **Use Case:** Match activity across a set of related pages, forms, webhooks, or campaigns

    **Example:** `countPageVisits(anyOf(urlContains("/pricing"), urlContains("/plans")), 30)` → counts visits to either the pricing or plans page in the last 30 days

    #### between()

    **Formula:** `between("YYYY-MM-DD", "YYYY-MM-DD")`

    **Components:** two dates = the start and end of the range; both days are fully included

    **Use Case:** Look back over a fixed calendar range instead of a rolling number of days

    **Example:** `countEmailEvents("click", between("2026-01-01", "2026-01-30"))` → counts email clicks between January 1 and January 30, 2026, inclusive
  </Accordion>
</AccordionGroup>

## Marketing Activity Tokens

This family of functions pulls a contact's marketing activity - page visits, email events, form submissions, webhook submissions, and Salesforce campaign memberships - into a token. Use them to personalize copy based on what a contact has actually done, like the pages they've viewed or the emails they've engaged with.

Like any other token, a marketing activity token is a separate asset: build it first in the token builder using these functions, then reference the saved token in your email copy or subject line (see [Tokens in emails](#tokens-in-emails)).

For example, create a token named `last_pricing_page` with the formula `lastPageVisit("page_title", urlContains("/pricing"))`, then reference it in your email copy to greet a contact by the topic they've shown the most interest in:

> Hi `{{first_name}}`, since you've been checking out `{{last_pricing_page}}`, here's a closer look at our plans.

Or create a token named `email_clicks_30d` with the formula `countEmailEvents("click", 30)` and reference recent engagement to decide what to send next:

> It looks like you clicked through our last email - `{{email_clicks_30d}}` times this month. Here's what else you might like.

<Info>
  Misspell a form, webhook, or campaign name in a condition helper, and it simply matches nothing - the token returns `0` (or the relevant fallback) with no error. If a token unexpectedly shows `0`, double-check the spelling of the name you passed in.
</Info>

<Info>
  `urlContains` matches against the domain and path only - it doesn't match against the query string. To match on UTM values, use the `utm...` helpers instead.
</Info>

<Info>
  The `last...At` accessors (`lastPageVisitAt`, `lastEmailEventAt`, `lastFormSubmissionAt`, `lastWebhookSubmissionAt`, `lastCampaignMembershipAt`) ignore the window entirely - they always return the most recent match, no matter how old it is.
</Info>

See the **Tokens glossary** above for the full list of marketing activity functions, condition helpers, and combinators, including their formulas, arguments, and fallback values.

# Answers to Common Questions

## Referencing fields and saved tokens

To reference a raw contact/product field directly inside a formula:

```text theme={null}
{{column('field_name')}}
```

Typing the field name while creating a token will auto-suggest it — click the suggestion to pull it in.

To reference an existing saved token from within another token or asset:

```text theme={null}
{{token('token_name')}}
```

Note: If you go the saved-token route, consider giving it a generic fallback value (see below) rather than leaving null cases unhandled.

## Building conditional logic

### Combining two conditions with AND

The token language's `if()` doesn't have a native AND operator. To combine two conditions, nest a second `if()` inside the true-branch of the first:

```text theme={null}
if(column("Country")=="United States", if(column("email")=="vip@example.com", "true", "false"), "false")
```

Only when the outer condition is true does the inner condition get evaluated; if the inner condition is also true, the formula returns the real value — otherwise it falls through to `"false"`.

Note: Every branch needs an explicit false/else output. Don't assume the token falls through to a sensible default if you leave a branch open.

### Boolean fields with a null state

If your boolean field actually has three possible states — true, false, and null/not-yet-populated — comparing it directly to a literal (like `1`) in a single check can throw an "incompatible argument type" error. Instead, write two separate checks: first test whether the field is empty, then test whether it's true. Between the two checks, you've covered all three real-world states.

Note: If a boolean or date comparison still errors after applying this two-check pattern, treat it as a possible token-engine issue rather than a formula mistake, and contact Inflection support.

### String functions abort silently to the fallback value on a null column

If a formula uses a string function (`toLower()`, `startsWith()`, `contains()`, `endsWith()`) on a column that can be null, the function doesn't evaluate to false and fall through to your else branch — it **aborts the whole formula** and jumps straight to the token's configured Fallback value, with no visible error.

**Fix:** guard every string-function call with `isEmpty()` on that column first, and order your branches so the "is this actually blank" check happens before any branch that calls a string function.

Note: Test a reordered formula in the token's draft/staging version first, confirm the output, then promote it to the live token — the live token keeps running the old formula until you explicitly promote the change. Also double-check any fallback values on related tokens that are literal `""` strings or the word `"default"` — these can silently pass as if they were real data and mask this same bug.

### Fallback values

A fallback value is a required field when you create a token — set it at token-creation time rather than trying to handle every null case only inside the formula logic.

Note: Watch for fallback values that are themselves silently wrong — a literal `""` or the word `"default"` can look like real data at a glance.

## Counting and rolling up activity

### `countIf()` syntax

`countIf()` takes an object name, then property/operator/value triples chained with `and`:

```text theme={null}
countIf("product_activity", "event_name", =, "Trial Started", and, "event_properties.category", =, "27")
```

Event-level custom properties need the `event_properties.` prefix — a bare property name will error.

Note: `countIf()` tokens (like all tokens) cannot be used directly as dynamic-list/audience criteria — see Known constraints below.

### Tokens can't count distinct users, only activity occurrences

A token can roll up product-activity occurrences, but it cannot produce a distinct-user count directly — for example, "how many active users in this org" isn't something a token formula can compute. Instead, bring that count over as its own field: on the account (via Salesforce) or on the user record (via your warehouse). If you can model it as an org-level attribute, that's generally the better placement than the account — but confirm first whether org attributes are actually flowing in from your connections.

## Date and time tokens

### `now()` always returns UTC

The `now()` function always returns UTC time — it never converts to your account's local timezone. This is standing behavior, not a bug. To make the output explicit or approximate your local time, wrap it with `dateTimeFormat()`:

```text theme={null}
dateTimeFormat(now(), "%b %d, %Y %I:%M %p UTC")
```

To approximate a specific local timezone, subtract a day-fraction offset (this converts the token's output from datetime to string):

```text theme={null}
dateTimeFormat(now() - 0.2917, "%b %d, %Y %I:%M %p")
```

Note: An offset like this is a fixed approximation — it doesn't account for daylight saving shifts, so revisit the offset value around DST changes if you rely on it.

### Tokens can only populate String-typed destination fields

A token can't stamp a native date/time-typed field directly. If you need a date/time value on a String-typed contact/account field, populate that String field with a `dateTimeFormat()`-formatted token instead. This has been confirmed safe for downstream warehouse/dbt use, since raw data typically gets cleaned before it reaches production tables.

## Using a token in a journey flow step

In an **Update Value** flow step, use the **Update by** selector to choose **Token**, then pick which token to use for the update.

### Worked pattern: turning recurring activity into a durable field

If you want to turn recurring product activity (like page views) into a contact/account field that another system can act on — not just display it in an email — this pattern works:

1. Build one token per time window or dimension you need (e.g., activity in the last 24 hours, last 7 days, or a rollup like `column("account_users")` for account-level counts).
2. Build a dynamic list of who should get the field stamped.
3. Create a journey scoped to that audience with an **Update Value by token** step to write each token onto the relevant contact/account field.
4. Because tokens are point-in-time snapshots — not live-updating — schedule the journey to re-run periodically (daily, for a 24-hour-window token) so the field stays current.
5. Spot-check a few contacts in each token's Preview Table before treating the values as reliable.

Note: The point-in-time-snapshot caveat is the load-bearing part of this recipe. Without the scheduled re-run, the stamped field goes stale the moment underlying activity changes.

## Testing and previewing tokens

### Preview mode won't resolve tokens — use a test send

In order for a token to populate, it needs a specific person to personalize for. A test send lets you select that person; plain Preview mode does not, so tokens won't resolve there. Always test with a contact who actually has the relevant field populated — testing against a contact with a null field will make a working token look broken.

### Multi-org/multi-user contacts: preview "scrolling"

If you're previewing an org-scoped token (e.g., `org.id`) for a contact tied to multiple orgs or users, the previewed value may cycle or "scroll" between the different possible values mid-session. This is expected behavior, not a bug. To lock the preview to one specific value, check **Receive as an org-user** and select the specific user-org combination you want to preview.


# Transactional Emails
Source: https://docs.inflection.io/journeys/transactional-emails

Steps and considerations when sending a transactional email.

## What Are Transactional Emails?

Transactional emails are non-promotional, service-related communications sent to deliver important information that a recipient needs to know — regardless of their marketing email preferences.

They are designed for essential updates such as legal notices, service disruptions, account activity alerts, and other operational messages.

Unlike marketing emails, transactional emails are always sent to intended recipients, even if they've unsubscribed from promotional content, while still respecting rules for invalid or bounced addresses.

Inflection now supports Transactional Emails via:

* A mandatory email category selection at creation time.
* Asset-level and journey-level visibility into whether an email is transactional.
* Logic that bypasses unsubscribes and communication limits.

## When to Use Transactional Emails

Choose **Transactional** when the email's **primary purpose** is to communicate essential, time-sensitive, and/or legally required information. Common examples include:

* Terms of Service or Privacy Policy changes
* System outage or incident notifications
* Billing failures, payment confirmations, or refund notices
* Event registrations, confirmations, or schedule changes

If the email's goal is to promote a product, encourage engagement, or drive sales, it should be classified as Marketing instead.

## Create a Transactional Email

When you create a new email (using either the Visual or Advanced Editor), you will be prompted to select an **Email Category**:

* **Marketing**
* **Transactional**

Select "**Transactional**" from the Email Category dropdown

<img alt="Email Category dropdown with Transactional selected when creating a new email" />

## Edit the Email Category

Once the email is created, you can not change its category.

* This applies to **both** Visual and Advanced Email Editors.
* You can clone an email asset to change its category.

### Visual Editor Example

<img alt="Visual Editor showing the email category is locked after creation" />

### Advanced Editor Example

<img alt="Advanced Editor showing the email category is locked after creation" />

## Email Asset List Enhancements

The Email List view now includes:

* A **new column** showing the category (Marketing or Transactional).
* A **category filter** to search or segment by type.

<img alt="Email List view with a category column showing Marketing or Transactional" />

Filter view:

<img alt="Email List category filter for Marketing and Transactional emails" />

In the journey, **Email Flow step panel** shows the type of the linked email as shown below:

<img alt="Email Flow step panel in a journey displaying the linked email's category" />

<Info>
  Transactional emails are always sent, regardless of unsubscribe status or communication limits. However, they still count toward the daily communication limit for subsequent marketing sends. (e.g., If communication limit for a day is set to 1 and a user is sent a transactional email, additional marketing emails will not be sent in accordance with communication limits.)
</Info>

<Info>
  Transactional Emails are subject to Monthly Marketed Contact (MMC) eligibility criteria just like any other email asset (or journey). Additionally, all metrics for transactional emails are reported the same as non-transactional emails.
</Info>


# Trigger Journeys
Source: https://docs.inflection.io/journeys/trigger-journeys

Enroll contacts automatically the moment a real-time event occurs.

Contact Journeys in Inflection come in two types: **Scheduled** and **Trigger**. Trigger Journeys enroll contacts automatically the moment a real-time event occurs, enabling instant follow-up and event-driven automation at scale.

Unlike Scheduled Journeys, which run against a pre-defined audience at a set time, Trigger Journeys respond to individual contact actions as they happen. When a qualifying event occurs - such as a form submission or an inbound webhook call - the contact is enrolled immediately, provided they match any audience criteria you've defined, and can receive a follow-up email within seconds.

| | Trigger | Scheduled |
| - | - | - |
| When contacts enter | Immediately, when an event occurs | On a schedule, against an audience |
| Entry criteria | A real-time event (e.g., form submission) | An audience list or segment |
| Best for | Instant follow-up, event-driven automation | Newsletters, scheduled campaigns |

## Create a Trigger Journey

When creating a new journey, select **Contact Journey**, then choose **Trigger** as the journey type. Use the Triggers section to define the real-time event that starts the journey.

<img alt="Creating a new Contact Journey with the Trigger journey type selected" />

## Triggers

The Triggers section defines the real-time event that enrolls contacts into the journey. Inflection supports two trigger types: Form Submission and Inbound Webhook.

<img alt="Triggers section showing the Form Submission and Inbound Webhook trigger types" />

### Form Submission

The Form Submission trigger enrolls a contact when they submit an Inflection form. Select one or more specific forms.

#### Form Field Filters

Filter the trigger so it fires only when a submitted form contains a specific field value. After selecting a form, click **Add Filter**, choose a form field, and enter the value to match (e.g., UTM Source = google).

<Info>
  Only contacts who submit the form with the matching field value are enrolled. Contacts who submit with a different value are not enrolled.
</Info>

### Inbound Webhook

The Inbound Webhook trigger enrolls a contact when a payload is received from a configured inbound webhook. Select an inbound webhook to associate with the journey. Any contact whose data arrives via that webhook is enrolled in real time.

Common use cases include enrolling contacts from third-party form providers (e.g., Webflow, Typeform) or any external system capable of sending a POST request to Inflection.

### Qualification Criteria

Qualification criteria control what happens when a contact qualifies for the journey more than once.

* **Qualify Once** — Enroll a contact on their first qualifying submission only. Subsequent submissions are ignored.
* **Qualify Always** — Enroll a contact every time they make a qualifying submission, as long as they are not currently active in the journey.

<Info>
  A contact cannot re-enter a journey while actively progressing through its steps, regardless of the qualification setting.
</Info>

## Audience

The Audience section narrows enrollment to the contacts you care about. After a trigger event fires, Inflection checks the contact against your audience criteria — only contacts who match are enrolled in the journey.

To define an audience, click **Edit** in the Audience section and add one or more filters. The Audience section uses the same filter blocks as dynamic lists and journey audiences, so you can qualify contacts by **person property**. For example, add a **person property** filter such as **Company** set to a specific value, or **Email** set to **not blank**, to enroll only matching contacts.

Combine multiple filters with **AND** / **OR** to express precise enrollment logic. With **AND**, a contact must match every filter to enroll. With **OR**, matching any one filter is enough.

The Audience section applies to both trigger types — Submitted a form and inbound webhook.

<Info>
  A contact is enrolled only when both conditions are true: the trigger event occurs **and** the contact matches the audience criteria. Leave the Audience section empty to enroll every contact who triggers the event.
</Info>

<Info>
  Audience filters evaluate the contact's stored properties, such as **Name**, **Email**, or **Company**. This is different from **Form Field Filters**, which match values in the submitted form payload. Use **Form Field Filters** to react to what was submitted; use the Audience section to qualify who the contact is.
</Info>

<img alt="Audience section with person property filters combined using AND/OR logic" />

<Info>
  Learn more about the available filter blocks and audience best practices: [Building Audiences](/database/building-audiences)
</Info>

## Supported Flow Steps

The following flow steps are available on the Trigger Journey canvas.

<img alt="Add step menu on the Trigger Journey canvas showing the available flow steps, including the Branching group" />

| Flow Step | Available |
| - | - |
| Send Email | ✅ |
| Add Delay | ✅ |
| Branch by Filter | ✅ |
| Branch by Value | ✅ |
| Update Value | ✅ |
| Add to Salesforce Campaign | ✅ |
| Send Internal Email Alert | ✅ |
| Wait for Salesforce Sync | ✅ |
| Add to Static List | ✅ |
| Remove from Static List | ✅ |
| Run Outbound Webhook | ✅ |
| Delete Contacts | ✅ |

<Info>
  Learn more about configuring individual flow steps and how to combine them: [Journey Flow Steps Reference](/journeys/journey-flow-steps)
</Info>

### Add To Static List And Remove From Static List

In a Trigger Journey, click **Add flow step** and choose **Add to static list** or **Remove from static list** from the Lists menu group.

* **Add to static list**: search for and select a static list. The step displays a green **Add** badge with the list name. When the trigger fires, Inflection adds the contact to that list.
* **Remove from static list**: search for and select a static list. The step displays a red **Remove** badge with the list name. When the trigger fires, Inflection removes the contact from that list.

<img alt="Add to static list step configured on the Trigger Journey canvas with the Add step panel open" />

<Info>
  List membership changes can take up to a few minutes to reflect.
</Info>

Read the [Journey Flow Steps Reference](/journeys/journey-flow-steps) for full configuration details.

### Run Outbound Webhook

In a Trigger Journey, click **Add flow step** and choose **Run outbound webhook** from the Integrations menu group. Search for and select an existing outbound webhook.

The step displays the webhook name, its HTTP method, and a **Captures response** badge when the webhook is configured to capture a response. When the trigger fires, Inflection calls the webhook at its destination endpoint.

Read the [Journey Flow Steps Reference](/journeys/journey-flow-steps) for full configuration details.

### Branching

Trigger journeys support the same branching flow steps as scheduled journeys. Use branching to split contacts into different paths based on their attributes or field values.

* **Branch by Filter** — Splits contacts into two paths (True / False) based on dynamic list filter criteria. Use this for precise condition-based routing using person properties. See [Journey Flow Steps Reference](/journeys/journey-flow-steps) for full configuration details.
* **Branch by Value** — Splits contacts into multiple paths based on a contact or account field value. Each unique value follows its own path, with a Default path for contacts that do not match any specified value.

## Publish Your Journey

Click **Publish** to activate the journey. The journey moves to Active status within seconds, and contacts begin enrolling in real time as qualifying events come in.


# Data Subject Erasure Requests
Source: https://docs.inflection.io/settings/data-subject-erasure-requests

Data Subject Erasure Requests (DSRs) allow individuals to request the deletion of their personal data, as required by privacy laws like GDPR and CCPA.

Data Subject Erasure Requests (DSRs) allow individuals to request the deletion of their personal data, as required by privacy laws like GDPR and CCPA. These requests are an important part of protecting user privacy and staying compliant with data regulations. In Inflection, DSRs can be handled either manually or through automated integrations

## How to add contact email(s) for an erasure request

### Option 1 - Bulk Upload CSV

1. Navigate to **Settings > Erasure Requests**.

   <img alt="Erasure Requests option in the Settings menu" />

2. Click on **“New Request”** on the top right corner.

   <img alt="New Request button on the Erasure Requests page" />

3. Upload a CSV file containing the list of email addresses to be erased.

   <Info>
     Note:

     The CSV file **must** include a header named `"email"`.

     Optionally, a `"reason"` column may be added for auditing purposes. If not provided, it will be updated as “User requested deletion”
   </Info>

   <img alt="CSV upload dialog for a new erasure request" />

4. Review the warnings displayed carefully. To confirm the erasure, type **“DELETE”** in the confirmation field.

   <img alt="Erasure confirmation dialog requiring DELETE to be typed" />

5. Once the request is processed, a CSV export will be available listing all contacts that were successfully erased.

   <Info>
     Note:

     The exported CSV will only include email addresses that were **successfully** removed. Contacts that do not exist in the database, contain invalid email formats, or fail validation for any other reason will **not** appear in the export.
   </Info>

### Option 2 - API endpoint connection for sending DSRs from external tools

1. Go to **Connection > Add Connection > Custom DSR Connection**.

   <img alt="Custom DSR Connection option in the Add Connection screen" />

2. Enter a connection name and description.

   <img alt="Dialog for entering the DSR connection name and description" />

3. You may use the shown URL and Bearer Token for sending erasure requests from external systems.

   <img alt="DSR connection details showing the endpoint URL and Bearer Token" />

4. Requests created via this method will also be shown under **Settings > Erasure Requests**.

<Info>
  For request/response details and sample calls, see the [Erasure API Endpoint documentation](/settings/erasure-api).
</Info>


# Email Settings
Source: https://docs.inflection.io/settings/email-settings

Configure global email settings, including communications limits and unsubscribe settings.

## Unsubscribe Configuration

### Default Settings

By default, an unsubscribe link is automatically included in the email header of each marketing email. Inflection's standard unsubscribe link is included in every email's header and resolves to Inflection's default opt-out page. Best for fast setup and full per-email unsubscribe-rate reporting.

When a contact clicks on the unsubscribe link, their **unsubscribed** contact field sets to **`True`**. Inflection will automatically exclude unsubscribed contacts from marketing sends.

<Info>
  "Unsubscribed" is a unique contact property that can only have **Two Way** as its Salesforce Sync Preference. This ensures that the latest subscription status is synchronized across all data connections.
</Info>

### Custom Opt-out Confirmation Page

Optionally, send contacts to a branded confirmation page after they unsubscribe. An email opt-out confirmation page is a webpage displayed to users after they unsubscribe from emails, allowing companies to personalize the opt-out experience for their audience. It offers many advantages for the brands, including:

* **Branding**: Reinforces brand identity, even during opt-out.
* **Audience feedback**: Collects reasons for unsubscribing to improve content.
* **Retention opportunity**: Offers options to adjust preferences instead of full opt-out, potentially retaining subscribers.

Inflection makes it easy to use your custom email opt-out confirmation page in your emails. Follow the steps mentioned below to use it.

#### Steps to Configure

1. In **Settings**, navigate to **Email Settings** and click the **Edit** button.

   <img alt="Email Settings page in Settings with the Edit button highlighted" />

2. You will see the option to turn on the opt-out confirmation page option. Use the toggle to turn it on.

   <img alt="Opt-out confirmation page toggle in Email Settings" />

3. Paste the URL of the custom opt-out confirmation page in the field and click **Save**.

   <img alt="Field for the custom opt-out confirmation page URL with the Save button" />

Now you have successfully set up the custom opt-out confirmation page for all of your emails. You can use it for opt-out surveys, audience feedbacks, offering alternative content, showing product offers, cool features etc.

<Tip>
  Remember to ensure that the unsubscribe URL begins with `http` or `https` to comply with email client requirements.
</Tip>

### Two-Step Opt Out

The two-step unsubscribe process adds an additional layer of confirmation. It confirms customer intent to unsubscribe, preventing accidental opt-outs. This process improves user experience and also protects against automated bots that could trigger unintended unsubscribe actions, preserving the integrity of your subscriber list.

To enable it, go to **Settings > Email Settings > Two-step opt out** and toggle the switch.

<img alt="Two-step opt out toggle in Email Settings" />

For both configurations, all unsubscribe links in the email, including the email header, will be modified accordingly.

<Info>
  Gmail may only display the unsubscribe link in the header after completing its internal trust check process.
</Info>

## Communications Limits

Communication limits can be used to prevent crowding end-user inboxes with multiple emails coming from different journeys. This can reduce marketing fatigue and unsubscribes.

### Configure Global Communications Limits

1. Go to **Settings > Communication Limits**. Click on "Edit" at the top right corner. Set the Toggle to active next to the **"Global Communication Limits"**

   <img alt="Global Communication Limits toggle in the Communication Limits settings" />

2. Choose which kind of limits you want to set. **You can set Daily Limits, Weekly Limits or both.**

3. Click save. Communication limits are now enabled. Customers will not receive emails if they exceed Daily OR Weekly limits.

<Info>
  Limits are applied on a **rolling window** from the time of sending.

  For example, if an email is sent at 9:00 AM on Monday, 17th Feb:

  1. Emails sent between 9:00 AM Sunday, 16 Feb → 9:00 AM Monday, 17 Feb are considered for daily limits
  2. Emails sent between 9:00 AM Monday, 10 Feb → 9:00 AM Monday, 17 Feb are considered for Weekly Limits
</Info>

### Override Communication Limits

You can override communication limits at 3 levels.

1. When **Ignore Send Limit** is enabled on a **Journey**, all emails within the journey will be sent to users, even if they exceed the daily or weekly limits
2. When **Ignore Send Limit** is enabled on an **Email Asset**, all flowsteps using that email Asset across different journeys will get sent to users, even if they exceed the daily or weekly limits
3. When **Ignore Send Limit** is enabled on a **Flowstep**, the email will get sent to users, even if they exceed the daily or weekly limits

#### Journeys

1. Open the Journey
2. In the left panel, go to **Journey Settings**
3. In the **Email Delivery Control** section, set the toggle to active next to **Ignore Send Limits**

<img alt="Ignore Send Limits toggle in the Email Delivery Control section of Journey Settings" />

#### Email Asset

1. Go to **Assets** → **Email**. Open the **Asset**.
   * Visual Editor Emails
     1. Click on the **Email Settings** on the top right

        <img alt="Email Settings button at the top right of the visual editor" />

     2. In the Settings panel, navigate to "Email Delivery Control" section at the bottom

     3. Set the toggle to active, next to "Ignore Send Limits"
   * Advanced Editor Emails
     1. On the Left panel, go to "Email Delivery Control" section at the bottom

        <img alt="Email Delivery Control section in the left panel of the advanced editor" />

     2. Set the toggle to active next to "Ignore Send Limits"

#### Email Flowstep

1. Open the **Journey.**

2. Click on the Email Flowstep. Click on the Pencil Icon to open the **Email Preview**

   <img alt="Pencil icon on the email flowstep that opens the Email Preview" />

3. In the Email Preview, navigate to "Email Delivery Control" section on the right bottom side

4. Set the toggle to active next to "Ignore Send Limits"

## Email Tracking

Every email in Inflection has three tracking switches that control what engagement data is collected when recipients interact with your emails. All three switches default to **on** for new emails.

### Tracking Switches

#### Track Opens

When enabled, Inflection tracks whether a recipient opened your email. Disable this to stop collecting open data for this email.

#### Track Link Clicks

When enabled, Inflection tracks when a recipient clicks any link in your email. Disable this to send links without click tracking.

#### Identify Visitors on Your Website

When enabled, a recipient who clicks a link in your email is identified as a known visitor on your website (requires website tracking to be set up). Disable this if you do not want email link clicks to trigger website visitor identification.

<img alt="Email Tracking section of the email settings drawer with the Track opens, Track link clicks, and Identify visitors on your website switches" />

<Info>
  All three switches default to **on** when you create a new email or clone an existing one. When you clone an email, the clone inherits the tracking settings from the original.
</Info>

### Tracking States

Each email displays a tracking badge on the Emails list page:

* **Full** — All three tracking switches are on (green badge)
* **Partial** — One or two switches are on, but not all three (orange badge)
* **None** — All three switches are off (gray badge)

Hover over the badge to see which switches are on and which are off.

### Warning Banner

When you turn off one or more tracking switches, a warning banner appears at the top of the email settings drawer. The banner tells you which tracking capabilities are disabled and reminds you that this affects reporting data for this email.


# Global UTM Parameters
Source: https://docs.inflection.io/settings/global-utm-parameters

Enable global UTM parameters to add tracking to links automatically.

UTM and custom parameters in email links enable precise tracking of campaign performance by capturing key details like source, medium, and campaign name. Parameters can be set at global, asset, and journey levels.

## Enable UTM Parameters in Email Links

Enabling UTM tracking globally to apply it across all emails in your workspace.

1. Navigate to **Email Settings** from the Settings page. Click **Edit**.

2. Toggle on **URL Parameters** in the **Email link parameters** section.

3. By default, the below UTM values will be configured at global level. These values can be overridden at email level.

   UTM source: `inflection`<br />UTM medium: `email`<br />UTM campaign: `{{journey name}}`<br />UTM content: `{{email name}}`

4. To add custom parameters, click **Add custom parameter** and update parameter key and value for each.

5. Save your changes to apply the defaults to all new and existing email assets and flow steps.

<img alt="URL Parameters toggle in the Email link parameters section of Email Settings" />

<Info>
  Note:

  * Tokens are not supported in global settings. However, you can override URL parameters with tokens at the email asset and flow step level.
  * UTM tracking cannot be disabled at lower levels once enabled globally.
</Info>

***

## Configure UTM Parameters at the Email Asset Level

Users can override the global UTM defaults and add more granular parameters within each email asset.

1. Open the email asset and click on the **Link Parameters** button at the top.

   <img alt="Link Parameters button at the top of the email asset editor" />

2. Review inherited UTM parameters which appear pre-filled and cannot be deleted.

3. Override any UTM field with a string or token value specific to the asset.

4. Add custom parameters with static text values or tokens.

   <img alt="Link parameters panel with UTM fields and custom parameters" />

   <Note>
     Once you override global default values, you will have the option to **Reset to global default**.
   </Note>

5. Click on **Done** to save the settings to the email asset.

***

## Configure UTM Parameters at the Journey Flow Step Level

Customize link parameters further at the flow step level within a journey for even more precision.

1. Open the journey and click on the email flow step to bring up a preview of the email.
2. To add new custom parameters unique to the flow step, click **Link parameter configuration**.
3. Review inherited parameters from the asset and global levels.
4. Override any UTM or custom parameter using a string or token.
5. You can add more parameters at the email flow step level, or override existing parameter values
6. Save the flow step settings to apply your changes.

***

## Inheritance and Precedence

The system uses a clear override hierarchy to manage parameters across levels.

1. Parameters flow from **Global → Email Asset → Journey flow step**.
2. Lower levels inherit values only if no overrides are set.
3. Overridden values remain fixed even if global settings change later.
4. Reset actions are available to reapply inherited values from immediate parent only.


# MMC Dashboard
Source: https://docs.inflection.io/settings/mmc-dashboard

Visibility into monthly usage overall and journey-by-journey.

## Monthly Marketed Contacts

MMCs are **unique contacts** (unique by email address) who route through one or more Inflection journeys in a given calendar month (i.e. August 1-August 31).

* Inflection does not charge for contact database volume, marketable contacts, seats or data volumes.
* Non-personalized batch journeys (i.e. typical newsletters) do not count against MMC cap, provided there are no MMC-triggering elements in the batch journey.

<Info>
  Read a more detailed MMC description here: [MMCs (Monthly Marketed Contacts)](/getting-started/mmcs).
</Info>

## The Dashboard

The **MMC Dashboard** displays how many contacts your Inflection instance has processed in a given month, giving you visibility into MMC and non-MMC usage overall and journey-by-journey.

When you open the MMC Dashboard, you'll see:

1. **Summary Metrics**
   * **Unique MMCs**: Unique contacts who meet MMC criteria in the selected month
   * **Total Contacts**: All contacts who qualified for a journey (both MMC and non-MMC) in the selected month
   * **Non MMC Contacts**: Unique contacts who qualified for journeys that do not meet MMC criteria in the selected month
   * **MMC contacts**: Unique contacts who meet MMC criteria in the selected month
   * **Total Journeys**: The number of journeys in a selected month used for MMC and Non MMC calculations
2. **Journey Drilldown**

   The Journey drilldown is designed to help you quickly identify MMC vs Non MMC counts and reasons for MMC qualification.

   A detailed table shows:

   * Journey Name
   * Last Run Date
   * Total Runs (sortable)
   * MMC vs Non MMC Totals (sortable)
   * Reasons (additional context on qualification)

   You can **search, filter, or export** this drill down for deeper analysis.

   <img alt="MMC Dashboard with summary metrics and the journey drilldown table" />

<Info>
  Trigger Journeys appear in the Journey Drilldown alongside scheduled journeys. For a Trigger Journey:

  * Every enrolled contact counts as an MMC, so the **Non MMC** total is always 0.
  * **Total Runs** is the number of times the journey was triggered during the month. A contact is still counted as one MMC (unique by email) even if they trigger the journey multiple times.
  * The **Reasons** column identifies the journey as a Trigger Journey.

  To confirm a specific contact was enrolled, open the journey's **Reports** tab and check the **Recipients** list.
</Info>

You can also expand the reasons field to view the MMC qualifying reason for each journey, and export the journey drilldown data for offline deeper analysis.

<img alt="Expanded Reasons field showing the MMC qualifying reason for a journey" />

### Filtering Option

You can filter the journey drill-down by:

* **Last Run Date** – pick from quick options (last week, last month, last quarter, etc.) or set a custom date range using the calendar picker.

<img alt="Last Run Date filter with quick options and custom date range calendar picker" />


# User Management
Source: https://docs.inflection.io/settings/user-management

Manage the users of your Inflection workspace based on your organizational needs.

Inflection's user management settings enable you to manage the users of your Inflection workspace based on your organizational needs. With this, you can invite new users to your workspace, assign different roles to the users and update the settings anytime.

## Roles

There are three roles in an Inflection workspace: Viewer, User, and Admin. As the name suggests, Admins have complete control over the workspace, they can invite and deactivate users and update user roles anytime. Users have basic access to the workspace, they can create journeys, assets like emails, webhooks, forms, etc. but they cannot invite or edit users or access the workspace settings.

<Tip>
  Admin role is usually assigned to marketing operations team while the marketers and content creators would be added as users.
</Tip>

## Invite a User

Follow these steps to learn how to invite new users to your Inflection workspace:

1. Go to **Settings** and then navigate to the **Users** tab

2. Click on **Invite users** button

   <img alt="Users tab in Settings with the Invite users button" />

3. Type in the name and email address of the user and assign a user role to that person.

4. You can add multiple users at one time by clicking on the **+** icon.

5. Click **Send invite** button to finish adding the user to the workspace.

   <img alt="Invite users dialog with name, email, and role fields and the Send invite button" />

After completing the above steps, the invited user will receive an email to join the workspace by setting their login credentials.

<img alt="Invitation email prompting the user to join the Inflection workspace" />

If you want to re-invite a user or cancel the invitation, you can click on the 3 dots icon on the right side of the specific user and choose your option.

## Deactivate a User

Follow these steps to learn how to deactivate an existing user in your Inflection workspace:

1. Go to **Settings** and then navigate to the **Users** tab

2. Find the user you want to deactivate and click on the 3 dots icon on the right and click on **Deactivate** button.

   <img alt="Deactivate option in the 3 dots menu of a user row" />

3. A confirmation pop-up will show up, click on the **Deactivate** button.

   <img alt="Deactivate user confirmation pop-up" />

## Update a User's Role

Follow these steps to learn how to update the existing user's workspace role:

1. Go to **Settings** and then navigate to the **Users** tab

2. Find the user you want to deactivate and click on the 3 dots icon on the right.

3. Click on the **Edit** button

   <img alt="Edit option in the 3 dots menu of a user row" />

4. In the pop-up window, click on the dropdown for the user role and select the desired role for that user and click on **Update user** button.

   <img alt="Update user dialog with the role dropdown and Update user button" />


# April 2026
Source: https://docs.inflection.io/whats-new/april-2026

Data Normalization, Conversions for user field changes, Wait for SFDC Sync flowstep, native form enhancements, UI updates, and Help Center 1.2.

* **Data Normalization**: A powerful way to clean up inconsistent field values across your contact database. Powered by AI, the mapping engine analyzes your input prompt and your existing values, then suggests smart groupings and mappings in seconds. You simply review and save. Write normalized values directly back to the source field, or preserve your raw data by routing output to a separate field. New incoming data is normalized the moment it is ingested, and you can backfill historical records with a single click. Find it under Database > Data Normalization and start with the fields that matter most to your reporting and segmentation. Some example use cases:
  * Convert all your countries to two-letter ISO codes
  * Standardize US states to letter codes
  * Keep your lead sources in consistent lowercase
  * Map hundreds of different job titles into cleaner job functions
* **Conversions Enhancement**: Use Conversions to help answer if your journeys are driving the outcomes you care about. Define Conversion events and link them to your journeys to measure outcomes! You can now add User field changes to measure conversions, in addition to Contact field changes, marketing actions, and product activities.
* **Wait for SFDC Sync flowstep**: This flowstep delays journey steps until the next Salesforce sync run completes. Use this step when downstream actions in your journey depend on data that has been written back to Salesforce.
* **Native Form Enhancements**: As a follow up to our initial release of Inflection Native Forms in March '26, we've added several enhancements including: field mapping overwrite rules, the ability to create new forms from the Folders tab, form submissions as Marketing Activity events, transparent background settings, consent checkbox mapping, and reCAPTCHA capabilities.
* **UI Enhancements**: Based on user feedback, we continue to update the UI for a better Inflection experience. In the April release, we're introducing the following changes:
  * Journey audience: the audience criteria UI on the journey page has been updated to make it easier to distinguish between outer groups and filter groups, with a clearer visual separation between operators and operands.
  * Email reports: a new Sent tab has been added to the Email Report's recipients page. Use this tab to see recipients that were sent emails from a journey. The Sent tab lives alongside the existing All, Not Sent, Open, Click, Bounce, Unsub, and Spam tabs.
* **Agent-Automated Email Migration**: Work with the Inflection team to build a custom Claude skill that migrates emails from a third-party platform in bulk or on an ongoing basis. Reach out to your customer success team if you're interested.
* **Inflection Help Center 1.2**: Now live at [docs.inflection.io](https://docs.inflection.io)! We've refreshed the content, reorganized the sections, and updated screenshots throughout, and the Inflection Agent pulls from these articles when answering your product questions!


# August 2026
Source: https://docs.inflection.io/whats-new/august-2026

Delete Contacts journey flow step, more flow steps in Trigger Journeys, hours as a time unit in audience filters, preview for advanced HTML emails, marketing activity in tokens, Deleted label on removed email assets, and Amplitude group properties.

* **Delete Contacts Journey Flowstep**: Journeys now include a "Delete contacts" step, found under Lists & Data in the flowstep menu. Any contact who reaches it is permanently removed from Inflection, along with their list and campaign membership. It works in both scheduled and trigger journeys, and it is always the final step in a flow since nothing can run after it. The step shows a running count of contacts deleted and in progress, and you can open a report listing every deleted contact with the date and time, then export it. An "Allow recreate" setting controls whether that person can enter your database again later. This is built for privacy requests, test data cleanup, and keeping your contact database accurate. Product documentation found [here](/journeys/journey-flow-steps#delete-contacts).
* **More Flow Steps in Trigger Journeys**: Trigger journeys now support three steps that were previously only available in scheduled journeys: Add to static list, Remove from static list, and Run outbound webhook. You can now build a real-time flow that reacts to an action, updates list membership, and notifies a downstream system all in one place, instead of waiting for a scheduled run. Product documentation found [here](/journeys/trigger-journeys#supported-flow-steps).
* **Hours as a Time Unit in Audience Filters**: When building a dynamic list or setting audience criteria on website or marketing activity, you can now filter by hour in addition to day, week, and month. So "visited the pricing page in the past 4 hours" is now possible, where previously the shortest window was a full day. This makes same-day follow-up and high-intent targeting far more precise. Product documentation found [here](/database/building-audiences#filters).
* **Preview for Advanced HTML Emails**: Emails built with the HTML editor (Advanced) now have a full preview, which previously was only available for emails built in the drag and drop (Visual) editor. Open the preview to see your email rendered as recipients will see it, toggle between desktop and mobile views, and enter any contact's email address to see their personalization fields resolve with real values. This removes the guesswork from hand-coded emails and cuts down on test sends. Product documentation found [here](/journeys/emails#build-with-html-editor-advanced).
* **Marketing Activity in Tokens**: Tokens can now pull from a contact's marketing activity, not just their profile fields. You can reference page visits, email opens and clicks, form submissions, inbound webhook submissions, and Salesforce campaign membership, and either count them over a time window or return the most recent one. For example, "you've visited our pricing page 3 times this month," or an email that references the last webinar someone registered for. Conditions let you narrow to a specific URL, page title, referrer, UTM value, form name, webhook name, or campaign type, and every token takes a fallback value so contacts with no activity still get clean copy. There are 12 new functions and 16 condition helpers in total, with the full reference in the docs. Product documentation found [here](/journeys/tokens#marketing-activity-tokens).
* **"Deleted" Label on Removed Email Asset**: When an email asset gets deleted in Inflection, you'll now see a clear "Deleted" label instead of wondering what happened. If an audience filter points to an email template that has since been deleted, the filter keeps working and the template name carries a yellow "Deleted" tag. Small change, but it removes a common source of confusion when auditing older lists and campaigns.
* **Amplitude Integration (Group Properties)**: An extension of our Amplitude integration that brings org-level data into Inflection. Amplitude stores org and workspace attributes such as plan type, entitlements, and billing cycle as "group properties." This update syncs them in, so you can build audiences and target journeys on org-level data, not just individual user activity. For example, target everyone in orgs on a Starter plan, or exclude demo accounts from your sends. Product documentation found [here](/connections/amplitude#sync-group-properties-from-amplitude).

The following features are not yet generally available, but will be released over the upcoming weeks on a customer by customer basis:

* **Unified Mapping v2**: A major upgrade to Unified Mapping, the screen where your connected data sources map to Inflection fields. You'll be able to manage far more of this yourself: map contact, account, and user fields, add and delete fields, connect and map data warehouse data, and set multiple sources per field, all from one place. Product documentation found [here](/connections/unified-mapping).
* **Inbound Webhooks and Forms Redesign**: We've rebuilt the setup and management experience for inbound webhooks and forms. Setup is a simpler two-step flow: create the endpoint, then map the fields. You send a sample payload, Inflection detects the fields for you, and you map them to contact fields on one screen. Each connection now has a single details page showing submissions, groups, errors, and connection health at a glance, plus pause, resume, and disable controls. All your forms now appear in one unified list regardless of provider, and creating a new form walks you through Inflection forms, Webflow, Formstack, or a custom form connection. Inbound webhooks documentation found [here](/connections/inbound-webhooks). Custom forms documentation found [here](/connections/custom-forms). Inflection forms documentation found [here](/connections/inflection-forms).
* **Bot Filtering and Engagement Deduplication**: Email reports will be able to strip out automated opens and clicks so your numbers reflect real people. Security scanners and link checkers routinely open every image and follow every link in an email the moment it arrives, and privacy services such as Apple Mail Privacy Protection and Gmail's image proxy pre-load tracking images whether or not anyone actually reads the message. A Bot filter control on the email report gives you the ability to exclude suspected bot activity. Alongside this, repeat opens from the same person on the same send are consolidated into a single counted open, so your open count reflects distinct readers rather than raw image loads.


# February 2026
Source: https://docs.inflection.io/whats-new/february-2026

Viewer role, dynamic list usability enhancements, email template ID in Segment export, and Help Center content in the Inflection Agent.

* **Viewer Role**: Viewer role types have read-only access in Inflection. They can view journeys, dynamic list previews, assets, database records, reporting, and connections, but cannot perform any create, edit, delete, or export functions.
* **Dynamic List Usability Enhancements**: We've made improvements to Dynamic List usability to improve user speed and agility as they segment and target in Inflection:
  * Operators are now organized, more complete, and visual
  * Drop-down lists (like product activities, journey names, etc.) are now alphabetized
  * Multiple values are now accepted for form names, list names, and inbound webhooks
* **Email Template ID Added to Segment Export**: We've added email template ID as a property in Segment bidirectional sync (aka export).
* **Inflection Help Center Content Integrated with Inflection Agent**: The Inflection Agent can respond to support questions by summarizing articles from our Help Center.


# January 2026
Source: https://docs.inflection.io/whats-new/january-2026

Conversions, Activity Log, MCP OAuth 2.1 beta, folder enhancements, Product Data Explorer redesign, and MMC indicators.

* **Conversions**: Use Conversions to help answer if your journeys are driving the outcomes you care about. Define Conversion events (Marketing actions, Product activities, Contact Field value changes) and link them to your journeys to measure outcomes!
* **Activity Log**: We're introducing the Activity Log, a new tab on the Contact record that provides a chronological view of changes made to the Contact and User record. See exactly what changed, when it changed, and where the change came from.
* **OAuth 2.1 Authentication for Inflection MCP (Beta)**: Inflection now supports OAuth 2.1 authentication, providing secure, standardized access to our MCP server. This enables seamless integration with AI assistants, automation platforms, and custom applications without sharing passwords. Beta participation will be evaluated on a customer by customer basis.
* **Folder Enhancements**: We've upgraded the Folders experience with powerful organization tools to help you manage your assets more efficiently. Quickly move single or multiple items into folders by dragging them directly from your list. Sort your folders by creation date (newest/oldest first) or alphabetically (A-Z or Z-A) right from the Folders UI.
* **Timezone Labels in UI**: We've added timezone labels to all date and time displays across the platform, making it crystal clear when events occurred and when syncs ran, especially valuable for multi-timezone teams!
* **Product Data Explorer Enhancements**: We've completely redesigned the Product Data Explorer with powerful new capabilities to help you manage and analyze your event data more efficiently. Filter events by status and date ranges. Sort by name, volume, or recency to quickly find what you need. Search by event or property name to discover events even when you only know the property identifier. Export your entire event catalog or filtered views for offline analysis, auditing, or team sharing.
* **Data Type Assignment for Product Activity Properties (Segment Data)**: Assign the correct data type (Int, Float, String, Boolean, DateTime) to each product activity property, enabling powerful type-specific operators like greater than, less than, and date comparisons.
* **MMC Indicator at Journey Level**: We've added proactive MMC indicators throughout the Journey building process to help you optimize your MMC management and avoid unexpected MMC consumption.


# July 2026
Source: https://docs.inflection.io/whats-new/july-2026

Inflection Public API (V1), Personalized Email Asset, Send Internal Alert for Trigger Journeys, journey lifecycle events in Data Warehouse and Segment writeback, shorter tracking URLs, and a redesigned Help Center.

* **Inflection Public API (V1)**: You can now connect to Inflection programmatically to read and manage your data outside the Inflection app. This first version covers contacts (look up, create, and update contacts, and pull their marketing activity, product activity, and linked Salesforce record), static lists (create and manage lists and their members), and email templates (look up, create). This opens the door to syncing Inflection with your own systems and automating routine data work.
* **Personalized Email Asset**: A single email can now hold a default version plus a tailored version for each individual contact, so every person receives the message written for them and anyone without a custom version automatically gets the default. There's never a blank send. Per-contact versions can be generated by an AI agent (i.e. Claude, in Clay, etc.) and sent into Inflection, which makes producing hundreds of individualized emails fast instead of manual.
* **Send Internal Alert (Trigger Journeys)**: Trigger Journeys now include a "Send internal email alert" step, so the moment a contact takes a qualifying action (like submitting a form), your team gets notified by email in real time. Pick an email template, add one or more internal recipients, and the alert fires automatically as part of the journey. This is ideal for fast sales follow-up and keeping account owners in the loop the instant something happens.
* **Journey Entry/Exit Events in Data Warehouse and Segment Writeback**: Inflection can now send journey lifecycle events (when a contact enters, completes, or exits a journey) to your connected data warehouse and your Segment workspace, alongside the email, form, and webhook events we already write back. This gives your data and operations teams a full picture of journey participation in the tools they already use, so they can report on journey performance and pass those events on to other systems.
* **Tracking URL Enhancements**: We've dramatically shortened the tracking links Inflection adds to your emails (the links behind clicks, images, opens, and unsubscribes). These used to run around 1,200 characters each and are now 70 to 85 percent shorter, roughly 200 to 300 characters. Because those links no longer add so much weight to your emails, your messages are lighter, less likely to be flagged by spam filters or clipped by providers like Gmail, and links are far less likely to get cut off in email clients that shorten long URLs. The improvement is most noticeable in image-heavy emails such as newsletters.
* **New Help Center**: We've launched a redesigned Help Center to make finding answers, troubleshooting, and self-serve enablement faster and easier.


# June 10, 2026
Source: https://docs.inflection.io/whats-new/june-10-2026

Edit templates by name, restyle emails in plain language, richer in-app chat, email grading, and 20+ new MCP tools.

*AI release*

* **Edit a saved email template by name**: you can say "edit the 'Welcome' email" without supplying a template ID.
* **Restyle emails in plain language**: change button color, font size, spacing, and padding by describing the change.
* **Richer in-app chat**: includes a live plan as the agent works, streaming activity, a tree view for parallel tasks, and email preview thumbnails on result cards.
* **Email-grading skill**: drop in an email to get an audit. Available to all users.
* **Accurate analytics**: fixed a display issue that caused counts and rates to render incorrectly.
* **20+ new MCP tools**: covers email clone, form and webhook submission breakdowns, Salesforce opportunity filters, live in-flight send status, and unified date filtering.

<Info>
  **New use cases**

  * "Edit the 'Trial Welcome' email and make the CTA green": restyle a template without opening the editor.
  * Audit any email for quality before sending.
  * Pull live "what's sending right now" status from chat.
</Info>


# June 2026
Source: https://docs.inflection.io/whats-new/june-2026

New Journey Canvas, Account Scoring, Amplitude integration (read), SFDC Opportunity matching strategies, inbound webhook deletion, and Trigger Journey audience filters.

* **Journey Canvas Usability Enhancements**: A complete re-write of our Journey canvas UX to introduce multiple optimizations, including: drag and drop flowsteps, drag connectors, duplicate flowsteps, copy paste flowsteps, undo/redo capability, safe parent-node deletions, journey canvas sticky notes, and more! Existing journeys are automatically migrated to the new canvas.
* **Account Scoring**: Account Scoring lets you build models that grade every account in your tenant from 0 to 100 based on the signals that define a strong fit for your business. Once a model is active, the score becomes a regular field on the Account object, available immediately in dynamic lists, journey branches, and anywhere else you use Account properties.
* **Amplitude Integration (Read)**: Amplitude is a product analytics platform that captures user and group behavior across your web, mobile, and server applications. The Amplitude integration lets Inflection receive those events as a source, so you can use Amplitude product activity to build audiences, journey filters, and personalize messaging in Inflection. V1 covers product activity events and user identify properties; group call data sync follows in a future release.
* **SFDC Opportunity Object (Read) v2**: This enhancement introduces Opportunity Matching Strategy configuration options, which allows you to dictate how contacts get matched to SFDC opportunities. You have the ability to choose between Deal Team Only, SFDC Account Only, or SFDC + Inflection Matches.
* **Delete Inbound Webhooks**: Delete inbound webhooks you no longer need, for example after migrating to a new provider or cleaning up webhooks created during testing. Deleting a webhook stops its endpoint URL from accepting new events.
* **Trigger Journey Audience Filter (Contact Properties)**: You can now add audience filters to Trigger journeys. This enhancement includes contact property filters; additional filter options will be added in future releases.


# June 3, 2026
Source: https://docs.inflection.io/whats-new/june-3-2026

Grounded audience building, faster email drafting, dashboard-accurate analytics, and token math for PQL scores.

*AI release*

* **Audiences and segments ground in your real data**: the agent checks your actual field values before building, so targeting is correct on the first try.
* **Better, faster email drafting**: tighter copy, less repetition, and lower cost per build.
* **Analytics match the dashboard**: correct labels and rates, plus a share-of-processed chart for single campaigns.
* **Token math**: build composite **PQL scores** from token arithmetic, with a verified preview.

<Info>
  **New use cases**

  * "Build a score = 3×demo\_requests + 1×email\_opens over 90 days" for lead prioritization.
  * Trust audience and segment counts without manually verifying field names.
</Info>


# March 2026
Source: https://docs.inflection.io/whats-new/march-2026

Inflection Native Forms, outbound webhook response mapping, customizable exports, and Salesforce performance improvements.

* **Inflection Native Forms**: In addition to packaged integrations with Webflow and Formstack forms, and custom form integration capability, we now have Inflection native forms! Create conversion-optimized forms in minutes using your existing contact fields, then connect them to Journeys for instant automated follow-up. No manual data mapping or third-party form tools required.
* **Outbound Webhook with Response Mapping**: Outbound webhooks have been enhanced to allow response mapping to contact fields. Response mapping allows webhook response data to automatically update contact fields in Inflection, simplifying use cases such as, but not limited to, data enrichment, email address validation, calling external LLMs, and scoring data integration.
* **Customizable Exports**: Inflection now lets you customize exports for contact and audience lists as a CSV file. This can be performed from your dynamic lists, journey audiences, journey reports, and static lists!
* **Salesforce Service Performance Improvements**: We're making the Salesforce connection more efficient by dedicating backend resources to full-resyncs triggered by adding new custom fields and other changes made to connection config. This enhancement ensures that regular Salesforce sync runs are not impacted by full-resyncs.
* **Contact Activity Log UX Enhancements**: As a follow up to our release of Activity Log in January, we improved the UX specifically around the "show details" action. You will now find a cleaner display of details with better usability.
* **Datawarehouse Sync History Enhancements**: We continue to improve the data provided in the connections UI around datawarehouse sync history. You will now see table-level details, including sync status and error messages.


# May 12, 2026
Source: https://docs.inflection.io/whats-new/may-12-2026

Build and edit by conversation, a streamlined MCP, artifacts in the in-app chat, and agents in Slack and Asana.

*AI release*

* **Build and edit by conversation**: audiences, emails, tokens, and segments, saved directly to Inflection.
* **A streamlined MCP**: consolidated to a clean set of tools across your whole workspace.
* **Artifacts in the in-app chat**: see what the agent builds, inline.
* **Agents in Slack and Asana**: start a campaign from your team channel, or turn a tagged Asana task into an email.

<Info>
  **New use cases**

  * Go from a campaign brief to a reviewable journey (audience, emails, and flow) in one sitting.
  * Kick off a campaign from Slack with approval gates.
</Info>


# May 2026
Source: https://docs.inflection.io/whats-new/may-2026

Trigger Journeys, SFDC Opportunity sync, Data Dictionary, unified mapping enhancements, richer form and webhook filters, and link tracking optimizations.

* **Trigger Journeys**: Trigger Journeys enroll contacts automatically the moment a real-time event occurs, enabling instant follow-up and event-driven automation at scale. Unlike Scheduled Journeys, which run against a pre-defined audience at a set time, Trigger Journeys respond to individual contact actions as they happen when a qualifying event occurs. Qualifying triggers for this V1 version of Trigger Journeys include form submissions and inbound webhooks, and a limited number of flowsteps. Additional qualifying events and flowsteps will be added in future releases.
* **SFDC Opportunity Object (Read)**: Inflection now syncs SFDC Opportunities natively, with no workarounds needed. Users can build Dynamic List audiences filtered by deal stage, amount, close date, and custom fields, and suppress campaigns for contacts in active negotiations.
* **Data Dictionary**: A new Field Insights panel appears inline while building Dynamic List filters, journey audience, or conversion events, showing field population stats, data types, min/max ranges, and a searchable list of real field values directly where you need them. No more guessing what's in a field or filing tickets to understand your data. Admins can also add plain-English field descriptions in Unified Mapping, which surface in Field Insights and power AI agent context via MCP.
* **Unified Mapping Enhancements (Segment identify call traits and deleting fields)**: This change brings two important changes to unified mapping: 1) the ability to map Segment identify call attributes to Contact fields, and 2) the ability to delete Contact and Account fields. Additional enhancements to unified mapping will be added in future releases.
* **Forms/Inbound Webhook Filter Enhancements**: Forms and Inbound Webhooks in Dynamic List audience now support multiple filter conditions, not just one. Marketers can define richer entry criteria for form-triggered journeys, combining conditions like "submitted form X" AND "has property Y" AND "has property Z", reducing the need for downstream branching logic.
* **Link Tracking URL Optimizations**: Tracking URLs embedded in emails (links, images, beacons, unsubscribe) have been reduced by 70 to 80%. This directly addresses email size issues encountered by users with image-heavy newsletters, improves deliverability, and reduces the risk of emails being flagged or clipped by email clients.


# May 29, 2026
Source: https://docs.inflection.io/whats-new/may-29-2026

Analytics in chat and MCP, file attachments in the in-app chat, and more reliable token building.

*AI release*

* **Analytics in chat and MCP**: campaign and journey rollups, breakdowns (top links, email-client opens and clicks, recipient engagement), and contact lookups.
* **Attach files in the in-app chat**: hand the agent a brief or asset to work from.
* **More reliable token building.**

<Info>
  **New use cases**

  * "How did the Q1 newsletter perform?": get an answer without leaving chat.
  * Look up a contact and their recent activity directly from chat.
</Info>