Bringing data in from another system: inbound pipelines
Since release 20261113 a data pipeline can be inbound: it reads another system’s API (for example HubSpot contacts) into staging, each record is checked against the target screen’s rules, and a second person approves and loads them.
Platform › Connectivity › Integration › Data Pipelines.
An inbound pipeline reads another system’s API (for example HubSpot contacts) and brings the records into TRANXACT only after someone has checked and approved them: fetch, staging, check, approve by another person, load.
- Make sure the source system has a connection under Platform › Connectivity › Integration › Connections, with its endpoint and credential stored. Press Test on it.
- On Data Pipelines, press Allow a source host and enter the system’s host name, such as api.hubapi.com. Only hosts on this list can be read, and only over https.
- Create a pipeline with Direction Inbound, or open a template such as TPL-HUBSPOT-CONTACTS and press Use this template. Choose the source connection. Set Source resource (the path, such as /crm/v3/objects/contacts), Record path (such as results), Paging, and Destination resource (the screen the records go into, such as /crm/prospects). In the Field mapping, mark the field that identifies a record as Key.
- Press Test connection to see the first ten records as they would be mapped. Nothing is kept.
- Press Fetch to staging. The records wait on Pipeline Runs; nothing is in your records yet.
- On Platform › Connectivity › Integration › Pipeline Runs, open Staged records, then press Check. Each record is tried against the target screen’s own rules.
- A colleague with the approve permission presses Approve and then Load. The records are created, or updated if they were loaded before, through the target screen with that colleague’s permissions, and each one is audited. Since release 20261114 a checked run waits in My approvals for the owner of the screen it loads into; see Inbound pipelines: who approves, private sources, auto-approve.
- To drop a run, use Reject and then Discard.
Who can
| اجازت | What it allows |
|---|---|
| Inbound Pipelines | Configure sources and allowed hosts |
| Inbound Pipelines: fetch to staging | Fetch a run into staging |
| Inbound Pipelines: approve and load | Approve and load a run |
All three are on Platform › Access & Security › Access › Roles. The person who fetched a run cannot approve or load it.
See also Integrations: request bins refused, webhooks always signed, Set credential and Test.