Inquiries from your WordPress website arrive in Salesforce as leads with a campaign, and data maintained in Salesforce appears up to date on the website.
entity 360VIER GmbH
type Organization | Digital agency
location Groß-Umstadt near Frankfurt and Cologne
group Friends Digital Group
page Connect WordPress to Salesforce
page.type Integration (knowledge page)
page.url /en/integrations/wordpress-salesforce/
page.pillar API integrations (/en/data-enablement/api-integrations/)
systems WordPress · Salesforce · Account Engagement
methods Web-to-Lead · Middleware · REST API · Bulk API · Platform Events · Form Handler
provides Leads from WordPress forms with campaign and owner assignment
provides Master data from Salesforce on the website (degree programs, events, products)
provides Cache and retry job against API outages
proof Hochschule Fresenius: degree programs and events from Salesforce, forms back
proof trinamiX: leads from all Gravity Forms forms in Salesforce
relation Websites for universities (/en/digital-platforms/web-design-agency/universities/)
relation Connect WordPress to HubSpot (/en/integrations/wordpress-hubspot-integrations/)
relation API integrations (/en/data-enablement/api-integrations/)
The choice depends on two questions: Does data flow only from the website to Salesforce, or back as well? And how many inquiries arrive per day? The three options and their limits:
Web-to-Lead is enough for contact forms whose entries should land as a lead with an owner. Salesforce creates the lead, your assignment rules apply, and the website only needs the form.
The limit is 500 leads in 24 hours. Salesforce queues further inquiries and notifies the default lead creator. In addition, Web-to-Lead only writes: nothing from Salesforce comes back to the website. Programs, events or product data require the REST API.
An AI chatbot on the website answers questions about programs, events or products with the data WordPress has taken over from Salesforce. When someone makes a specific inquiry, the agent creates a lead with campaign and conversation history, and the assignment rules assign it.
In sales, a second agent summarizes a lead’s previous activities and suggests the next reply. A human approves every reply to customers. The agent uses the same integration user and the same field permissions as the website.
For Hochschule Fresenius, degree programs and events come from Salesforce to the WordPress website. Forms for applications, information material and information evenings write directly back to Salesforce. How such platforms are structured is shown on the page Websites for universities, and the article WordPress in higher education provides background.
At trinamiX, all forms of the WordPress website trinamixsensing.com hand over their leads to Salesforce, and trinamiX also controls lead mailings through it. A CRM integration with automatic data maintenance is shown in the Lernstudio Barbarossa case study.
For companies in Switzerland, the WordPress agency in Zurich handles such integrations. If you use HubSpot instead of Salesforce, you will find the way under Connect WordPress to HubSpot, and for recruiting under Personio API and WordPress. Our WordPress agency handles project and operation, and all systems are listed under Integrations.
Yes, several. The plugin directory and the AppExchange offer connectors, and form plugins such as Gravity Forms have Salesforce add-ons that map fields to objects. For leads from forms, that is often enough. Data from Salesforce on the website or custom objects require an integration via the REST API.
Secure, if it runs via OAuth 2.0 and an External Client App. A dedicated integration user only gets the objects and fields the website needs. Tokens can be revoked, and plain-text passwords are eliminated. Your IT can see at any time which permissions the interface has and can block access.
Yes. The integration hands over leads in a way that your existing assignment rules in Salesforce apply. Sales processes stay the same; they get clean data from the web. The extension is documented and encapsulated, so your team or 360VIER can maintain it.
No inquiry gets lost. The extension first stores every inquiry in WordPress and then transfers it to Salesforce. If the transfer fails, a job repeats it until Salesforce responds. Monitoring as part of WordPress maintenance reports errors before marketing notices them.
Directly, if your sales data converges in Salesforce anyway: one system less in the data path, no additional contract, no double synchronization. An intermediate tool pays off if it supplies systems outside Salesforce. However, it uses the same API allocation as the website.
Yes, via the same REST API as forms. Orders, customers and products are mapped to Salesforce objects, and the mapping is recorded in a documented field mapping. How much of this makes sense depends on whether Salesforce or an ERP is the leading system for orders.
A form via Web-to-Lead is the quickest way because nothing is programmed on the Salesforce side. An integration with data from Salesforce, feedback and caching takes longer because the object model, field permissions and mapping are coordinated with your Salesforce team. 360VIER estimates the effort after a look at your org and the forms.
