Build a Cendryva Connector
Use this article to understand the conceptual development process for a new connector.
What the Framework Provides
The Cendryva connector development framework provides connector definitions, configuration validation, connection testing, record retrieval, lifecycle metadata, and testing utilities.
Development Process
- Define the provider and connector identifier.
- Define required configuration fields.
- Validate all configuration.
- Implement connection testing.
- Retrieve only supported records.
- Normalize records into Cendryva-compatible structures.
- Preserve source lineage and timestamps.
- Handle pagination, timeouts, rate limits, and provider errors.
- Add automated tests.
- Complete security and product review before making the connector available.
Distribution
Public marketplace publishing and partner commercialization are planned capabilities. Contact Cendryva to arrange access to development tooling and the review process.
Design Notes
Treat provider errors as data: distinguish authentication failure, rate limiting, transient timeouts, and genuinely empty results, because each implies a different operator response.
Normalization is where most connectors go wrong. Preserve the provider's own timestamps and record identifiers so imported values stay traceable to their source.
Troubleshooting
- Configuration validation passes but the connection test fails.
- Validation checks shape, not authority. Test with the least-privileged credential the connector documents as required.
- Records import but lineage is missing.
- Carry the provider record identifier and timestamps through normalization; without them, rollups cannot preserve lineage.