Last updated: May 26, 2026

The Tofu + Salesforce integration connects Tofu, an AI-native B2B marketing platform, directly to your Salesforce CRM instance to create a closed-loop system for generating, delivering, and measuring personalized marketing content at scale. This integration enables marketing teams to pull account, contact, opportunity, and campaign data from Salesforce into Tofu's AI content engine, generate fully personalized campaign assets for every target account, and push finished content plus engagement data back into Salesforce where it can be tracked, attributed, and acted upon by sales. If your organization runs Salesforce as its system of record and struggles to produce enough personalized content for ABM programs, multi-touch campaigns, or deal acceleration workflows, this integration eliminates the manual content creation bottleneck that prevents teams from scaling beyond a few dozen target accounts. This guide walks through every detail a marketing ops professional needs: how data flows between the two platforms, how to set up and configure the integration, the specific use cases it unlocks, what syncs and what does not, how Tofu fits alongside Pardot and Marketing Cloud, and answers to the most frequently asked technical questions.

What the Integration Does

At its core, the Tofu + Salesforce integration creates a bidirectional data bridge between your CRM and Tofu's AI content generation engine. Salesforce serves as the source of truth for your account hierarchy, contact records, opportunity pipeline, campaign membership, and custom objects. Tofu reads that data to understand each target account's industry, size, technology stack, deal stage, and buyer personas, then uses that context to generate personalized campaign content. Finished assets and engagement data flow back into Salesforce where they attach to the appropriate records for sales visibility, lead scoring, and campaign attribution.

The integration connects through Salesforce's Connected App framework using OAuth 2.0 authentication. Your Salesforce administrator creates or approves a Connected App, grants Tofu the required API permissions, and the platforms maintain a persistent, token-refreshing connection. No third-party middleware such as Zapier, Workato, or MuleSoft is required for the core integration, although those tools can complement it for highly customized workflows involving non-standard objects or external data warehouses. The native connection handles authentication, token refresh, rate limiting, and Salesforce API versioning automatically.

In practical terms, here is how the integration works end to end. Your marketing team creates a campaign brief in Tofu that specifies the campaign theme, target personas, value propositions, messaging angles, and asset types needed. Tofu pulls the relevant account and contact data from Salesforce, enriching each record's profile with industry context, opportunity stage, engagement history, and any custom field data you have mapped. The AI engine then generates complete, production-ready assets: landing pages tailored to each target account's specific situation, email sequences that reference the prospect's deal stage and pain points, one-pagers that speak to the buyer's role and industry, and ad copy variations optimized for each segment. Those assets can then be delivered as links on Salesforce records, pushed to connected marketing automation tools, or hosted on Tofu-managed microsites with tracking that writes engagement data back to Salesforce.

The net result is that your Salesforce instance becomes both the data source that fuels content personalization and the system that receives engagement intelligence back, creating a feedback loop where every content interaction is visible to sales reps on the records they already work in daily.

How Data Flows Between Tofu and Salesforce

Understanding the data flow is essential for marketing ops and Salesforce administrators who need to manage permissions, ensure data integrity, and maintain compliance. The integration moves data in two clear directions, with defined boundaries around what Tofu reads from Salesforce versus what it writes back.

Data syncs operate on a near-real-time basis for most record types. Salesforce Streaming API and Platform Events enable Tofu to listen for changes to account, contact, and opportunity records as they happen, with most updates reflected in Tofu within two to five minutes. Bulk syncs for initial data loads or large-scale list imports use the Salesforce Bulk API 2.0 and typically complete within 15 to 45 minutes depending on org size. Engagement data flows from Tofu back to Salesforce as activities are recorded, with a typical latency of under one minute for individual events and batched writes every five minutes for high-volume campaigns.

Setup Guide

Setting up the Tofu + Salesforce integration requires Salesforce System Administrator permissions (or a user profile with Manage Connected Apps and API Enabled permissions) and a Tofu account with the integration tier. The full setup process takes 30 to 60 minutes depending on your Salesforce org's complexity, the number of custom objects you want to sync, and whether you need to create custom fields for Tofu data writeback. Below is the complete step-by-step process.

Step 1: Connecting Your Salesforce Org

Begin in your Tofu workspace by navigating to Settings → Integrations → Salesforce. Click Connect Salesforce to initiate the OAuth 2.0 flow. You will be redirected to the Salesforce login page where you should authenticate with an account that has System Administrator privileges. If your org uses My Domain (which most production orgs do), the login URL will automatically resolve to your custom domain.

Tofu supports both production and sandbox Salesforce orgs. If you want to test the integration in a sandbox first, select the Sandbox toggle before initiating the OAuth flow. Sandbox connections use the test.salesforce.com login endpoint. Most teams test in a full or partial copy sandbox before connecting their production org, which is the recommended approach for organizations with complex Salesforce configurations.

During the OAuth authorization, Salesforce will display the permissions Tofu is requesting through the Connected App configuration. These include:

• API access (api): Required for all data read and write operations via the Salesforce REST and Bulk APIs
• Refresh token (refresh_token, offline_access): Allows Tofu to maintain the connection without requiring re-authentication
• Read access to Accounts, Contacts, Leads, Opportunities, Campaigns, Campaign Members, and configured Custom Objects
• Write access to custom fields (Tofu-namespaced fields only), Activities, Tasks, Campaign Member Status, and the Salesforce Files/Content system
• Streaming API access: Enables real-time change detection for trigger-based content generation

Tofu does not request or receive access to modify your Salesforce org configuration, automation rules (Flows, Process Builder, Apex triggers), permission sets, or user records. The integration operates strictly at the data level: it reads records for personalization context and writes back content links, engagement activities, and campaign attribution data. Your Salesforce admin retains full control over which fields and objects are accessible through standard Salesforce field-level security and object permissions.

Step 2: Syncing Accounts, Contacts, and Opportunities

After authentication, Tofu initiates an initial data sync. The platform uses Salesforce Bulk API 2.0 for this first load to minimize API call consumption and avoid hitting rate limits. The sync pulls your Account, Contact, Lead, and Opportunity records along with their associated Campaign Member records. Depending on your org size, this takes anywhere from a few minutes for smaller orgs (under 10,000 accounts) to 45 minutes for enterprise orgs with hundreds of thousands of records.

During setup, you configure field mappings that tell Tofu which Salesforce fields to pull for personalization. The platform provides a default mapping for standard fields:

• Account fields: Name, Industry, NumberOfEmployees, AnnualRevenue, BillingCity, BillingState, BillingCountry, Website, Description, Type, and OwnerId
• Contact fields: FirstName, LastName, Title, Department, Email, Phone, LeadSource, AccountId, and OwnerId
• Opportunity fields: Name, StageName, Amount, CloseDate, Probability, Type, LeadSource, and associated AccountId
• Lead fields: FirstName, LastName, Company, Title, LeadSource, Status, and any lead score fields

Custom field mapping is where the integration becomes especially powerful. If your Salesforce org includes custom fields such as a Technology Stack picklist, an ICP Tier score, a Product Interest multi-select, or data from enrichment tools like ZoomInfo or Clearbit, you can map those fields in the Field Mapping configuration screen. These mapped fields then become available as personalization variables in Tofu campaign briefs. This means the data enrichment, scoring, and segmentation work you have already done in Salesforce directly informs the AI-generated content without any additional manual effort.

Step 3: Configuring Campaign Triggers

Campaign triggers define when Tofu should automatically generate or update content based on changes happening in Salesforce. This is where the integration shifts from a passive data sync into an active content automation engine. Navigate to Campaigns → Triggers in your Tofu workspace to set these up.

The most common Salesforce-based triggers include:

• Opportunity stage change: When an opportunity moves to a specific stage (for example, from "Discovery" to "Proposal"), trigger the generation of deal-stage-appropriate collateral such as a personalized business case, competitive comparison, or ROI calculator
• Account field update: When an account's ICP tier, industry classification, or enrichment data changes, trigger the regeneration of account-specific content to reflect the updated profile
• Campaign membership: When a contact or lead is added to a specific Salesforce Campaign (for example, "Q3 ABM Tier 1"), trigger a full suite of personalized assets for that account
• Lead status change: When a lead moves from "Marketing Qualified" to "Sales Accepted," trigger the generation of sales-ready collateral that the assigned rep can use in outreach
• Task completion: When a sales rep logs a specific activity type (such as "Discovery Call Completed"), trigger the generation of follow-up content tailored to what was discussed
• Custom object change: For orgs with custom objects representing product usage, support interactions, or partner data, trigger content generation based on changes to those records

Each trigger is configured with a campaign brief template (the instructions Tofu's AI uses to generate content), the asset types to produce, and the delivery destinations in Salesforce. Triggers support two modes: fully automated, where content is generated and delivered without human review, and semi-automated, where generated content is queued for approval before being pushed to Salesforce. Most organizations begin with the semi-automated mode for the first two to four weeks, then transition to fully automated once the team is confident in the content quality. Triggers also support conditions and filters, so you can limit a trigger to specific record types, account tiers, or opportunity amounts to avoid generating content for every minor pipeline change.

Step 4: Configuring Content Delivery

Content delivery configuration determines how Tofu-generated assets appear inside Salesforce and how they are accessible to your sales and marketing teams. There are several delivery methods, and you can use different methods for different asset types:

• Custom field links: Tofu writes personalized content URLs to custom fields on Account, Contact, or Opportunity records. Sales reps see a direct link to the personalized landing page, one-pager, or microsite for that specific account. This is the most common delivery method because it puts content exactly where reps already look.
• Salesforce Files: Generated PDFs, one-pagers, and document-format assets are uploaded to Salesforce Files and attached to the relevant Account or Opportunity record. This keeps collateral organized within the Salesforce content library and respects your org's sharing and visibility rules.
• Activity logging: For each content generation and delivery event, Tofu creates an Activity record on the associated contact or lead, providing a timestamped log of what content was generated and delivered. This gives sales managers visibility into what marketing has provided for each account.
• Task creation: When high-value content is generated (or when a prospect engages with personalized content), Tofu can create a Task assigned to the account or opportunity owner, prompting them to follow up. Tasks include the content link and a brief description of the engagement.
• Chatter posts: For organizations that use Salesforce Chatter, Tofu can post to the Account or Opportunity Chatter feed when new content is available, notifying the entire account team rather than just the owner.
• Campaign member updates: Tofu updates Campaign Member Status to reflect content delivery and engagement milestones, feeding your Salesforce campaign influence and attribution reports.

Asset naming follows a configurable convention. The default format is [Campaign Name] - [Account Name] - [Asset Type] - [Date], which you can customize in the delivery settings. For organizations managing hundreds of generated assets across multiple campaigns, consistent naming is critical for searchability and organization within Salesforce reports and list views.

Use Cases

The following use cases represent the highest-impact workflows that the Tofu + Salesforce integration enables. Each describes a specific scenario, the Salesforce trigger, the content generated, and the business outcome.

Deal-Stage Collateral Generation

When an opportunity moves from one stage to the next, the type of content a buyer needs changes fundamentally. Early-stage opportunities need educational content that establishes the problem space. Mid-stage opportunities need solution comparisons, technical validation, and social proof. Late-stage opportunities need business cases, ROI projections, and procurement-ready documentation. The Tofu + Salesforce integration triggers content generation automatically at each stage transition. When an opportunity moves to "Evaluation," Tofu generates a personalized competitive comparison that references the prospect's industry, company size, and known tech stack. When it moves to "Negotiation," Tofu produces a customized ROI calculator and business case document. Sales reps find the new collateral as a link on the Opportunity record within minutes of the stage change, eliminating the typical two-to-five-day lag of requesting custom content from marketing.

Account-Specific Landing Pages

For ABM programs targeting named accounts, generic landing pages underperform compared to pages that reference the prospect's company, industry, and specific challenges. The Tofu + Salesforce integration enables marketing teams to generate account-specific landing pages at scale by pulling Account record data (industry, size, description, technology stack) from Salesforce and using it to personalize every element of the page, from the headline and hero copy to the case studies featured and the CTA language. When a new account is added to a target Campaign in Salesforce, Tofu automatically generates a personalized landing page and writes the URL back to a custom field on the Account record. Sales reps can share that URL directly with prospects, and marketing can use it in outbound email campaigns. Engagement data from page visits flows back to Salesforce as Activities, giving the account team real-time visibility into prospect interest.

Opportunity-Triggered Email Sequences

Email sequences that reference a prospect's specific deal context perform significantly better than generic nurture emails. The Tofu + Salesforce integration allows marketing teams to generate personalized email sequence content triggered by opportunity creation or stage changes. When a new opportunity is created for a target account, Tofu generates a multi-touch email sequence with subject lines, body copy, and CTAs personalized to the contact's role, the account's industry, and the opportunity's product interest. The generated email content can be pushed to Pardot or Marketing Cloud for automated sending, or delivered as templates that sales reps send through Salesforce's native email functionality or sales engagement tools like Outreach or Salesloft. Each email in the sequence references the previous touchpoint, creating a coherent narrative rather than a collection of disconnected messages.

Campaign Attribution in Salesforce

One of the most valuable aspects of the Salesforce integration is the ability to track Tofu-generated content performance within Salesforce's native campaign attribution framework. When Tofu generates and delivers content for a campaign, it creates or updates Campaign Member records to track who received what content. As prospects engage with personalized assets, Tofu updates Campaign Member Status to reflect engagement milestones such as "Content Delivered," "Content Viewed," "CTA Clicked," and "Asset Downloaded." These status changes feed directly into Salesforce Campaign Influence reports, allowing marketing leadership to measure which Tofu-generated content contributed to pipeline creation and closed revenue. This closed-loop attribution eliminates the black box problem that many teams face when trying to measure the ROI of personalized content programs.

What Syncs and What Does Not

Transparency about data sync boundaries matters for security reviews, compliance audits, and setting accurate expectations. Here is an honest accounting of what the integration handles and what falls outside its scope.

What syncs from Salesforce to Tofu:

• Standard Account, Contact, Lead, and Opportunity field data (as configured in field mapping)
• Campaign and Campaign Member records (name, status, member lists)
• Custom object data for objects explicitly configured in the integration settings
• Record ownership information (used for task assignment and notification routing)
• Picklist values and record type metadata (used for accurate field rendering in personalization)
• Account hierarchy relationships (parent-child account structures)

What syncs from Tofu to Salesforce:

• Content asset URLs written to Tofu-namespaced custom fields
• Engagement Activity records (logged on contact, lead, or account timelines)
• Campaign Member Status updates for content delivery and engagement tracking
• Tasks assigned to record owners for follow-up on high-engagement events
• Files uploaded to Salesforce Files and attached to relevant records
• Chatter posts (if enabled) announcing new content availability

What does not sync:

• Salesforce org configuration, metadata, or automation rules (Flows, Process Builder, Apex, Validation Rules)
• User records, permission sets, profiles, or roles
• Case or Service Cloud data (the integration focuses on sales and marketing objects)
• Salesforce Knowledge articles or community content
• Historical Activity records older than the integration activation date (only net-new activities are created)
• Attachments or files already stored in Salesforce (Tofu reads record data, not existing file attachments)
• Formula field calculated values in real-time (formula fields are read at sync time, not dynamically recalculated)
• Encrypted field data in Salesforce Shield environments (encrypted fields return masked values unless decryption is explicitly configured)

On the technical side, the integration respects Salesforce API limits. Tofu monitors your org's daily API call allocation and throttles sync frequency if consumption approaches 80 percent of the limit. For Enterprise Edition orgs, the default API limit is typically more than sufficient. For Professional Edition orgs with lower API limits, Tofu can be configured to use scheduled batch syncs instead of real-time streaming to conserve API calls. The integration also respects Salesforce field-level security: if a field is not visible to the connected user's profile, Tofu will not be able to read or write to that field, regardless of the integration configuration.

Salesforce + Tofu + Pardot or Marketing Cloud

Many Salesforce customers also use Salesforce's own marketing automation tools: Pardot (now called Marketing Cloud Account Engagement) for B2B marketing automation, or Marketing Cloud (formerly ExactTarget) for enterprise-scale multi-channel marketing. A natural question is how Tofu fits alongside these tools rather than replacing them.

The short answer is that Tofu is a content generation engine, not a marketing automation platform. Pardot and Marketing Cloud are execution engines: they send emails, manage nurture tracks, score leads, and orchestrate multi-step campaigns. Tofu generates the personalized content that those platforms deliver. In practice, this means Tofu and Pardot or Marketing Cloud are complementary, not competitive. Tofu generates the emails, and Pardot sends them. Tofu creates the landing page content, and Marketing Cloud hosts or delivers it. Tofu produces the one-pagers, and Pardot's automation rules determine when and to whom those one-pagers are distributed.

Here is how a typical Salesforce + Tofu + Pardot workflow looks in practice:

• Step 1: Salesforce holds the account and opportunity data. A new account is added to a target Campaign in Salesforce.
• Step 2: Tofu detects the Campaign membership change, pulls the account data from Salesforce, and generates a complete asset suite: personalized emails, a landing page, a one-pager, and ad copy.
• Step 3: Tofu pushes the generated email HTML to Pardot as email templates. The landing page content is either hosted on Tofu's domain with Salesforce tracking or pushed to Marketing Cloud's content builder.
• Step 4: Pardot's Engagement Studio or Marketing Cloud's Journey Builder handles the sending logic, timing, A/B testing, and follow-up sequences using the Tofu-generated content.
• Step 5: Engagement data from both Pardot (email opens, clicks) and Tofu (landing page visits, content downloads) flows back to Salesforce Campaign Member records for unified attribution.

For Marketing Cloud customers specifically, Tofu integrates through Salesforce's Marketing Cloud Connect, which bridges CRM data with the marketing execution layer. Tofu-generated content blocks can be pushed to Marketing Cloud Content Builder as reusable content areas, then assembled into Marketing Cloud emails and landing pages using the platform's native drag-and-drop tools. This approach preserves Marketing Cloud's sophisticated sending infrastructure, deliverability management, and compliance features while dramatically accelerating the content creation step that typically bottlenecks campaign launch timelines.

The key distinction is this: Pardot and Marketing Cloud answer the question "when, how, and to whom should we send this content." Tofu answers the question "what should the content say for each specific account and buyer." Teams that use both tools together report that their campaign launch time drops from weeks to days because the content creation step, which is typically the longest phase in any campaign workflow, is reduced from a manual process to an AI-assisted one that produces dozens or hundreds of personalized variations from a single brief.

Frequently Asked Questions