Ylem documentation
  • 🗒️General information
    • Introduction to Ylem
    • Quick start guide
    • Release notes
  • 🔬Open-source edition
    • Installation
    • Usage of Apache Kafka
    • Task processing architecture
    • Configuring integrations with .env variables
  • 💡Integrations
    • Connecting an integration
    • Library of integrations
      • Amazon Redshift
      • Apache Kafka
      • APIs
      • Atlassian Jira
      • AWS Lambda
      • AWS RDS
      • AWS S3
      • ClickHouse
      • ElasticSearch
      • E-mail
      • Google Big Query
      • Google Cloud SQL
      • Google Pub/Sub
      • Google Sheets
      • Immuta
      • Incident.io
      • Jenkins
      • Hubspot
      • Microsoft Azure SQL
      • MySQL
      • OpenAI ChatGPT
      • Opsgenie
      • PostgreSQL
      • PlanetScale
      • RabbitMQ
      • Salesforce
      • Slack
      • Snowflake
      • Tableau
      • Twilio. SMS
      • WhatsApp (through Twilio)
    • Initial demo data source
  • 🚡Pipelines
    • Pipeline management
    • Tasks
      • Aggregator
      • API Call
      • Code
      • Condition
      • External trigger
      • Filter
      • For each
      • GPT
      • Merge
      • Notification
      • Query
      • Pipeline runner
      • Processor
      • Transformer
    • Running and scheduling pipelines
    • Library of templates
    • Environment variables
    • Mathematical functions and operations
    • Formatting of messages
  • 📈Statistics and profiling
    • Statistics of runs
    • Slow tasks
  • 📊Metrics
    • Metric management
    • Using previous values of a metric
  • 💼Use cases, patterns, templates, examples
    • Use cases
    • Messaging patterns
      • Datatype Channel
      • Message Dispatcher
      • Messaging Bridge
      • Message Bus
      • Message Filter
      • Message Router
      • Point-to-Point Channel
      • Publish-Subscribe Channel
      • Pull-Push
    • Functional use cases
      • Streaming from Apache Kafka and messaging queues
      • Streaming from APIs
      • Streaming from databases
      • Data orchestration, transformation and processing
      • Usage of Python and Pandas
      • KPI Monitoring
      • OKRs and custom metrics
      • Data Issues & Incidents
      • Reporting
      • Other functional use cases
    • Industry-specific use cases
      • Finance and Payments
      • E-commerce & Logistics
      • Customer Success
      • Security, Risk, and Anti-Fraud
      • Anti-Money Laundering (AML)
  • 🔌API
    • OAuth clients
    • API Reference
  • 👁️‍🗨️Other resources
    • FAQ
    • Our blog on Medium
Powered by GitBook
On this page
  • Configuring integration for open-source and on-premise versions using OAuth 2.0
  • Step 1. Salesforce Connected App and authorizing Ylem to have access to user's account
  • Step 2. Creating a new integration with Salesforce

Was this helpful?

Edit on GitHub
  1. 💡Integrations
  2. Library of integrations

Salesforce

PreviousRabbitMQNextSlack

Last updated 7 months ago

Was this helpful?

This integration is only available in open-source and on-premise editions. Please contact us, if you want to have Salesforce in the cloud edition for you organization.

Integration type: Write

With Salesforce integration you can stream data and create Salesforce tickets in real-time.

If you need to stream flexible data directly to Salesforce API, consider using API integration instead.

Configuring integration for open-source and on-premise versions using OAuth 2.0

Step 1. Salesforce Connected App and authorizing Ylem to have access to user's account

You need to create your own Salesforce Connected App first and integrate your Ylem instance with it so that your users will be able to authorize Ylem to access their Salesforce account data.

Here you can read more about how to create a connected APP and manage OAuth 2.0 authentication with Salesforce.

Please note, that a Salesforce user must be assigned to the system permissions "API Enabled", and "Apex REST Services"

As soon as the application is created, you will get OAuth 2.0 CLIENT_ID and CLIENT_SECRET that must be placed into the ./backend/integrations/.env file of Ylem together with the redirect URL to your Ylem instance:

INTEGRATIONS_SALESFORCE_OAUTH_CLIENT_ID=%%REPLACE_IT_WITH_THE_CLIENT_ID_OF_YOUR_APP%%
INTEGRATIONS_SALESFORCE_OAUTH_CLIENT_SECRET=%%REPLACE_IT_WITH_THE_CLIENT_SECRET_OF_YOUR_APP%%
INTEGRATIONS_SALESFORCE_AFTER_AUTHORIZATION_REDIRECT_URL=https://%%REPLACE_IT_WITH_THE_DOMAIN_NAME_OF_YOUR_YLEM_INSTANCE%%/salesforce-authorizations/{uuid}/?justConnected

Now you can open https://%%YOUR_YLEM_DOMAIN_NAME%%/salesforce-authorizations and try to authorize Salesforce Integration by clicking on the button "Add Salesforce authorization".

If configured correctly, after the redirection to Salesforce and giving the permissions, you will get back to the same page with the new authorization appeared in the list:

Step 2. Creating a new integration with Salesforce

Now the same aithorization can be used for creating new integrations.