AUTOMATE NOW
  • Connection guide
  • OplaGO
  • HexaSync

Get started with OplaGO on HexaSync

Connect OplaGO to HexaSync with a read-only API key to read leads and contacts, add webhooks for real-time updates, re-authorize, and fix errors.

HexaSync TeamLast updated

This guide helps you connect OplaGO to HexaSync Automation Engine to read lead and contact data from OplaGO. You need to create an API key in OplaGO and set up webhooks so that HexaSync receives changes in real time.

Before you start

  • A Beehexa account to sign in to HexaSync Automation Engine. If you do not have one yet, sign up on the same page.
  • An OplaGO account at go.oplacrm.com. HexaSync only sees the records that this user can see, so use an account that can view all the leads and contacts you need.
  • Permission to open Company settings in OplaGO to add webhooks. If you do not have this permission, ask your OplaGO administrator to do the step that adds the webhooks.

Note: This Connector only reads leads and contacts. HexaSync does not pull orders, invoices or any payment data from OplaGO.

Part 1: Authorize the OplaGO connection on HexaSync

Step 1: Sign in to HexaSync

  1. Go to HexaSync Automation Engine and sign in with your Beehexa account.
  2. Open Templates.

Step 2: Start the OplaGO connection

  1. Open the OplaGo Connector setup page.
  2. On the OplaGO row, select Connect.

If OplaGO was connected before, HexaSync shows the Choose an app to connect to OplaGO screen:

  • To keep using the current API key, keep that Connector App selected and select Continue, then go to Step 5: Add webhooks in OplaGO.
  • To use a different API key, select Use a different app, then select I will enter my OplaGO API key.

Step 3: Create an API key in OplaGO

  1. Open a new tab and sign in to OplaGO with the account you chose.

  2. Select your profile picture in the top right corner, select Personal Settings, then select API Keys & MCP.

  3. Select Create new API key and fill in:

    Field Value
    Key name 
    HexaSync
    Read-only key On
    No expiry On, so that the API key does not expire

  4. Select Create.

  5. Copy the Client_id and Secret key, and save them in a safe place.

Note: OplaGO shows the Secret key only once. If you close the window before you copy it, create a new API key. The Secret key works like a password, so do not share it with anyone.

Step 4: Enter the API key in HexaSync

  1. Go back to HexaSync.
  2. Paste the Client_id into the Client ID field and the Secret key into the Secret Key field, then select Continue.

Step 5: Add webhooks in OplaGO

The next screen gives you Your HexaSync Webhook URL and Your Webhook Secret Key. You use these two values to create webhooks in OplaGO, so that HexaSync receives lead and contact changes in real time.

  1. Copy Your HexaSync Webhook URL and Your Webhook Secret Key, and save them in a safe place.

  2. In OplaGO, open Company settings, select Integration › Webhook, then open the Configurations tab.

  3. Select Add new and fill in:

    Field Value
    Endpoint URL Paste Your HexaSync Webhook URL, including the full path
    Method 
    POST
    Event type Select one event from the table in action 5
    Secret Key Paste Your Webhook Secret Key, with no extra spaces
    Status Turn on Active
    Description 
    HexaSync

  4. Select Save.

  5. Repeat actions 3 and 4 for each of the following events. Each event is a separate webhook, and they all use the same Endpoint URL and Secret Key.

    Data Event type
    Leads Create Lead, Update Lead
    Contacts Create Contact, Update Contact

  6. Go back to HexaSync, scroll to the bottom of the screen and select I have set up the webhooks in OplaGO — continue.

Note:

  • You can still continue if you cannot add the webhooks right away. Without webhooks, the data is still updated every hour. To see the Webhook URL and Webhook Secret Key again, re-authorize by following Part 2 and keep the API key you are using.
  • If your company has renamed objects in OplaGO, the names in the Event type list change too. Select the Create and Update events that match Lead and Contact.

Step 6: Create the OplaGo Connector

  1. When the OplaGO row shows Connected, select Create OplaGo Connector.

  2. Check the suggested Connector name, for example [Acme Corp] OplaGo Connector, edit it if needed, then select Continue.

  3. Creating the Connector takes a few minutes. Stay on the page until HexaSync moves to the Tasks page of the Connector by itself.

Part 2: Re-authorize the OplaGO connection

Re-authorize when HexaSync can no longer pull data with the old API key, for example:

  • The API key has been revoked (Revoke) or has expired in OplaGO.
  • The OplaGO user who owns the API key has left the company or their account has been locked.
  • You want HexaSync to use another user’s API key.

You also use this process to see the Webhook URL and Webhook Secret Key again.

Step 1: Open the Connector Settings

  1. Open Connector Apps and select OplaGo Connector.
  2. Select Settings in the left menu.
  3. In the Connected Apps & Credentials section, select Re-authorize on the OplaGO row.

Cannot use Re-authorize? Only the person who created the Connector App or a person with the Connector App admin role can see this button. Ask one of those people to do it.

Step 2: Choose the API key

  • To keep using the current API key, keep the selection and select Continue.
  • To use a new API key, create the key by following Step 3 in Part 1, select Use a different app, then select I will enter my OplaGO API key. Enter the new Client ID and Secret Key, then select Continue.

Step 3: Check the webhooks

The screen shows Your HexaSync Webhook URL and Your Webhook Secret Key again.

  1. Compare Your Webhook Secret Key with the Secret Key of the webhooks in OplaGO. If they are different, update the Secret Key of each webhook.
  2. If you have not set up the webhooks yet, follow Step 5 in Part 1.
  3. Scroll to the bottom of the screen and select I have set up the webhooks in OplaGO — continue.

Step 4: Confirm the connection

  • HexaSync saves the API key to the Connector App and opens the Tasks page again.
  • In Settings, confirm that the OplaGO row has the status Connected.
  • The next update uses the new API key within one hour. The data pulled before is kept.

Part 3: Check that the connection works

Check the connection details

  1. Open Connector Apps and select the OplaGO Connector App you just created.
  2. Select Settings.
  3. In Connected Apps & Credentials, confirm that the OplaGO row has the status Connected.

Check the data

The Tasks page of the new Connector has two tasks: [OplaGO] Leads and [OplaGO] Contacts.

  • Within one hour, HexaSync pulls leads and contacts for the first time.
  • After that, the data is updated every hour. If you added the webhooks, leads and contacts are updated in real time when they change.
  • Each record keeps all the information OplaGO returns: name, job title, customer name, phone number, email, address, source, status, owner, score, custom fields and creation date.

Note: HexaSync only reads data and does not change anything in OplaGO.

Check the webhooks

  1. In OplaGO, create or edit a test lead.
  2. Open Company settings › Integration › Webhook, then select the Delivery logs tab.
  3. Confirm that the event you just created has the status SENT or PUBLISHED. If the status is FAILED, check the Endpoint URL and Secret Key of the webhook again.

Part 4: Common errors and how to fix them

HexaSync Could Not Connect Your OplaGO API Key

The Client ID or Secret Key is not correct.

  1. Copy them again from OplaGO, and check that you did not paste them into the wrong fields.
  2. Select Back to the API key details and enter them again.

OplaGO Did Not Issue An Access Token

The API key has been revoked or has expired.

  1. Create a new API key in OplaGO by following Step 3 in Part 1.
  2. Select Fix my details and try again, select I will enter my OplaGO API key and enter the new key.

Other errors

Message How to fix it
This API key is already registered to another account Someone else has already connected this API key. Ask them to share it, or create a new API key.
HexaSync Could Not Give You An OplaGO Webhook URL The connection has been saved. Select Continue to go on. Send a screenshot to support@beehexa.com to get the Webhook URL.
The name already exists Choose a different Connector name.
Connector Quota Reached Contact support@beehexa.com to raise the quota.
HexaSync Could Not Link The Credential To Your Profile The API key was saved but is not linked to the Connector yet. Select Go to Manage Credentials and link the key to the Connector, or contact support@beehexa.com.
A webhook in OplaGO reports FAILED Check that the Endpoint URL was pasted in full and that the Secret Key is the same as Your Webhook Secret Key.

For other cases, send a screenshot (with confidential information hidden) to support@beehexa.com.

Part 5: Frequently asked questions

Does HexaSync write or change data in OplaGO?

No. Every call to OplaGO is a read call, so a read-only API key is enough.

What data does HexaSync get from OplaGO?

Only leads and contacts, but it keeps all the fields OplaGO returns for these two types: name, job title, customer name, phone number, email, address, source, status, owner, score, custom fields and creation date.

How is lead and contact data stored?

Exactly as OplaGO returns it, with no changes. HexaSync only sees the records that the OplaGO account you use for the connection can see.

Why does the Connector have no orders and invoices?

This Connector only confirms that the connection to your OplaGO works, so it reads only two basic data types. Orders, invoices and payment data are not pulled.

How many webhooks do I need to add in OplaGO?

You need 4 webhooks: Create Lead, Update Lead, Create Contact and Update Contact. They all use the same Endpoint URL and Secret Key. See how to add them in Step 5.

When do I need to re-authorize the connection?

When the API key is revoked or expires, when the person who owns the key leaves the company, when you want to use another person’s key, or when you need to see the Webhook URL and Webhook Secret Key again. Follow Part 2.