Connect the systems you already use — without custom integration code
Your team runs refunds in Stripe, updates in the ERP, and notifications in Slack. Plugins bring those actions into the case — with role checks, approval steps, and an audit trail — so you do not build a custom integration for every system.
Four steps. One case.
When an operator opens a case, the plugin sees the case type, metadata, and current state. It decides which actions are relevant — and hides the rest.
The operator sees the available actions inside the case. They choose one — like "issue refund" or "update vendor record" — and confirm the details.
The plugin sends the request to Stripe, your ERP, Slack, or any internal API. Role checks, approval steps, and permissions are enforced before the action fires.
The response from the external system — success, failure, confirmation details — writes back to the case timeline automatically. The audit trail stays complete.
Stop building approval and audit infrastructure into every integration
Without plugins, every new system connection means building custom code for role checks, approval steps, error handling, and audit logging. That is weeks of work per integration — work that compounds as the team adds more systems. Plugins move that infrastructure into Latch so the team writes the action logic once and gets permissions, approvals, and audit trails for free.
Permissions carry over
Role checks and approval steps apply to every plugin action automatically. The team does not rebuild that logic for each system.
Every action is recorded
The request, the response, and any failures write back to the case timeline. No separate logging infrastructure needed.
Start with one. Add more later.
Connect Stripe this week. Add the ERP next month. Each plugin is independent — adding a new one does not require changes to the existing ones.
What teams connect first
Most teams start with one plugin for the system that creates the most manual work. These are the most common starting points.
A customer requests a refund above the auto-approve threshold. The operator reviews the case, a second reviewer approves, and the Stripe plugin processes the refund — all from one screen.
A vendor bank-detail change arrives. The plugin surfaces the "update vendor record" action only after the case passes the required review steps.
After a case completes, a plugin posts the outcome to a Slack channel — so the team stays informed without checking the case manually.
An internal tool handles account suspensions, entitlement changes, or config updates. A plugin wraps that API call with role checks and an audit trail.
Questions about how plugins work
Common questions about connecting external systems to Latch through plugins.
How hard is it to build a plugin?
The integration is small by design. A plugin lists the actions available for a case, then runs one when the operator chooses it. TypeScript and Go SDKs handle the contract, so most plugins are tens of lines of code, not hundreds.
Do plugins replace existing integrations?
No. Plugins wrap the call to your external system with permissions, approval steps, and an audit trail. The external system stays where it is. The plugin adds the control layer around it.
What happens when a plugin fails?
Failure becomes part of the case history. The team can see that the action was tried, what came back, and why the expected result did not happen. Nothing is silently lost.
Can I connect systems that do not have a public API?
If the system has any programmatic interface — REST, GraphQL, gRPC, a CLI, or even a database — a plugin can wrap it. The SDK is flexible about transport.
How do plugins interact with approval steps?
Approval steps and plugins work together. A plugin action can require approval before it runs — including two-person review. The approval gate sits between the operator choosing the action and the action actually executing.
Pick one external system and see how it connects
Bring the system your team uses most — Stripe, an ERP, Slack, an internal API — and we will walk through how a plugin wraps it with approval steps and an audit trail.