Brink + Monitor ERP
Everything you need to connect Brink and Monitor ERP: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- Varies by project
Prepare Brink
- Confirm the exact product and environment
- Let Junipeer confirm the auth pattern
- Create or receive the technical credentials
- Add the credentials in Junipeer
- Verify in a non-production environment first
- 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
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
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 Brink (5)
| Setting | What it controls | Key |
|---|---|---|
| API Key | Enter the API key for your Brink account. | brink_api_key |
| Environment | Enter the name of your Brink environment – the part of the API address that identifies your environment. | brink_environment_name |
| Exclude Orders created before this date | Enter a date. Orders in Brink created before this date are not synced. | stdintegration_filter_brink_order_created_date |
| Oauth2 Client ID | Enter the OAuth2 client ID for your Brink account. | brink_oauth2_client_id |
| Oauth2 Client Secret | Enter the OAuth2 client secret for your Brink account. | brink_oauth2_client_secret |
Settings 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 |
Did this page help you?