Connectors and external systems

What connectors do today

Priostack stores connector definitions: you can create, clone, export, import and publish them. But connectors are stored, not executed: no activity chain runs, nothing calls an outbound service, and an inbound connector webhook answers 501 with "received but not yet processed". Connectors cost nothing today.

Export redacts configuration values whose names mark them as secrets. Nothing encrypts a connector configuration at rest, so keep secrets out of it.

Call external systems from a worker

Until connectors run, integrate a system from a job worker. Model a service task with a job type, let your worker activate that job, call the service, map the fields it needs, and complete or fail the job with the result. Keep authentication in the worker and out of the process variables.

Design for duplicate events

External systems can deliver an event more than once. If your own service starts instances from their events, use the event identifier to detect repeats before starting duplicate business work.

Test one integration end to end

1. Start with a minimal representative payload.
2. Inspect the variables the worker receives and the call it makes.
3. Test an invalid payload, a timeout and a duplicate delivery.
4. Confirm that the instance completes, or fails into an incident you can see in operations.

Layer 2 is a Go library you run in your own service, not a hosted Priostack feature.