Integrations
The screens for moving data in and out of Optima over files, streams and databases, and for reaching systems inside your own network.
The integration screens are where data flows are set up and watched. Together they cover how data gets into Optima from your systems, how it gets out again, and how Optima reaches systems that are not on the public internet.
| Screen | Use it to |
|---|---|
| Data connectors | Define the connections that import or export data: files on SFTP or cloud storage, Kafka and NATS streams, and SQL databases. Also holds the estate-wide run history and scheduled SQL transforms. |
| Connector detail | Configure one connector: filters, field mappings, schedule, transform script, and read its run history. |
| Private networks | Route a connector's outbound connections through a tunnel into your own network. |
Data connectors sits in the Data group of the navigation rail. Private networks is under Settings → Integrations.
Licence and roles
Data connectors and private networks are part of the Connect licence feature. If your plan does not include it, neither entry appears in the navigation. Reading needs the integration_viewer role; creating, changing, activating and deleting needs integration_editor, or another role your administrator has given access to this area — see Licences and roles.
Settings that need their own explanation
A few connector settings are written up as separate pages because the console links to them from its help icons:
- Collection purposes and clearance: which consent purposes imported data is stamped with, and what an export may send.
- Change data capture: importing database change events.
- Field mappings: how file columns become profile, event or dataset fields.
- Google Cloud Storage credentials and Amazon S3 credentials.
- Export enrichment: adding fields to exported profiles.
- SQL transforms: scheduled statements and report exports.
- Dead letters and retries: what happens to messages that keep failing.