Connecting Datacloud
Wire external databases and ingest APIs into Salesforce Data Cloud with correct connector JSON, credentials, and schema definitions.
Overview
Connecting-datacloud is an agent skill for the Build phase that guides creation of Salesforce Data Cloud connector and ingest API configuration JSON.
Install
npx skills add https://github.com/forcedotcom/sf-skills --skill connecting-datacloudWhat is this skill?
- JSON templates for HerokuPostgres and IngestApi connector definitions
- Credential and parameter blocks for ingress-style database connections
- Ingest API schema definitions with Text, DateTime, and custom fields
- Part of the forcedotcom *-datacloud skill family with shared CREDITS/UPSTREAM docs
- Agent-guided assembly of label, name, connectorType, and method fields
- Documents HerokuPostgres and IngestApi connectorType patterns
- Sample ingest schema includes Id, Name, Timestamp, and Value fields
Adoption & trust: 603 installs on skills.sh; 513 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to connect a Heroku Postgres database or custom ingest stream to Data Cloud but lack a consistent connector payload and field schema.
Who is it for?
Builders wiring Postgres or Ingest API sources into an existing Salesforce Data Cloud org with agent-assisted JSON.
Skip if: Teams that only need high-level Data Cloud strategy without connector implementation, or non-Salesforce data stacks.
When should I use this skill?
User is defining or editing Salesforce Data Cloud connectors, ingest API objects, or Postgres ingress credentials as JSON.
What do I get? / Deliverables
You get validated connector and schema JSON blocks ready to apply in your Data Cloud workflow, with a clear path to related orchestrating-datacloud skills.
- Connector JSON with credentials and parameters
- Ingest API schema JSON with typed fields
Recommended Skills
Journey fit
Data Cloud connector setup is integration work done while building or extending a Salesforce-centric data platform. Connector types (Heroku Postgres, Ingest API) and field schemas are classic build-time integration tasks, not launch or growth work.
How it compares
Use for concrete connector JSON in the Data Cloud family—not generic MCP database tools or unrelated ETL CLIs.
Common Questions / FAQ
Who is connecting-datacloud for?
Solo builders and small teams on Salesforce who configure Data Cloud ingest connectors and want structured, repeatable JSON from their coding agent.
When should I use connecting-datacloud?
During Build integrations when adding Heroku Postgres ingress or Ingest API objects, or when extending an existing *-datacloud workflow with a new source.
Is connecting-datacloud safe to install?
Review credential handling in your repo and check the Security Audits panel on this Prism page before installing; never commit real passwords in connector JSON.
Workflow Chain
Requires first: skill forcedotcom sf skills orchestrating datacl
SKILL.md
READMESKILL.md - Connecting Datacloud
# Credits & Acknowledgments This skill is part of the `*-datacloud` family of skills covering the full Data Cloud workflow lifecycle. Shared upstream source mapping and maintenance notes live in: - [../orchestrating-datacloud/CREDITS.md](../orchestrating-datacloud/CREDITS.md) - [../orchestrating-datacloud/UPSTREAM.md](../orchestrating-datacloud/UPSTREAM.md) { "connectorType": "HerokuPostgres", "label": "My Heroku DB", "name": "My_Heroku_DB", "method": "Ingress", "credentials": [ { "paramName": "credentialType", "value": "UsernamePasswordAuthentication" }, { "paramName": "user", "value": "<HEROKU_DB_USER>" }, { "paramName": "password", "value": "<HEROKU_DB_PASSWORD>" } ], "parameters": [ { "paramName": "jdbc_connection_url", "value": "<HOST>:<PORT>" }, { "paramName": "DATABASE", "value": "<DATABASE_NAME>" } ] } { "connectorType": "IngestApi", "label": "<CONNECTOR_LABEL>", "name": "<CONNECTOR_NAME>" } { "schemas": [ { "label": "<OBJECT_NAME>", "name": "<OBJECT_NAME>", "schemaType": "IngestApi", "fields": [ { "name": "Id", "label": "Id", "dataType": "Text" }, { "name": "Name", "label": "Name", "dataType": "Text" }, { "name": "Timestamp", "label": "Timestamp", "dataType": "DateTime" }, { "name": "Value", "label": "Value", "dataType": "Number" } ] } ] } { "connectorType": "REDSHIFT", "label": "My Redshift", "name": "My_Redshift", "method": "Ingress", "credentials": [ { "paramName": "authenticationOption", "value": "usernameAndPassword" }, { "paramName": "username", "value": "<REDSHIFT_USER>" }, { "paramName": "password", "value": "<REDSHIFT_PASSWORD>" } ], "parameters": [ { "paramName": "url", "value": "<HOST>:<PORT>" }, { "paramName": "database", "value": "<DATABASE_NAME>" }, { "paramName": "hasPrivateNetworkRoute", "value": "false" } ] } { "connectorType": "SPUnstructuredDocument", "label": "My SharePoint Docs", "name": "My_SharePoint_Docs", "method": "Ingress", "credentials": [ { "paramName": "clientId", "value": "<AZURE_APP_CLIENT_ID>" }, { "paramName": "clientSecret", "value": "<AZURE_APP_CLIENT_SECRET>" }, { "paramName": "tokenEndpoint", "value": "https://login.microsoftonline.com/<AZURE_TENANT_ID>/oauth2/v2.0/token" } ] } { "connectorType": "SNOWFLAKE", "label": "Snowflake Demo", "name": "Snowflake_Demo", "method": "Ingress", "credentials": [ { "paramName": "credentialType", "value": "KeyPairAuthentication" }, { "paramName": "user", "value": "<SNOWFLAKE_USERNAME>" }, { "paramName": "privateKey", "value": "<YOUR_PRIVATE_KEY_WITHOUT_BEGIN_END_HEADERS>" } ], "parameters": [ { "paramName": "accountUrl", "value": "https://<ORG_ID>-<ACCOUNT_ID>.snowflakecomputing.com" }, { "paramName": "database", "value": "<DATABASE_NAME>" }, { "paramName": "warehouse", "value": "<WAREHOUSE_NAME>" }, { "paramName": "region", "value": "<AWS_REGION>" }, { "paramName": "hasPrivateNetworkRoute", "value": "false" } ] } # connecting-datacloud Connection and connector workflows for Salesforce Data Cloud. ## Use this skill for - listing available connector types - inspecting configured connections - testing a connection - browsing source objects, databases, fields, and uploaded schemas - preparing connector JSON for Snowflake, SharePoint Unstructured, and Ingestion API sources - preparing for stream creation ## Key reminders - `connection list` requires `--connector-type` - `connection test` may need `--connector-type` for non-Salesforce name resolution - use `connection schema-upsert` aft