Skip to content
JunipeerKnowledge Base
EnglishSvenska

Ongoing + Bigquery

Everything you need to connect Ongoing and Bigquery: how to connect, which data moves, which settings there are and what to do when something goes wrong.

  • 1 data flow
  • Connect in about 13 minutes
Start connecting

1. Getting started

Prepare both systems first, then connect them in Junipeer.

  1. about 10 minutes

    Prepare Ongoing

    1. Open the Ongoing API access setup
    2. Create or confirm the dedicated API user
    3. Copy the API username and password
    4. Confirm any client or goods owner identifiers
    5. Paste the credentials into Junipeer
    Full instructions
  2. about 3 minutes

    Prepare Bigquery

    1. Open the BigQuery connector in Junipeer
    2. Click Connect
    3. Sign in with the correct Google account
    4. Review and approve access
    5. Confirm the target project or dataset if prompted
    6. Return to Junipeer and verify the connection
    Full instructions

  3. Connect and test

    Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.

    Getting started with Junipeer

2. How the data flows

What Junipeer can move between the two systems. The arrow shows which way the data goes.

  • Orders
Based on what each connector can fetch and send. You choose which flows to switch on in Junipeer.

3. Settings

The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.

You don't need to read them all

In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.

How the Junipeer MCP works

Settings for Ongoing (2)

SettingWhat it controlsKey
Exclude Orders created before this datePick a date to skip older orders.stdintegration_filter_ongoing_order_created_date
Goods ownerChoose which Ongoing goods owner this integration works with.ongoing_goods_owner_id

Settings for Bigquery (12)

SettingWhat it controlsKey
Customer table nameEnter the name of the table in BigQuery where customers are added.bigquery_customer_table_name
Data SourceEnter the source to set on the data that is sent to BigQuery, so you can see where it came from.bigquery_data_source
Dataset IDEnter the ID of the dataset in BigQuery where Junipeer should create its tables.bigquery_dataset_id
Define Extra Customer FieldsAdd extra fields (columns) to the customer table in BigQuery.bigquery_custom_customer_fields
Define Extra Order FieldsAdd extra fields (columns) to the order table in BigQuery.bigquery_custom_order_fields
Define Extra Order Rows FieldsAdd extra fields (columns) to the order row table in BigQuery.bigquery_custom_order_rows_fields
Include Order RowsDecide whether order rows are included when orders are sent to BigQuery.bigquery_include_order_rows
Include Personal InformationDecide whether personal information , such as names and addresses, is included when orders are sent to BigQuery.bigquery_include_personal_information
Show all 12 settings
SettingWhat it controlsKey
Include Postal Code and CityDecide whether the customer's postal code and city are included when orders are sent to BigQuery.bigquery_include_postal_code
Map Custom Order Rows FieldsFill your extra BigQuery order row fields with data from the order rows.bigquery_map_custom_order_rows
Order table nameEnter the name of the table in BigQuery where orders are added.bigquery_order_table_name
Project IDEnter the ID of your Google Cloud (GCP) project where your BigQuery data lives.bigquery_project_id

Did this page help you?