THE FIELD GUIDE / OPERATIONS

Service credentials & external integrations

Connect approved automation, ticketing and SIEM workflows with scoped identities and durable delivery.

Mr Patchy documentation · 2 min read

Create a limited service identity

Administrators preview effective API and server scope before issuing a credential. Rotation, expiration, revocation and audit attribution apply independently of human accounts. Queueing through an integration respects role, lifecycle, approval and recovery gates.

Retry with the same request identity

A supported mutation accepts an idempotency key bound to the service identity, target set and payload. A matching retry returns the original operation; conflicting reuse receives an explicit error. Review uncertain outcomes before creating a new request.

Deliver traceable events

Use stable event IDs, explicit field mappings, verified destinations and bounded delivery retries. Inspect failures and deduplicate at the receiver. Integration audit data retains useful context while redacting credentials and sensitive evidence.

Go deeper

Open the application reference for capability scope and technical details.

Open View scope in issue #337 ↗

Actual application interface with illustrative documentation data.