# Before You Begin {% hint style="info" %} CONNECTORS ARE COMING AUGUST 2026 {% endhint %} ### Overview Connectors are a paid feature available to all UbiQuity customers. Access is controlled by user permissions, and some setup steps will require involvement from technical teams within your organisation. Taking a few minutes to prepare before you start will help ensure your Connector runs smoothly once it's active. *** ### Permissions Access to Connectors is controlled by user permissions within UbiQuity. You need the appropriate permission to view the Connectors dashboard. Additional permissions are required to create, edit, and manage Connectors. If you cannot see Connectors in the menu, or do not have permission to make changes, contact an administrator within your organisation or reach out to your UbiQuity account manager. *** ### What you need before you start #### **A supported storage location** Connectors work with storage locations that you host and manage within your own environment. UbiQuity does not host storage on your behalf. Supported storage types are: * SFTP * Microsoft Azure Blob Storage * Amazon S3 Before setting up a Connector, make sure your storage location is provisioned and accessible. See Connection Setup for instructions specific to your storage type. #### **Access credentials** You will need credentials that allow UbiQuity to connect securely to your storage location. | Storage type | Credentials needed | | ------------------ | ---------------------------------------------------------------------- | | SFTP | Hostname, username, and SSH key or password | | Azure Blob Storage | Storage account details and SAS token or Application Service Principal | | Amazon S3 | Bucket details and IAM role or access keys | Use dedicated service accounts where possible, and limit access to only the folders or containers required for the Connector. #### **A sample file (imports only)** If you are setting up an Import Connector, you will need a representative sample CSV file to upload during setup. Your sample file should: * Use the same structure as the files you plan to import * Include a header row * Contain realistic data values All fields referenced by the Connector must already exist in UbiQuity. Connectors do not create database fields. #### **An understanding of your data flow** Before starting, be clear on the following: * Whether you are importing data into UbiQuity or exporting data out * Which database is in scope — Contact, Transactional, or both * How often the Connector should run. Import Connectors scan for matching files every five minutes automatically. Export Connectors run on a schedule you configure. *** ### Involving the right people You do not need to be technical to configure a Connector within UbiQuity. However, the underlying storage and access controls are typically managed by IT or cloud platform teams within your organisation. You may need support from: * IT or infrastructure teams * Cloud platform teams (AWS, Azure) * Security or compliance teams These teams can provision storage, generate credentials, and confirm that the setup meets your organisation's security and data residency requirements. *** ### Pricing and billing Connectors are billed monthly, per Connector. Billing begins when a Connector is activated and is charged for the full month — partial months are not prorated. If you deactivate a Connector during the month, the full monthly charge still applies for that billing period. See the [UbiQuity pricing page](https://www.ubiquity.co.nz/platform/connectors#pricing) for current Connector pricing. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ubiquity.co.nz/documentation/data-and-integrations/connectors/before-you-begin.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.