Build your own integration
ship it to every Revo customer

The Developer Console is a dedicated workspace for every integration your team builds. Register a new application, set its marketplace profile (name, icon, category, description, support contact), generate and rotate client credentials, declare triggers and actions, configure auth and rate limits, manage marketplace publishing, and monitor usage. Every piece is managed from one place, and every change is captured in a version history so reverting a misconfiguration is one click.

Triggers and actions are declared with JSON schema documents that describe the shape of the data they produce or consume. The schema lists every field, marks which are required and which optional, specifies the type of each (string, number, boolean, object, array), and includes descriptions the platform renders as inline help in the workflow editor. The same schema validates runtime calls, generates documentation, and drives the field mapping experience in the editor.

The auth flow is configured in the Developer Console rather than written from scratch in your codebase. Pick the method your service supports, declare the scopes you need, set the redirect path, and provide the connection metadata. When an end user installs your integration, the platform walks them through the secure connection using your configuration, stores the credentials encrypted, refreshes them automatically on your behalf, and handles revocation cleanly when the user disconnects.

Rate limits can be configured at several levels and combined to express the exact protection your service needs. Calls per second prevents tight loops from overwhelming an endpoint, calls per minute smooths out medium term spikes, and calls per day caps overall usage. Optional per user limits ensure no single customer consumes disproportionate capacity. The platform enforces every limit on every workflow that uses your integration, and limits can be adjusted as your service capacity grows.

The software development kit ships in every popular language a typical engineering team uses TypeScript and JavaScript for Node.js backends, Python for data and machine learning teams, Go for service oriented architectures, Ruby for Rails, PHP for web stacks, and Java for enterprise environments. Each library wraps the same set of capabilities behind native idioms, with type safety, tooling support, and inline documentation that matches what developers expect from a first class library.

Marketplace submission is reviewed across three areas: documentation completeness, schema correctness, and basic quality. The team checks that your trigger and action descriptions are clear, your schema validates against sample payloads, your auth flow works end to end, your rate limits are reasonable, and your profile is complete (icon, description, category, support contact). Most submissions clear within a few business days, with feedback on anything that needs addressing.