← 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 ↔ SalesforceWebhooks out, REST API in.
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

Each change reaches Salesforce as a webhook. Your systems can also write back to Eventtia through the REST API. Registration status, check-in and session enrollment are mapped in the project.

Attendance

Sync registrations and attendance to Salesforce.

Registration is only half the story. Your CRM also needs to know who came. Each change in Eventtia sends an attendee_updated webhook, so the record in Salesforce follows the attendee from registration to check-in.

01

Registered

A new registration creates or updates a Contact or Lead, and a Campaign Member on the event's campaign.

02

Checked in

When the attendee is scanned at the entrance, Salesforce shows it: the Campaign Member status, for example Attended.

03

Cancelled or changed

A cancellation, a confirmation, a rejection or a new attendee type updates the same record.

Two-way

Store the Salesforce ID in Eventtia.

On the first sync, Salesforce returns the ID of the record it created. Eventtia stores this ID on the attendee, in a private field that only admins see. Every later update carries the ID, so Salesforce finds the record directly. No search, no duplicates. Your systems can also write back through our REST API: update an attendee, or mark a registration as paid when your finance tool receives the payment.

01

First sync

Salesforce creates the record and returns its ID.

02

Stored in Eventtia

The ID is saved on the attendee, visible to admins only.

03

Every update

Check-ins, cancellations and status changes carry the ID back to Salesforce.

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.

How do I sync event registrations and attendance from Eventtia to Salesforce?

Eventtia sends a webhook for each new registration and each change, including check-in, cancellation and status changes. The integration writes them to Salesforce: a Contact or Lead, a Campaign Member on the event's campaign, and the Campaign Member status, for example Attended.

Is the Eventtia and Salesforce integration two-way?

Yes. Eventtia sends event data to Salesforce through webhooks, and stores the Salesforce record ID on each attendee, so every update matches the right record. Salesforce or your other systems can write back to Eventtia through the REST API, for example to update an attendee or mark a registration as paid.

Can Eventtia store Salesforce record IDs?

Yes. Eventtia stores the Salesforce record ID on the attendee, in a private field visible to admins only. Every later webhook carries it, so Salesforce matches the record directly, with no search and no duplicates.

How does Eventtia connect to Salesforce?

Through Eventtia webhooks and the Eventtia REST API, mapped to your own Salesforce objects and fields, including custom objects. You can build it directly, with n8n, or with Zapier. Eventtia does not use a generic one-click connector, so the integration follows your Salesforce model.

Can one Eventtia webhook cover all our events?

Yes. An Eventtia account webhook covers every event in the account, with no setup per event. In a group account, it can be limited to one entity's events.

Who builds the Eventtia and Salesforce integration, and how long does it take?

Your developers, with the Eventtia API and webhooks, or the Eventtia team, as a scoped and quoted project. It typically takes 1 to 4 weeks. A simple webhook setup can be live in one week.

Which Eventtia data can go to Salesforce?

Registrations, registration changes, check-ins, events, payments and invoices, through the documented Eventtia webhook triggers, plus data from the Eventtia REST API, including answers to custom registration questions. The exact fields and Salesforce targets are defined in your project.

How fast does Eventtia data reach Salesforce?

Eventtia sends each webhook when the trigger fires. The delay in your setup is measured during testing.

Can we test the Eventtia and Salesforce integration before going live?

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

Is the Salesforce integration included in Eventtia plans?

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

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