← All integrations Integrations · Salesforce

Eventtia and Salesforce, mapped to your own fields.

Our webhooks and REST API send Eventtia data to Salesforce, into the objects and fields your org already uses. Build the integration and the workflows your teams need, shaped to your Salesforce model. Your developers can build it, or our team can.

Talk to us about your integration See the mapping
Connection
Webhooks + REST APIStandard and custom objects.
Direction
Eventtia → SalesforceEvent data goes to your org.
Built by
Your team or oursOur build is a scoped, quoted service.
Timeline
1 to 4 weeksA simple webhook setup takes about one week.
Our approach

Built around your Salesforce org.

Each Salesforce org has its own objects, custom fields and rules. So each Eventtia integration is scoped and mapped for that org. When a documented trigger fires in Eventtia, for example a new attendee or an updated registration, the integration receives the webhook and writes to the Salesforce records you choose.

01

Your objects

Contact or Lead, Campaign, Campaign Member, or the custom objects your org uses.

02

Your fields

Standard and custom fields, including the answers to your custom registration questions.

03

Your rules

Consent, duplicates, and which record wins when data differs.

Proposed mapping

What can move from Eventtia to Salesforce.

A proposed mapping to validate for your project. The final mapping depends on your org and on the data each trigger provides.

  1. A new registrationattendee_created
    Contact or Lead, and a Campaign Member on the event's campaign
  2. A registration changeattendee_updated
    Updated Contact or Lead fields, Campaign Member status
  3. A new or updated eventevent_createdevent_updated
    Campaign
  4. A paymentpayment_created
    A record chosen with your finance team
  5. An invoiceevent_invoice_createdevent_invoice_updated
    A record chosen with your finance team
  6. Custom registration questionsattendee data (webhook or API read)
    Standard or custom fields you choose

Data flows from Eventtia to Salesforce. Registration status, session enrollment and on-site attendance are different data, and each is scoped in the project.

Three ways to build it

With n8n, Zapier, or directly.

With n8n

An n8n workflow starts on an Eventtia webhook, can read more data from our API, and writes to Salesforce with n8n's Salesforce node.

Low-code

With Zapier

A Zap sends Eventtia data to Salesforce with Zapier's Salesforce app. Our Zapier app is available on request: our team sets you up.

No code, on request

Directly

Your backend receives the webhook and writes to Salesforce through its API. Use this when you need full control, high volumes or complex rules.

Full control
How a project runs

From scope to live data, in four steps.

  1. Step 01

    Scope

    List the events, objects and fields that matter to your teams, and the rules: consent, duplicates, which record wins.

  2. Step 02

    Map

    Each Eventtia field gets a target in Salesforce.

  3. Step 03

    Build and test

    The integration receives Eventtia webhooks and writes to a Salesforce sandbox first. Your team checks test registrations.

  4. Step 04

    Go live

    Switch to production.

In production

Cartier runs it today.

Each event feeds its own Salesforce campaign.

Cartier links each event to a Salesforce campaign. Attendees go to that campaign, so the attendees of every event are in the CRM Cartier already uses.

Partner since 2022 Read the case study
  1. 01
    Event

    Each event has its Salesforce campaign set in Eventtia.

  2. 02
    Campaign

    Attendees are added to that campaign.

Cartier also uses Salesforce Marketing Cloud with Eventtia.

FAQ

Salesforce integration questions.

Does Eventtia have a native Salesforce connector?

No. Eventtia connects to Salesforce through webhooks and our REST API, mapped to your own objects and fields. This takes more setup than a one-click button, and the result follows your Salesforce model.

Which data can go to Salesforce?

Data from the documented webhook triggers (attendees, events, payments, invoices) and from our REST API. The exact fields and Salesforce targets are defined in your project.

How fast does data arrive?

Webhooks are sent when the trigger fires in Eventtia. The delay in your setup is measured during testing.

Who builds the integration?

Your developers, using our API and webhooks, or our team, as a scoped and quoted project.

How long does it take?

Typically 1 to 4 weeks. A simple webhook setup can be live in one week. A larger scope can take longer, and we agree the timeline when we scope the project.

Is it included in my plan?

Building the integration is a separate service, quoted for your scope.

Can we test before going live?

Our projects are built and tested against a Salesforce sandbox before switching to production.

Tell us how your Salesforce org works.

Share your objects and fields. We will tell you what the integration involves, who should build it, and how long it takes.

Talk to us All integrations