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
  • How to connect?
  • Authorize your Hubspot
  • Configure your new destination
  • Example of the configured destination
  • Configuring integration for open-source and on-premise versions
  • Using Hubspot and OAuth 2.0
  • Using API integration, Hubspot API, and Private app access tokens

Was this helpful?

Edit on GitHub
  1. Integrations
  2. Library of integrations

Hubspot

PreviousJenkinsNextMicrosoft Azure SQL

Last updated 7 months ago

Was this helpful?

Open-source and On-premise editions of Ylem require separate specific configurations for this integration. See

Integration type: Write

Integration with Hubspot allows you to create tickets there in a real-time streaming mode. Instructions are available in the video or the text below.

How to connect?

So first things first — the authorization.

Authorize your Hubspot

Once consent's given, you will be redirected back to our application, where you can change the name of just a freshly connected Hubspot instance of yours.

Configure your new destination

Now, on the page of new Hubspot destination creation, you can choose your just-connected Hubspot. Now the question is, what are those pipeline IDs, pipeline stage ID, and owner ID? These are the internal IDs in your Hubspot. How to find them?

Pipeline / stage id

First of all navigate yourself to the configuration of pipelines, by clicking that link on the Tickets page.

In there you will find a list of your pipelines and corresponding stages. By clicking </>, it will reveal an ID, that you will need to put in your destination configuration.

Owner id

An owner is the one who creates a ticket. E.g, you could create a special account for just Ylem or use any other natural person account. In order to find the owner id, please go to the ticket properties, find a property "Ticket Owner", and click "Edit". You'll see something like this.

You need to copy a value in the red rectangle.

Example of the configured destination

After you've done all the steps above, your Hubspot configuration in Ylem will look like this. Now you can use it in your pipelines!

Configuring integration for open-source and on-premise versions

If you don't use the cloud version of Ylem but have it installed on your infrastructure under your domain name, you can choose one of the following two ways how to make this integration work.

Using Hubspot and OAuth 2.0

It is the same way how it works in our cloud version. You need to create your own Hubspot Application and integrate your Ylem instance with it so that your users will be able to authorize Ylem to access their Hubspot accounts.

By default you will only need a scope to create tickets:

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_HUBSPOT_OAUTH_CLIENT_ID=%%REPLACE_IT_WITH_THE_CLIENT_ID_OF_YOUR_APP%%
INTEGRATIONS_HUBSPOT_OAUTH_CLIENT_SECRET=%%REPLACE_IT_WITH_THE_CLIENT_SECRET_OF_YOUR_APP%%
INTEGRATIONS_HUBSPOT_AFTER_AUTHORIZATION_REDIRECT_URL=https://%%REPLACE_IT_WITH_THE_DOMAIN_NAME_OF_YOUR_YLEM_INSTANCE%%/hubspot-authorizations/{uuid}/?justConnected

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

Using API integration, Hubspot API, and Private app access tokens

Another way of creating an integration with Hubspot to be able to create tickets directly from Ylem is using its REST API with Private app access tokens.

Step 1. Create your Private app access token

Private app access tokens is a safe alternative to using username and password for authentication with various 3rd-party services like Ylem.

This page contains a detailed explanation of how it can be created:

Step 2. Creating API Integration and sending requests to it from Ylem pipelines

As soon as you have your Private app access token configured, you can use it as an Access Token for POST/GET requests to Hubspot API.

Go to "" and click "Add Hubspot Authorization". You will be redirected to Hubspot's page where you need to give your concern.

Here you can read more about how to manage .

If configured correctly, the process from this point should work exactly as same as .

Check and create a Ylem with it:

Now you can call it directly from the Ylem pipelines with the necessary query parameters and headers using the task.

💡
Hubspot Authorizations
OAuth 2.0 authentication with Hubspot
Hubspot REST API reference
API Integration
API_Call
described above
below
How to integrate Ylem with Hubspot
Private apps
Logo