Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Salesforce Data 360 SFTP Ingestion Pro

    1

    Validate Parquet schemas and publish files to Salesforce Data 360 via guarded SFTP staging scripts.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Salesforce Data 360 SFTP Ingestion Pro

    Salesforce Data 360 SFTP Ingestion Pro

    Example session with this skill installed

    Validate my orders.parquet file against the orders-contract.json schema and publish it to the /salesforce/inbound directory.

    • Read your context and instructions
    • Compiled the salesforce data 360

    I have completed the validation and publication process for the orders data. The file passed all schema checks and has been staged on the remote SFTP server.

    Publication Audit Report

    TaskStatusDetails
    Schema ValidationPASSAll 14 fields match orders-contract.json
    Key CheckPASS0 nulls, 0 duplicates found in order_id
    Row Count12,500Matches expected batch size
    StagingSUCCESSUploaded as orders.parquet.part
    Final RenameSUCCESSAtomic rename to orders_20231027_T1430.parquet
    Remote PathCOMPLETED/salesforce/inbound/orders_20231027_T1430.parquet
    {
      "event": "publication_success",
      "timestamp": "2023-10-27T14:30:05Z",
      "contract": "orders-contract.json",
      "remote_file": "orders_20231027_T1430.parquet",
      "stats": {
        "rows": 12500,
        "errors": 0
      }
    }
    

    Next steps

    1. Log in to your Salesforce Data 360 org and navigate to Data Streams.
    2. Refresh the stream associated with the /salesforce/inbound directory to begin ingestion.
    3. Check the Data Lake Object (DLO) metadata to verify the new records are visible.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Manual SFTP uploads to Salesforce Data 360 often lead to ingestion failures due to schema drift or primary key violations. This skill enforces data integrity by validating Parquet files against local contracts before they hit the staging server.

    What it does

    • Contract validation verifies Parquet schemas against JSON definitions to prevent upstream ingestion errors.
    • Key integrity checks identifies duplicate or null primary keys and validates record grain before publication.
    • Guarded SFTP staging uploads files using .part extensions and atomic renames to ensure Data 360 doesn't pick up partial files.
    • Unique file naming generates compliant, unique filenames to prevent accidental overwrites in the staging directory.
    • Lifecycle auditing generates JSON reports for every validation and publication step to provide an audit trail of source quality.

    How it works

    1. Define the contract by specifying the physical schema, primary keys, and refresh semantics in a JSON manifest.
    2. Execute validation using the provided scripts to check Parquet files for schema compliance and key quality.
    3. Stage for publication by configuring environment variables for host, user, and SSH keys.
    4. Publish to SFTP using the guarded script which handles the staging, renaming, and remote path recording.
    5. Monitor Ingestion by verifying the resulting Data Stream runs and DLO freshness within Salesforce.

    Frameworks & tools

    This tool utilizes Node.js for validation logic and OpenSSH sftp for secure file transfers. It is designed for workflows targeting Salesforce Data 360 (Data Cloud).

    Why this beats prompting it yourself

    Prompting an agent to "upload a file" ignores the specific atomic renaming requirements and schema strictness of Data 360. This skill provides the exact shell scripts and validation logic needed to handle Parquet-to-D360 pipelines without manual intervention or corrupt data streams.

    Use cases

    • Pre-flight validation for automated ETL pipelines pushing Parquet files to Salesforce.
    • Debugging schema drift when Data 360 streams fail due to unexpected field changes.
    • Key quality audits to ensure upsert keys are unique and non-null before ingestion.

    Known limitations

    Requires local OpenSSH and Node.js environments. Does not include Data 360 API credentials or scheduling logic.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.

    Requires local Node.js and OpenSSH sftp client. Does not trigger Data 360 ingestion internally; it only manages the publication to the staging area.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Accounts
    Salesforce
    Software
    Node.jsSalesforce CLI

    Permissions

    Read Files
    Write Files
    Environment Variables
    Network Access
    Terminal / Shell

    Allowed Hosts

    login.salesforce.com
    Listed5 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a pre-flight validator and secure uploader, ensuring Parquet files strictly match your Salesforce Data 360 schema and using atomic renaming to prevent the platform from ingesting incomplete files.

    The package includes a comprehensive validation engine, a manifest generator for data contracts, and guarded SFTP shell scripts designed specifically for the Salesforce staging environment.

    Yes, as long as your agent environment supports Node.js and has OpenSSH installed, it can trigger these scripts to automate the validation and publication workflow.

    It validates physical schema compliance (data types, field names) and data integrity (null checks, primary key uniqueness) against a JSON contract before any data is transmitted.

    This skill is optimized for SFTP-based ingestion into Salesforce Data 360 (Data Cloud); while it handles Parquet files generally, the atomic staging logic is tailored to Salesforce's ingestion requirements.

    You will need a local environment with Node.js and OpenSSH, along with your Salesforce SFTP credentials and a JSON definition of your target data schema.

    New in Data & Databases