Cendryva
Join the waitlist

Connect a Supported System

Follow this workflow to bring data from a supported provider into Cendryva and confirm it is trustworthy.

Availability: Plan-dependent7 min readLast reviewed September 3, 2026

Prerequisites

  • Permission to administer integrations
  • A supported provider
  • Required provider credentials or OAuth authority
  • An organization selected in Cendryva
  • Knowledge of the data or events being imported

Instructions

  1. Review the supported connector catalog.
  2. Confirm that the provider is marked Available.
  3. Review the provider's required credentials and permissions.
  4. Create the connection through the application's integration workflow.
  5. Complete provider authorization.
  6. Test the connection.
  7. Configure supported resources and synchronization behavior.
  8. Run an initial synchronization.
  9. Verify source freshness, mapping, ownership, units, and reporting periods.
  10. Monitor failures and reconnect when credentials expire.

Expected Result

The connection tests successfully, an initial synchronization completes, and imported data maps to statistics with correct units, owners, and reporting periods.

Not Everything Is Real Time

Some connectors poll on a schedule, while others receive supported events through webhooks. Do not describe every connector as real-time. Check the synchronization behavior of each connection before promising freshness to reviewers.

Security Guidance

  • Use least-privilege provider credentials.
  • Never place credentials in documentation, screenshots, support messages, or client-side code.
  • Rotate credentials when exposure is suspected.
  • Disconnect integrations that are no longer needed.

Troubleshooting

Authorization completes but the test fails.
Check that the authorizing account holds the provider permissions the connector requires, and that the correct provider account or workspace was selected.
The initial synchronization returns no records.
Confirm the configured resources and date range contain data, and that the credential's scope includes them.
Values arrive but statistics look wrong.
Verify mapping, units, and reporting periods. A correct import with a mismatched period produces a plausible wrong number.
The connection stops working after some time.
Provider credentials and tokens expire or get revoked. Reconnect the integration and review failure notifications.

Related Articles