Authorise the source
Configure Agent inside the organisation’s network and allow only the required server and operations. The connection uses the permitted resource rather than opening access to the entire network.
Illustrative use case
Show partners current stock availability
Send selected stock information to a dealer portal or partner app. Data Bridge reads the approved data from your internal system and makes it available through an API, an address for automatic data exchange. Partners do not need direct access to your full database.
Local SQL databaseUBC Data Bridge AgentERPREST API
HOW THE WORKFLOW RUNS
Local SQL databaseUBC Data Bridge AgentERPREST API
01Authorise the source
02Prepare availability
03Define the API contract
04Connect the portal
THE CHALLENGE
What slows the work down
Partners need stock by warehouse without full accounting-database access. Shared files become outdated, and different availability calculations produce inconsistent answers. The integration needs a defined dataset, freshness requirements and a clear retrieval interface.
Distributors, sales leaders, partner-portal owners and IT teams.A PRACTICAL EXAMPLE
Illustrative scenario: a dealer portal requests available products for a category and warehouse. Data Bridge reads an internal source through Agent, applies the agreed reservation rule and exposes a prepared result through a controlled data endpoint.
HOW THE WORKFLOW RUNS
From the first step to the right action.
Prepare availability
Read balances, map products and warehouses, and apply the agreed reservation calculation. Exclude internal fields that the external application should not receive.
Define the API contract
Add a data-output endpoint, choose its format and configure selection parameters. Set API-client permissions and the maximum age of the prepared result.
Connect the portal
Provide the integrator with generated endpoint documentation. Check warehouse queries, empty results and the portal’s response when the data exceeds the allowed freshness limit.
VALUE FOR THE TEAM
Make the work repeatable.
- Partner applications receive prepared business data without direct access to the whole ERP environment.
- A single maintained workflow applies the availability calculation consistently whenever the data is prepared.
- A defined API contract gives the data owner and portal developer a shared integration specification.
Keep control of the result.
- Limit Agent resources, source permissions and API-client access to what this particular scenario requires.
- Define refresh frequency, maximum result age and a clear portal response when the request cannot be fulfilled.
- Keep the endpoint authenticated unless public access is deliberate, and verify the fields and products exposed.
THE WORKFLOW OUTCOME
The dealer portal reads a consistent stock dataset through a defined API, while access to the internal database remains limited to the configured integration route.
Capabilities behind this workflowFROM IDEA TO WORKING FLOW
Bring your challenge. See a way forward.
Sources, rules and outcomes — let’s build the conversation around your workflow.