Skip to main content
Connectors let Ingestly interact with external services on your behalf. Once a connector is set up, pipeline nodes such as the HTTP action and callback output can make authenticated requests through it without exposing credentials in the pipeline configuration. A connector is an identity (a name, a type, and an authentication method) with a separate credential profile for each pipeline environment. Each connector has a Development profile and a Production profile, each with its own status and encrypted credentials. This keeps building-and-testing credentials separate from the credentials used by live Production pipelines. See pipeline environments for details.

​
Connector catalog

Open Settings and select Connectors, then click New Connector to browse the catalog. Ingestly offers three connector types:

​
Creating a connector

  1. Click New Connector and pick a type from the catalog.
  2. Read the Setup instructions shown with the form. Each type lists the prerequisites you need on the external service (for example registering an app, choosing scopes, or copying an identifier into the form).
  3. Give the connector a name.
  4. Configure the Development credentials. This profile is required and is used while you build and test the connector.
  5. Optionally configure the Production credentials now, or add them later. Production credentials are used when a pipeline runs in Production.
  6. Save the connector.
Production credentials are optional at creation. You can create a connector with only its Development profile connected and add Production later from the connector’s edit dialog. Connect the Production profile before you copy a pipeline that uses it into Production.

​
OAuth connectors (Business Central, QuickBooks Online)

For an OAuth connector, click Connect to start the OAuth flow for that environment. You sign in on the external service’s consent screen and grant the requested permissions, then you are redirected back to Ingestly when authorization completes. Business Central connectors require two extra fields for each environment:
  • Environment: the Business Central environment name (for example production). Use 1 to 50 characters made up of letters, digits, dots, underscores, or hyphens.
  • Company ID: the company GUID. It is required and must be a valid GUID.
Use Save settings in the profile to persist the Environment and Company ID without re-running the OAuth flow.

​
API Key connectors

The API Key connector is not an OAuth integration. Instead you supply one or more header credentials and a base URL:
  • Header rows: one or more Header name and Header value pairs sent with every outbound request (for example Authorization: Bearer ... or X-Api-Key: ...).
  • Base URL: the host outbound requests are restricted to.
Click Connect to save and validate the profile.

​
Managing connectors

The connectors list shows a Name column, a Type column, and two status columns: Development and Production. Each status column shows the profile’s status for that environment, or Not set when that environment has no profile configured yet. Each row has two actions:
  • Edit: open the connector’s edit dialog. The dialog shows both environment profiles (Development and Production) side by side so you can configure, test, or rotate either one.
  • Delete: permanently remove the connector.

​
Per-environment profile actions

Test, disconnect, and credential rotation are configured separately for each environment inside the edit dialog. Each profile offers:
  • Connect: shown when the profile is not connected. Enter the credentials and connect that environment.
  • Test: verify a connected profile is still authorized and healthy.
  • Disconnect: revoke that environment’s access while keeping the connector entry.
  • Rotate credentials: replace a connected profile’s credentials without re-authorizing from scratch.
There is no standalone Rotate Credentials dialog. Rotation lives in each environment profile inside the connector’s edit dialog, alongside Test and Disconnect.

​
Connector status

Each environment profile reports one of these statuses:
You cannot delete a connector that is referenced by a pipeline. Remove the connector from any pipeline that uses it first, then delete it.

​
Permissions

Managing connectors requires the Account.Connector permission. Among the built-in roles only Admins have it, but you can grant it to a custom role. See roles and permissions for details.