Flint doesn't have a native Salesforce integration yet, but many customers have set up a working connection by giving an AI agent access to Salesforce. The agent reads account data, enriches it as needed, and calls the Flint API to generate a personalized landing page for each account.

This pattern is especially common with Salesforce-heavy sales teams. Reps trigger the process (or it runs automatically on pipeline stage changes) and get a ready-to-share personalized page without leaving their workflow.

A good example of this in practice is Airtable. Their sales reps use an internal bot that:

1. 1.Reads account and opportunity data from Salesforce (company size, industry, stage, key contacts, notes)
2. 2.Enriches the context with any additional research
3. 3.Calls the Flint API with that context to generate a personalized ABM page for the account
4. 4.Returns the page URL to the rep so they can share it in outreach or deal conversations

The reps never leave their tools - the bot handles the Flint page creation in the background and drops the URL wherever it's needed.

The general pattern looks like this:

1. 1.A trigger fires - a rep types a command, a Salesforce opportunity reaches a certain stage, or a new account is created
2. 2.An AI agent (or automation tool) queries Salesforce for the relevant account data
3. 3.The agent optionally enriches the data with additional research (news, LinkedIn, website content)
4. 4.The agent sends a POST request to the Flint API with the account context
5. 5.Flint generates a personalized landing page based on your template
6. 6.The page URL is returned and stored - in Salesforce, in Slack, or wherever your team works

• •A Flint account with API access (sign up at flint.com)
• •A Salesforce account with API access
• •An AI agent or automation tool that can read Salesforce data and make HTTP requests
• •An ABM page template already created in Flint
• •Your Flint Site ID and API Key from https://app.tryflint.com/app/team

This is the most flexible approach and works well for sales teams that already use internal AI tools.

You can use tools like Relay.app, n8n, or a custom agent built with the Claude API or OpenAI to orchestrate this:

1. 1.Configure your agent with Salesforce read access (via the Salesforce REST API or a native connector)
2. 2.Define a prompt or workflow that instructs the agent to pull relevant account fields: company name, industry, ARR, number of employees, opportunity stage, key contacts, and any account notes
3. 3.Have the agent format this data and send it to the Flint API as the context field in the request body
4. 4.Receive the generated page URL and store it back in Salesforce (on the account or opportunity record) or post it to Slack

For the Flint API request format, see the API documentation.

Relay.app supports Salesforce as a trigger and includes built-in AI enrichment steps. This is a good option if you want a no-code setup.

1. 1.In Relay.app, create a workflow triggered by a Salesforce event (new opportunity, stage change, etc.)
2. 2.Add steps to pull additional account context from Salesforce
3. 3.Add AI enrichment steps if needed (company research, LinkedIn, news)
4. 4.Add an HTTP request step to call the Flint API
5. 5.Optionally add a Salesforce step to write the page URL back to the opportunity or account record

See the Relay.app + Flint guide for a detailed walkthrough - it uses HubSpot and Attio as examples but the pattern is the same for Salesforce.

Both Zapier and n8n have Salesforce connectors that work well for this use case.

• •Zapier: Use a Salesforce trigger (updated opportunity, new account, etc.), pull the relevant fields, then use a Webhooks step to call the Flint API
• •n8n: Build a workflow with a Salesforce trigger node, an HTTP Request node for the Flint API, and an optional Salesforce node to write the URL back

Both tools let you map Salesforce fields directly into the Flint API request body without writing code.

• •The more Salesforce context you pass, the more personalized the generated page will be. Include opportunity stage, key pain points from notes, and the primary contact's role.
• •Store the generated page URL as a custom field on the Salesforce opportunity record so reps can find it without switching tools.
• •Trigger page generation at a specific pipeline stage (e.g., when an opportunity moves to "Evaluation") rather than on every new account, to avoid generating pages for cold leads.
• •If your team uses Slack, have the automation post the page URL to a sales channel so the rep gets an immediate notification.

• •Auto Pages for New CRM Records with Relay.app - Full walkthrough using Relay.app with CRM triggers
• •Flint API & MCP - API reference for programmatic page generation
• •Airtable Page Generator - Another example of API-driven page generation from external data

Sign up for Flint

Read the Relay.app + Flint guide