Integrations That Write Themselves

Summary

Ramp describes an approach to scaling integrations beyond what engineers can build and maintain by hand. Its agentic system lets customers describe a missing workflow integration, researches the provider’s API, requests credentials through a secure widget, writes and tests ordered API-call “recipes,” and generates a deterministic script that runs the integration after build time. An internal Integration Factory applies the same pattern to first-party connectors, producing evidence for review and opening pull requests; the post says 75 integrations have shipped this way, with work reduced from weeks or months to hours. Security controls include HTTPS and hostname allowlists, private-address rejection, isolated egress, bounded responses, business-scoped immutable recipes, and test credentials rather than customer data. The central design lesson is to use models during research and construction, keep them out of execution, and bound autonomy with verification artifacts.

Takeaways

1. 1

   Customer-created integrations can become first-class integrations, including workflow steps or tools that anyone across the business can use.

2. 2

   The model operates at build time: it researches documentation, writes and tests recipes, and generates a deterministic script that is invoked during later executions.

3. 3

   Factory-generated connectors include endpoint-level requests and responses plus product-level test recordings, allowing reviewers to assess evidence rather than rely only on code inspection.