Connectors

Updated March 24, 2026

Overview

The Connectors page displays the two platforms in your integration and lets you manage the credentials used to connect to each one. Every integration has exactly two connectors — one for each side of the data sync.

You can find this page under Configure > Connectors in the left sidebar.

Connector cards

Each connector is shown as a card with:

  • Platform name and logo — the system this connector links to

  • Manage button — opens the credential management interface

  • Connection dropdown — shows which specific connection/account is in use. Some platforms support multiple connections (e.g., a test environment and a production environment), and you can switch between them here.

  • Status badge — shows the current connection state:

- Connected (green) — credentials are valid and the connection is active - Disconnected — credentials are missing or expired and need to be re-entered

  • Manage Connections button — opens a view where you can add new connections, remove old ones, or update credentials

Setting up credentials

How you connect depends on the platform:

OAuth-based platforms: Click Manage and you will be redirected to the platform's login page to authorize Junipeer. After granting access, you are redirected back and the connector shows as Connected.

API key-based platforms: Click Manage and enter the required credentials — typically an API key, secret, or access token. The specific fields depend on the platform. See your connector-specific getting started guide for step-by-step instructions.

Account-based platforms: Some connectors let you select from a list of available accounts or environments after authenticating.

Multiple connections

Some platforms support connecting multiple accounts. For example, you might have a test environment and a production environment. The connection dropdown lets you switch between them without reconfiguring the entire integration.

To add a new connection:

  1. Click Manage Connections

  2. Click Add Connection (or equivalent)

  3. Enter credentials or complete the OAuth flow

  4. Select the new connection from the dropdown

Re-authenticating

If a connection becomes invalid (e.g., an API key was rotated, or an OAuth token expired), the status badge will change to Disconnected. To fix this:

  1. Click Manage on the affected connector

  2. Re-enter credentials or re-authorize via OAuth

  3. Verify the status returns to Connected

After re-authenticating, your existing settings and flows are preserved — you do not need to reconfigure the integration.

Platform-specific setup

Each platform has its own requirements for creating API credentials or authorizing access. The exact steps vary — some use OAuth, some require API keys, and some need additional configuration in the platform's admin panel.

For step-by-step credential setup instructions, refer to the getting started guide for your specific connector pair on the Knowledge Base homepage.

Tips

  • Always test the connection after entering credentials by running a manual Export One on a single record.

  • If a connector shows as Connected but syncs are failing, the issue may be with permissions rather than the connection itself. Verify that the connected user/API key has all required permissions.

  • Keep API credentials secure. Junipeer encrypts stored credentials, but you should still rotate keys if you suspect they have been compromised.

Was this article helpful?