This guide helps you connect BowNow to HexaSync Automation Engine to sync the lead list from a BowNow tracking code. The Connector App reads all existing leads on the first connection, then updates every hour, or in real time through a webhook if you configure one. The data is used to assess data quality before you connect to another system.
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.
- A BowNow account with permission to open Settings ▸ Configure System for the tracking code you want to connect.
- The Tracking ID and API Key of the same tracking code.
Note: Each tracking code needs its own Connector App. If you need to sync several tracking codes, connect each tracking code separately.
Part 1: Connect BowNow to HexaSync
Step 1: Sign in to HexaSync
- Go to HexaSync Automation Engine.
- Sign in with your Beehexa account.
Step 2: Open the BowNow Connector template
- Open the BowNow Connector setup link.
- On the BowNow card, select Connect.
Step 3: Get the Tracking ID and API Key
- Sign in to BowNow and open Settings ▸ Configure System for the tracking code you want to sync.
- Copy the Tracking ID.
- Copy the API Key next to the Tracking ID.
Both values must belong to the same tracking code. If you take the Tracking ID and API Key from two different tracking codes, BowNow refuses the connection.
Step 4: Enter the BowNow connection details
-
Go back to HexaSync and fill in:
Field Value Tracking ID Paste the Tracking ID you copied Tracking Code Name Enter the tracking code name, for example Acme Corp. HexaSync uses this name to suggest the Connector App name in a later stepAPI Key Paste the API Key you copied -
Select Continue.
Note: HexaSync does not show a saved API Key again. If you reconnect the same tracking code, you need to enter the API Key once more.
Step 5: Configure the webhook in BowNow
HexaSync shows a webhook URL. If you want to receive changes in real time, add this URL to the webhook configuration of the correct tracking code in BowNow. This step is optional: without a webhook, HexaSync still updates the data once every hour.
- Copy the webhook URL on the HexaSync screen.
- In BowNow, open Settings ▸ Configure Webhook for the tracking code you are connecting.
- Create a new webhook, paste the URL into the URL field, and select the events you want to sync.
- Save the configuration in BowNow. You do not need to paste any value back into HexaSync.
- Go back to HexaSync and select Continue.
Step 6: Confirm the BowNow connection
- When the BowNow row shows the Connected status, select Create BowNow Connector.
Reconnecting the same tracking code? HexaSync updates the existing connection and does not create a new one. You must enter the API Key again because HexaSync does not show a saved key again.
Step 7: Create the Connector App
- Check the suggested Name and Description, and edit them if needed.
- Select Continue.
- Keep the page open until HexaSync moves to the Connector App page. Creating the Connector App can take a few minutes.
The new Connector App has the [BowNow] Leads task. Continue by checking the connection status and data as described in Part 3.
Part 2: Re-authorize the BowNow connection
Re-authorize when HexaSync can no longer get leads with the old API Key, for example:
- The API Key of the tracking code was changed in BowNow.
- The [BowNow] Leads task reports an authentication error and gets no more data.
You need the new API Key and the Tracking ID of the tracking code that is already connected. You get them the same way as in Step 3 of Part 1.
Step 1: Open the Connector App settings
- Open Connector Apps and select the BowNow Connector App you want to re-authorize.
- Select Settings in the left menu.
- Under Connected Apps & Credentials, select Re-authorize on the BowNow row. The System key row just below shows the Tracking ID in use.
Cannot use Re-authorize? This action is shown only to the person who created the Connector App or to someone with admin permission on the Connector App. Ask a person with the right permission to do it.
Step 2: Enter the connection details again
HexaSync shows empty fields because it does not show a saved API Key again.
- Enter the current Tracking ID, the Tracking Code Name, and the new API Key.
- Select Continue.
Note: Keep the same Tracking ID. To sync another tracking code, create a new Connector App.
Step 3: Save the webhook URL
The webhook URL screen appears again. The URL is the same as on the first connection.
- If you already created the webhook in BowNow, you do not need to do anything else. If not, follow Step 5 of Part 1.
- Select Continue.
Step 4: Check the result
HexaSync saves the new API Key to the Connector App, then takes you back to the Tasks page.
- In Settings, the BowNow row shows Connected.
- The next update, within one hour, uses the new API Key.
- Leads that were already synced stay unchanged.
Part 3: Check that the connection works
Check the connection details
- Open Connector Apps.
- Select the BowNow Connector App you just created, then open Settings.
- Under Connected Apps & Credentials, confirm that the BowNow row has the Connected status.
- Check that the Connector App has the [BowNow] Leads task.
Check the data
- On the first sync, the Connector App gets all existing leads in the tracking code.
- After that, the data updates every hour if no webhook is configured. If a webhook is configured, changes are updated in real time for the events you selected in BowNow.
- The synced data includes each lead’s full name, email, phone number, company name and details, address, status, tracking group, created date, and updated date.
Note: The Connector App only reads lead data from BowNow. It does not create or edit data in BowNow.
Part 4: Common errors and how to fix them
| Message | How to fix it |
|---|---|
| HexaSync Could Not Connect Your BowNow Tracking Code | Read the description line on the screen to find the cause. Common causes: the Tracking ID or API Key has extra spaces, the two values do not belong to the same tracking code, or the API Key was changed in BowNow. Select Back to installation and enter the details again. |
| BowNow refused the token request: request quota exceeded | The tracking code has used up its API call quota for the day. Wait a while, then connect again. |
| Could not reach https://api.bownow.jp/v1/auth/token | BowNow cannot be reached right now. Try again in a few minutes. |
| The name already exists | Use a different Connector App name. |
| Connector Quota Reached | Contact support@beehexa.com to raise the quota. |
| Couldn’t Start Connector Creation / Connector Creation Failed | Send a screenshot to support@beehexa.com. |
| Connector Creation Is Taking Longer Than Expected | Wait a few more minutes. If the Connector App still does not appear, send the Job ID shown on the screen to support@beehexa.com. |
For other cases, send a screenshot (with confidential information hidden) to support@beehexa.com.
Part 5: Frequently asked questions
Does HexaSync write or edit data in BowNow?
No. The BowNow Connector App only reads lead data in BowNow. It does not create or edit data.
What data does HexaSync get from BowNow?
HexaSync gets lead information: full name, email, phone number, company name and details, address, status, tracking group, created date, and updated date.
Can the Tracking ID and API Key come from two different tracking codes?
No. Both values must belong to the same tracking code. Otherwise, BowNow refuses the connection.
Does each tracking code need its own Connector App?
Yes. Each Connector App connects to one tracking code. To sync another tracking code, create a new Connector App.
Do I have to configure a webhook?
No. The webhook is optional. Without a webhook, HexaSync still updates the data every hour. With a webhook, the data is updated in real time when something changes. See how to add one in Step 5.
When do I need to re-authorize the BowNow connection?
Re-authorize when the API Key changes or the [BowNow] Leads task reports an authentication error and stops receiving data. Follow Part 2.