Skip to main content

Connectors

Connectors

A connector is how DataLug reaches another system. You create a connection for it once, on the Connections page, and then pick that connection on a Source, Load, DB Script or Notification node. Each connector's page lists its fields, its operations and its limits.

When to use it​

You want toUse
Read or write tablesA database connector
Collect or deliver filesA file storage connector
Read or write records in a sales systemA CRM connector
Work with tickets, issues or marketing dataA support and marketing connector
Read a spreadsheet, or send an email or chat messageA messaging and sheets connector
Send your account's logs to your own toolingAn observability log destination
Call any other HTTP APIThe Generic REST API connector

Databases​

  • SQL Server: tables, views and stored procedures in Microsoft SQL Server.
  • PostgreSQL: tables and stored procedures, with TLS verification options.
  • MySQL: tables and stored procedures in MySQL.
  • Oracle: tables and stored procedures, by service name, SID or TNS.
  • Snowflake: tables, bulk COPY INTO and stage files.

File storage​

The File hub setup guide covers the provider-side setup for these connectors.

CRM​

  • Salesforce: sObjects, files, Knowledge and Data Cloud objects.
  • HubSpot: contacts, companies, deals and related records.
  • Pipedrive: persons, organizations, deals and activities.
  • Zoho CRM: leads, contacts, accounts, deals and other modules.
  • Keap: contacts, companies, opportunities and tasks.
  • Insightly: contacts, organisations, opportunities, leads and tasks.
  • Freshsales: contacts, accounts and deals, read through saved views.
  • Copper: people, companies, opportunities, leads, projects and tasks.

Support and marketing​

  • Zendesk Support: tickets, users, organizations and Help Center articles.
  • Jira Cloud: issues with JQL, comments and worklogs, and issue writes.
  • Marketing Cloud: Data Extension rows and contacts in Salesforce Marketing Cloud.

Messaging and sheets​

Lead sources​

  • Meta Lead Ads: Facebook lead form submissions, one row per lead, through a Webhook Trigger.

Observability​

  • Datadog: account logs to Datadog Log Management.
  • Grafana Loki: account logs to Grafana Loki.
  • Elasticsearch: account logs to an Elasticsearch data stream.
  • Splunk: account logs to the Splunk HTTP Event Collector.

Log destinations are set up under Manage Account > Log Destinations, not as connections.

Other​

  • Generic REST API: any HTTP endpoint, with an API key, a bearer token or OAuth 2.0.
  • DataLug API: the APIs your account deploys in API Studio.

Troubleshooting​

The connection form lists its steps on the left. Open any step from that list. The Environments step holds the values that differ per environment.

Test connection is in the form footer. Beside it, Test against picks Base, the connection as saved, or an environment, whose values are applied first.

  • Test connection fails. Read the message under the form. It names the provider's error and code. Check the credentials first, then whether the system is reachable from the runtime.
  • A connection works in one environment only. Open the Environments step and compare that environment's values with the base connection. Use Test against to test each one.
  • A new connection does not save and names your plan. Your plan sets how many saved connections the account can have, inactive ones included. See Billing.
  • An operation is missing from Configure Action. Some operations can be unavailable on the platform. Saved actions that already use one keep working.
  • A saved action says its operation is turned off. That operation is not available on the platform. Choose another operation for the node.