Custom Integrations
Some integrations are available only as managed or custom implementations. They are not exposed as broad self-serve setup until a customer need justifies the product work and the connector has passed launch-readiness checks.
What Custom Means
| Status | Meaning |
|---|---|
| Live | Available through the normal product setup path and tested for the documented use case |
| Managed | Available through Vendo-led setup for selected customers or early users |
| Custom | Built or enabled when a customer asks and the implementation is scoped |
| Coming soon | Planned, but not available for customer use yet |
How Setup Works
- Contact Vendo with the source or destination you need.
- Vendo confirms the required APIs, permissions, expected data, and business use case.
- The team scopes setup, validation checks, caveats, and support expectations.
- Vendo implements or enables the integration for the account.
- The first sync is validated against row counts, timestamps, duplicate checks, and expected fields.
Before Requesting a Custom Integration
Have this ready:
- Platform name and account/workspace URL
- Source or destination direction
- Required data objects or events
- Credential or OAuth permission owner
- Expected warehouse tables or destination objects
- Launch deadline and success criteria
Support Expectations
Managed and custom integrations get high-touch support during setup. They may require manual validation, additional monitoring, and account-specific runbooks. Vendo will not present a custom integration as self-serve until the setup path, docs, credential checks, and operational recovery path are productized.
Last updated on