Connect information to defined work.
Bring records and events from the services you built into the Context Layer, and send reviewed outputs back to them.
- reads
- moves
- publishes
- Status
- Open
- Batch
- BR-0412
- Reviewed values
- BR-0412 feed timessent
- Feed 3
- 11:40, planned 09:00
- Margin note
- Feed 3 added late
What the connection makes available.
Plan the connection around the work.
Review what the connection reads, the information your team needs, and the access the job requires.
| Kind | Enterprise systems |
|---|---|
| State | Available |
| Does | reads, publishes |
| Directory | Connectors directory |
Identify the source and the people responsible.
- 01The interface to discussIdentify the API or webhook and the information the operational job requires.
- 02The technical ownerBring the team responsible for the interface, access, and operating constraints.
- 03The intended interactionDescribe what to read, the events to receive and the reviewed outputs to send.
The information available through this connection.
Use this information to build operational context, with pointers to its original sources.
- 01
Records
DV-0088 and the batch it names
- 02
Resources
Deviations, batches and lots
- 03
Endpoints
The ones your OpenAPI describes
- 04
Payloads
JSON, mapped to the Ontology
- 05
Events
A deviation raised or updated
- 06
Attachments
The files a record carries
- 07
Webhooks
Signed, and checked on arrival
- 08
Identifiers
DV-0088, BR-0412, lot 2231-B
Questions about REST API and webhooks.
Discuss the information you need and how your team will use it.
Turn time spent finding information into time spent moving forward.
Bring the job you want to move forward and the records you'd like connected. Thirty minutes on how Katalyze would do the work, and where your experts come in.
Or, just a quick chat to run through the product, your call.
