Offline Data (CRM) Connections
Share CRM and offline data, such as leads, bookings and revenue, with Scowtt.
- Connect Salesforce to ScowttScowtt learns which leads become customers by reading your CRM history. Salesforce connects through a native connector in the Scowtt app, which is the fastest way to share CRM data. You authorize access with a standard OAuth login, so no credentials are shared directly with Scowtt.
- Connect HubSpot to ScowttHubSpot connects through a native connector in the Scowtt app. You authorize access with a standard OAuth login, so no credentials are shared directly with Scowtt.
- Connect Klaviyo to ScowttKlaviyo connects through a native connector in the Scowtt app. You authorize access with a standard OAuth login, so no credentials are shared directly with Scowtt.
- Share data through BigQueryIf your data lives in BigQuery, or can be exported there, you grant Scowtt read-only access to the relevant dataset. Your data stays in your own Google Cloud project; nothing is copied or moved. Scowtt queries the dataset directly on a schedule.
- Share data through Databricks Delta SharingIf you use Databricks with Unity Catalog, share tables with Scowtt through Delta Sharing. Scowtt reads the live tables read-only, with no export job to schedule.
- Send files through SFTPSFTP is a simple way to get started quickly. Your team uploads files to a Scowtt SFTP account on an agreed schedule, using key-based login.
- Share data through Google Cloud StorageFor teams already on Google Cloud, Scowtt can set up a read-only access pattern against a GCS bucket you own, similar to the S3 setup.
- Send files to a Scowtt-managed bucketIf your team doesn't run Google Cloud, or your tool writes files out, Scowtt can provide the bucket. Your tool gets upload access to one folder.
- Share data through Amazon S3You keep full ownership of your S3 bucket. Your team creates a role in your own AWS account that gives Scowtt read-only access to a specific bucket or folder. No access keys or long-lived credentials are ever shared, and you can revoke access entirely on your end at any time.
- Push data to Scowtt's APIIf your team has development resources and wants to send data directly, Scowtt can provide an API endpoint for your systems to push to. Because the API is flexible across customers, it starts with a short mapping exercise to align your fields with what Scowtt expects.
- Let Scowtt pull from your APIIf none of the other options fit, for example when your data is only available through a proprietary internal API, Scowtt can build a custom connector to pull directly from your system. It's the most resource-intensive option and is usually recommended only when no other export path exists.
- Export data from SnowflakeSnowflake customers unload curated tables on a schedule to cloud storage that Scowtt can read.
- Export data from Amazon RedshiftRedshift customers unload the agreed tables on a schedule to an S3 bucket they own, then give Scowtt read-only access.
- Export data from AmplitudeAmplitude customers use the built-in export to send events to a bucket they own, then give Scowtt read-only access.
- Send data from Twilio SegmentSegment customers deliver data through the BigQuery or AWS S3 destination, depending on their plan.