Connectors
Install a connector
Connect an external system to SQIP from the web console
A connector moves data between a SQIP topic and another system. You can create and manage connectors from the SQIP web console without installing software on your computer.
Choose a connector
HTTP REST API source
Poll an HTTPS API and publish its JSON response records to a topic.
HTTP REST API sink
Send topic records to an HTTPS API using POST or PUT.
FTPS file source
Read complete files from an FTPS directory into a topic.
PostgreSQL CDC source
Capture inserts, updates, and deletes from selected PostgreSQL tables.
PostgreSQL JDBC sink
Write topic records into a PostgreSQL table.
Before you begin
Prepare the following information:
- An installation name that clearly describes the data flow.
- The tenant, ready cluster, and namespace where the connector will run.
- For a source, the output topic that will receive records.
- For a sink, the input topic that already contains records.
- The address and credentials for the external system.
- Permission to access the selected topic and create connectors.
Warning
Do not place passwords, access tokens, or API keys in URLs, headers, or ordinary text fields. Enter them only in the credential fields provided by SQIP.
Installation steps
Open Connectors
Sign in to SQIP and open Connectors.
Start a new connector
Search or filter the marketplace, find the source or sink that matches your data flow, and select Select and install.
Choose the data route
Enter an installation name and select the tenant, cluster, and namespace. Select an output topic for a source or an input topic for a sink.
Enter the connection settings
Use the connector-specific guide linked above. It includes a sample value and explanation for every field.
Add credentials
Enter the one-time credential requested by the connector, or expand Use an existing secret reference instead. Stored passwords and tokens are not shown again after submission.
Review and install
Review the destination, topics, and settings, then select Install connector.
Wait for Running status
The connector may briefly show Pending or Provisioning. It is ready when its status changes to Running.
Common setup fields
| Field | What to enter | Example |
|---|---|---|
| Installation name | A unique name of 3–63 characters that starts with a letter | orders-http-source |
| Tenant | The tenant that owns the connector | Acme Streaming |
| Cluster | The tenant's ready cluster association | Select the available ready cluster |
| Namespace | The namespace containing the related topics | orders |
| Output topic | For sources, the topic that receives imported records | api-events |
| Input topic | For sinks, the topic whose records are sent out | order-events |
| Parallelism | Number of connector instances; use the catalog default unless you have a tested scaling requirement | 1 |
Note
The exact tenant, namespace, and topic choices depend on your access. Contact your tenant administrator if the required option does not appear.
Time values
Fields ending in Ms use milliseconds.
| Duration | Value to enter |
|---|---|
| 1 second | 1000 |
| 5 seconds | 5000 |
| 10 seconds | 10000 |
| 30 seconds | 30000 |
| 1 minute | 60000 |
| 5 minutes | 300000 |