Operelio
CRM integrations

One webhook connects Zapier, Make or your own code
to HubSpot and Salesforce.

Every folder in Operelio has its own webhook address. Any tool that can post JSON with a secret in its header can send leads to it, Typeform has a signed address of its own, and each lead is cleaned, scored and routed before it reaches HubSpot or Salesforce. Email, files and the API come in the same way, and lists go to Pipedrive too. These are the CRM integration tools Operelio has today, with where each one stops.

See how trails workSee pricing

One webhook, every lead source.

If a tool can send a JSON webhook and add a header, it can send you leads. There's no app to install for each one: copy the folder's webhook address and secret, paste them into the tool, and its leads start arriving.

  1. 1

    Make a secret, then copy both.

    On the folder's Settings tab, under Its webhook, press Make a secret. Copy the Address and the secret, which starts with opw_. The secret is shown once, when it's made.

  2. 2

    Send one lead per call.

    POST one JSON object, using the secret as a Bearer token. Its keys become the lead's columns, and it needs at least an email or a name. You get a 202 once it's stored.

    curl -X POST https://operelio.com/api/webhooks/folders/<folder-id> \
  -H "Authorization: Bearer opw_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: form-48213" \
  -d '{"email": "maya.collins@example.com", "name": "Maya Collins", "company": "Calder Events"}'
  3. 3

    The trail does the rest.

    The trail runs its steps and Scorecard, checks the CRM, routes the lead by your rules, and pushes the ones you let through into HubSpot or Salesforce. For a trail's first 7 days live, each lead waits for you to look at it first.

What can send it
  • Zapier
  • Make
  • Your own code
  • anything that can send JSON with a header
  • One lead per call, up to 64 KB.
  • A repeat with the same Idempotency-Key, or with no key and the same body, is caught for 7 days.
  • Past 60 leads a minute or 1,000 an hour, leads are still taken and gathered into one job every 10 minutes. None is turned away.
  • Get a new secret any time. The old one keeps working for 24 hours while you paste in the new one, or press Stop the old secret now if it leaked.
  • Single leads a month: 1,000 on Starter, 5,000 on Pro, 20,000 on Agency. Not on Free. Past that, each lead uses a job.

Already use Zapier or Make? Add a step that posts to your folder's webhook address: Webhooks by Zapier (POST, Payload Type JSON) or Make's HTTP module (Make a request, application/JSON), with the secret in an Authorization header. Those leads are then cleaned, scored and routed before they reach HubSpot or Salesforce.

Using a form on your own site? It needs no tool in between. Each folder can make a form address, on its Settings tab under Website form. Paste the code it gives you into your page, and each submission becomes a lead, with a column for each field. Posts that look like spam are held and never run.

Using Typeform? It can't send that header, so each folder has a Typeform address of its own, ending in /typeform, and a Typeform secret that starts with opt_. In Typeform, add a webhook to your form with that address, and set its secret to the folder's Typeform secret. Typeform signs each response with it, and a response with the wrong signature is turned away. Email, phone, name and company questions fill those columns, and every other question gets its own column.

What every lead goes through on the way in.

A lead that arrives one at a time and a list that arrives as a file go through the same trail, but not the same checks. Here is what each one gets before anything reaches your CRM.

A single lead (webhook or email)

  • The trail's own steps: cleanup, find and replace, filters, and the Do Not Contact screen if the trail has a Remove suppressed contacts step.
  • The Scorecard, if the trail has one.
  • The CRM check on HubSpot and Salesforce: Already in the CRM, New person at an existing company, or New.
  • Your routing rules.
  • The push. An existing contact is filled in, never overwritten.
  • In a trail's first 7 days live, you look at each lead before it goes.

Single leads skip Verify emails and Company Active Check. Those run on lists.

A list or file (upload, email attachment, or the API)

The same trail steps, Scorecard, CRM check and routing, plus:

  • Nine safety checks that can't be switched off.
  • Whichever of these the trail has:
    • Remove duplicates inside the file.
    • Company Active Check.
    • Verify emails.
    • The CRM Formatter, matched to your CRM's fields.
    • A Bridgeant review of the push.
  • The push. A value your CRM already has is kept unless you let the trail replace it.

What it's for

  • Form and enquiry leads to the right rep.

    Each one is scored and routed by your rules as it arrives, and sent to HubSpot or Salesforce once it passes.

  • Event and webinar lists into the CRM, clean.

    Drop the export in a folder or email it in. With Verify emails and Company Active Check on the trail, bad emails and dead companies come out before the push.

  • Partner and vendor files.

    With a Map sources step, a list in someone else's columns is mapped onto your trail's. A new sender's file waits for you once if a column isn't clear.

Your CRM, kept as it is.

HubSpot integration

This HubSpot CRM integration turns lists and single leads into HubSpot contacts and companies, with the owner your routing rules pick. For a single lead, a score can move the lifecycle stage forward, and if you turn deals on, make a deal for the scores you pick (4 and 5 unless you choose others).

  • A value HubSpot already has is kept unless you let a trail replace it.
  • A single lead only fills in blanks.
Starter and up
HubSpot import template →What a trail pushes to your CRM →

Salesforce integration

This Salesforce CRM integration turns lists and single leads into Leads, or Contacts with their Accounts. You choose which. For a single lead, a score can set the Lead Status on a Lead it creates, and if you turn deals on, an Opportunity is made when you send Contacts with Accounts.

  • If one of your Salesforce duplicate rules matches a record we send, Salesforce refuses it.
Starter and up
Salesforce import template →What a trail pushes to your CRM →

Pipedrive integration: lists, not single leads yet

Lists become people and organizations in Pipedrive.

  • Single leads can't be sent to Pipedrive yet. Leads that arrive one at a time wait in Operelio, and lists still go to Pipedrive.
Starter and up
Pipedrive import template →What a trail pushes to your CRM →

Your own CRM

Describe your CRM's fields as a custom template. Operelio then shapes each file to it over the API, and you load the result with your CRM's own importer. There's no direct push. That covers HubSpot, Salesforce and Pipedrive only.

Custom templates on Starter, the API on ProHow to connect Operelio to a custom CRM →

On HubSpot and Salesforce, each person is checked against the CRM before it's pushed, for a list's rows and single leads alike: Already in the CRM, New person at an existing company, or New. Your routing rules can use the answer, including sending a new person to their company's owner. On a long list, rows the check can't reach in time are marked Not checked. A list of companies isn't checked. People are matched on email address, companies on website or name, so a record already there is updated, not created again.

Each folder is a way in.

Every way in can feed the same trail. Folders start on Starter.

Email: send enquiries or attach files

Each folder has its own address. An email sent to it with no attachment becomes one lead. In a form email, lines like Name: Maya Collins fill the matching columns. Any other email keeps its sender's name and address, and its text goes in a Notes column. Attach a CSV, Excel (.xlsx or .xls), PDF or Word (.docx) file and it lands in the folder. The first table in a PDF or Word file becomes rows, with any later table that carries on from it (the same header, or the same number of columns). Other tables are left out. A filled PDF form becomes one row, each answer a column.

Where it stops
  • Up to 10 files an email.
  • PDFs up to 50 pages. Scanned pages can't be read.
  • Auto-replies, bounces and newsletters are skipped.
  • You can limit which senders a folder accepts.
Starter and upWatched folders →

Upload or drop a file

Put a CSV or Excel file in a folder. Operelio waits until it has been there for 3 minutes, so a file still uploading isn't run half-written, then the trail runs it. Each file gets its own run.

Where it stops
  • Uploads take .csv, .xlsx and .xls. PDF and Word come in by email only.
Free can upload a file to test a trail in the sandbox. Running live starts on Starter.Create a trail →

A trail can also run the files in its folder daily, on weekdays, weekly, or every 6, 8 or 12 hours. When a trail runs →

Build your own

The Operelio API

Upload files, run cleanup, the CRM Formatter and the file tools (deduplicate, find and replace, merge, split and more), and download the results over HTTPS with an API key. The Email Verifier and Company Active Check aren't on the API.

Where it stops

1,000 calls a month on Pro, 5,000 on Agency. Not on Free or Starter.

Pro and upDevelopers →API endpoints →
# Upload a file to your workspace
curl -X POST https://operelio.com/api/v1/uploads \
  -H "Authorization: Bearer op_your_api_key_here" \
  -F "file=@contacts.csv"

Not sure which way in fits?
Start with a trail.

Build one in the sandbox for free, test it on a real file, and add the ways in when it does what you want.

See how trails workSee pricing