Skip to content
Applications and cloud sources

Applications and cloud sources

Where: Sources in the sidebar → New source → Connect database → pick the connector under Connector. Applications and cloud sources are listed there too.

Follow Connect a database, application or cloud source and pick the connector under Connector. The fields for each one are below. Connectors marked OAuth open a sign-in window for that service instead of asking for a key; the access they request is read-only.

Amazon S3

  • S3 Path (required): the full path including bucket and file, starting with s3://, for example s3://bucket-name/path/to/file.csv.

BigQuery

  • GCP Project ID and Dataset (both required).
  • Authentication method:
    • Service account key — paste the full contents of the service account’s JSON key file into Service Account JSON.
    • Google OAuth — click Connect with Google and authorize read-only access.

Google Sheets (OAuth)

Authorize read-only access with your Google account, then choose a mode:

  • Single spreadsheet — paste the Spreadsheet URL or ID. Optionally set a Worksheet name (leave it empty to import every tab as its own table) and a Range in A1 notation. The first row is the header.
  • Drive folder — Pick Drive folder: every spreadsheet inside is imported, and each worksheet becomes a table.

OneDrive (OAuth)

Click Connect with Microsoft, then Browse OneDrive to pick a Single file or a Folder. CSV, Parquet and Excel files are supported.

If you see Microsoft needs an administrator from your organization to approve Teramot OneDrive, send the approval link the app offers to your Microsoft administrator. Retrying does not help until they approve it.

Salesforce

  • Salesforce Username, Password and Security Token (all required). Get the token in Salesforce under Settings > Reset My Security Token.

Monday.com

  • API Token (required): in Monday.com, Profile > Developers > My Access Tokens.
  • Workspace ID (optional): leave it empty to load boards from every workspace the token can reach.

Airtable

  • Personal Access Token (required): create it at airtable.com/create/tokens with the data.records:read and schema.bases:read scopes, and give it access to the base.
  • Base ID (required): starts with app; find it in the base’s URL.

HubSpot (OAuth)

Click Connect with HubSpot and authorize access. No API key is needed.

Odoo

  • Host (required): your Odoo address, for example https://mycompany.odoo.com.
  • Database (optional): leave it empty to use the default database.
  • API Key (required): in Odoo, Settings > Technical > API Keys.

Tango

Tango Gestión connects through its API, which your Tango license must include.

  • API URL (required): your Tango Connect address, for example https://123456-001.connect.axoft.com, or your own server’s API port, for example http://servidor:17000. Your own server must be reachable from the internet. Pasting the address of a Tango web page also works, and fills in the company id.
  • API token (required): in Tango web, Menú de usuario › Desarrollador › Generar. The token has the permissions of the Tango user who generates it, so use a query-only user.
  • Company id (required): the number after company/ in the Tango web address; in …/company/32/… it is 32. The Connect key, such as 123456/001, is not the company id.
  • Live queries and Other processes (ABM) (optional): processes to load besides the standard ones, one per line, as 12205 or 12205: Sales by seller. Each Tango screen shows its process id under Apertura › Api.
  • Read history from (optional): Live queries are read from this date onward. Left empty, each query reads its default period in Tango.

The tables offered are Tango’s standard processes (customers, items, orders, sellers, price lists and others) and the ones you add. A process the token cannot read, or that has no data, is not listed. Every refresh loads each table in full.

MongoDB

Choose how to connect under MongoDB connection:

  • Connection URI — paste the Atlas URI from Atlas (Database → Connect → Drivers), replacing <password> with the database user’s password.
  • Host & credentials — for self-hosted MongoDB: Host (the primary node for a replica set), Port, User, Password and Auth Source (admin by default).

In both modes, Database is required: the database whose collections are loaded.

Options:

  • Connect using TLS, with an optional Server CA if your server uses its own certificate authority. With TLS, the host must be the name on the server’s certificate.
  • Authentication method: Username and password, or X.509 certificate, which needs a Client certificate and its Private key (plus the Key passphrase if the key is encrypted).

MongoDB can also be reached through a private connection, in Host & credentials mode with an explicit port.

SAP ECC (RFC)

  • Connection Mode: Application Server or Message Server.
  • Client (Mandant): the 3-digit client number. User and Password. Language is optional (EN by default).
  • Application Server: Application Server Host and System Number (2 digits).
  • Message Server: Message Server Host, Logon Group, Message Server Service, and System ID (SID) or its older alias R/3 Name.
  • Tables (recommended): the SAP tables to load, comma-separated — for example EKKO, EKPO, LFA1. Without it, only the first 100 tables of the catalog are listed.
  • Per-table filter (optional): one filter per line, as TABLE: predicate in SAP OpenSQL, applied in SAP before loading. Use it to bound large tables.
  • SNC (optional) and Advanced ingest (optional) for landscapes that need them.

SAP ECC can also be reached through a private connection, in Application Server mode with a two-digit System Number. Teramot reaches the application server on its RFC port, 3300 plus the system number (3301 for system 01). Message Server mode is not available over a private connection.