Overview
Euler integrates with Salesforce using OAuth 2.0 authentication. Once authenticated, Euler inherits the user’s permissions.
This guide explains how Euler interacts with key Salesforce objects, what data is read and written, and how users can configure their integration.
How Euler Reads Data from Salesforce
Euler primarily reads from three main Salesforce objects:
Partner Object (Usually the Account Object)
Partner Contacts
Opportunities
1. Partner Object (Account or Custom Object)
Euler identifies partner records in Salesforce. For most organizations, partners are stored in the Account object, but some companies use a custom object for partners.
If using the Account object, Euler looks for:
A record type ID that identifies partner accounts, or
A dropdown field (e.g.,
Type = Partner)
Fields that Euler reads from the Partner object:
Partner Name
CRM ID of the Partner (Account ID)
Created Date
Last Modified Date
This information is mapped to the Partner object in Euler.
2. Partner Contacts
Euler reads partner contacts linked to the Partner object and ensures they are correctly mapped to the associated partner using the related Account ID.
Fields that Euler reads from the Partner Contact object:
First Name
Last Name
Salesforce Contact ID
Email Address
Job Title
Created Date
Last Modified Date
Euler automatically relates these contacts back to the Partner object in its system.
3. Opportunity Object
Euler reads opportunities and links them to partners.
Key fields from the Opportunity object:
Billing ID (if available)
Partner Lookup Field (how the opportunity is associated with a partner)
Opportunity Name
Salesforce Opportunity ID
Close Date
Amount
Stage Name
Last Stage Change Date
Created Date
Last Modified Date
If a company tracks billing data in Salesforce, Euler can connect to their custom billing objects to pull out additional billing details linked to an opportunity.
Euler Forms: Writing Data to Salesforce
Euler Forms allow users to map form responses to Salesforce fields, making the writeback process completely customizable.
Each question in a form can be mapped to a Salesforce field.
Users can choose which Salesforce object to write data to.
Forms support add-ins (extra data fields that aren’t explicitly asked in the form).
Example: Writing Back Partner Data
If a customer is creating a new partner in Euler, they might want to ensure that the partner is classified correctly in Salesforce.
Since "Partner Type = Partner" isn't a question in the form, Euler allows customers to set default values using add-ins.
Authentication & Security
Euler authenticates via OAuth 2.0.
Euler inherits the permissions of the authenticated user.
Summary
Euler connects to Salesforce via OAuth 2.0 authentication.
Euler reads data from three main objects: Partner (Account or Custom), Partner Contacts, and Opportunities.
Euler writes data back through Forms, allowing customizable mappings to Salesforce objects and fields.
Additional fields can be written using Add-Ins in Euler Forms.