Monitor ERP + Bigquery
Everything you need to connect Monitor ERP and Bigquery: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 2 data flows
- Connect in about 13 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10 minutes
Prepare Monitor ERP
- Open the Monitor integration / API setup
- Generate or retrieve the API access key
- Confirm the technical integration user if relevant
- Note the correct company or database context
- Enter the values in Junipeer
- about 3 minutes
Prepare Bigquery
- Open the BigQuery connector in Junipeer
- Click Connect
- Sign in with the correct Google account
- Review and approve access
- Confirm the target project or dataset if prompted
- Return to Junipeer and verify the connection
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.
Junipeer - Orders
- Customers
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 worksSettings for Monitor ERP (15)
| Setting | What it controls | Key |
|---|---|---|
| API URL | Enter the address of your Monitor API, for example https://host:8001 . | monitor_api_base_url |
| Company Number | Enter the number of the Monitor company to connect to, for example 001.1 . | monitor_company_number |
| Customer Levels | Choose which kinds of Monitor customers are fetched and sent on. | monitor_customer_levels |
| Default Monitor ERP Warehouse | Choose the Monitor warehouse that is treated as the default when stock is fetched from Monitor. | monitor_default_warehouse_id |
| Exclude Orders created before this date | Choose a date. Orders created before this date are not synced. | stdintegration_filter_monitor_erp_order_created_date |
| Find the Monitor Customer By | Decide how Junipeer finds the Monitor customer an order belongs to. | monitor_order_customer_lookup |
| Language Code | Enter the language code used when connecting to Monitor, for example sv . | monitor_language_code |
| Order Row Type | Choose the row type used for order lines in the Monitor order. | monitor_order_row_type |
Show all 15 settings
| Setting | What it controls | Key |
|---|---|---|
| Order Type | Optional. Choose the Monitor order type given to customer orders created in Monitor. | monitor_order_type_id |
| Password | Enter the password for the Monitor user above. | monitor_password |
| Project | Optional. Choose the Monitor project used on customer orders created in Monitor. | monitor_project_id |
| Sales Price List | Choose the Monitor price list that article prices are taken from. | monitor_article_price_list_id |
| Stock Order | Decide whether customer orders are created as stock orders in Monitor. | monitor_is_stock_order |
| Username | Enter the Monitor username Junipeer should log in with. | monitor_username |
| Warehouse | Optional. Choose the Monitor warehouse used on customer orders created in Monitor. | monitor_warehouse_id |
Settings for Bigquery (12)
| Setting | What it controls | Key |
|---|---|---|
| Customer table name | Enter the name of the table in BigQuery where customers are added. | bigquery_customer_table_name |
| Data Source | Enter the source to set on the data that is sent to BigQuery, so you can see where it came from. | bigquery_data_source |
| Dataset ID | Enter the ID of the dataset in BigQuery where Junipeer should create its tables. | bigquery_dataset_id |
| Define Extra Customer Fields | Add extra fields (columns) to the customer table in BigQuery. | bigquery_custom_customer_fields |
| Define Extra Order Fields | Add extra fields (columns) to the order table in BigQuery. | bigquery_custom_order_fields |
| Define Extra Order Rows Fields | Add extra fields (columns) to the order row table in BigQuery. | bigquery_custom_order_rows_fields |
| Include Order Rows | Decide whether order rows are included when orders are sent to BigQuery. | bigquery_include_order_rows |
| Include Personal Information | Decide whether personal information , such as names and addresses, is included when orders are sent to BigQuery. | bigquery_include_personal_information |
Show all 12 settings
| Setting | What it controls | Key |
|---|---|---|
| Include Postal Code and City | Decide whether the customer's postal code and city are included when orders are sent to BigQuery. | bigquery_include_postal_code |
| Map Custom Order Rows Fields | Fill your extra BigQuery order row fields with data from the order rows. | bigquery_map_custom_order_rows |
| Order table name | Enter the name of the table in BigQuery where orders are added. | bigquery_order_table_name |
| Project ID | Enter the ID of your Google Cloud (GCP) project where your BigQuery data lives. | bigquery_project_id |
Did this page help you?