Sign in once. Siftree reads your records and reacts to new events as they happen.
Get Job Status
Check the status of a DSS build job, returned as baseStatus.status . Poll this after Build Dataset using the id it returned. NOT_STARTED and RUNNING mean the job is still in flight; DONE , FAILED and ABORTED are…
List Datasets
List the datasets of a DSS project. Use this to discover a dataset's name — the identifier Build Dataset needs to build it — along with its type (e.g. Filesystem ) and connection parameters. Use List Projects first if…
List Jobs
Retrieve the latest build jobs of a DSS project, each with its jobId and state . Use this to check what a project has been building recently, or to recover a jobId you no longer have before calling Get Job Status .…
List Projects
List the projects on the DSS instance. Start here when you only know a project by its display name: every other Dataiku tool is addressed by projectKey (e.g. MYPROJECT ), which this tool returns. Only projects the…
List Scenario Runs
Retrieve the last runs of a DSS scenario. Use this after Run Scenario , which returns no run identifier of its own, to follow the outcome: each entry carries a runId , start / end timestamps and a result object…
List Scenarios
List the scenarios of a DSS project, with each scenario's id , whether it is currently running , and whether it is active (i.e. responding to its own triggers). Call this before Run Scenario to find a valid scenario…
Act
Take action in Dataiku
Agents update records and send messages for you, automatically, as drafts, or after you approve.
Build Dataset
Start a job that builds one or more outputs (typically datasets) in a DSS project. Use this to rebuild specific outputs directly; use Run Scenario instead when the pipeline is already orchestrated as a scenario. Use…
Run Scenario
Start a run of a DSS scenario — the usual way to kick off an orchestrated pipeline (a sequence of builds, checks and reporters) as opposed to building a single dataset, which Build Dataset does. Use List Scenarios to…
Siftree is an AI platform that sales, CX, marketing, product, and strategy teams use to find, win, and keep customers.
Siftree connects calls, tickets, reviews, social, documents, video, and the systems you already use — then builds pipelines, datasets, tools, and cited insights your team and agents can operate on. Long-horizon agents keep building after you walk away.
- Describe what you need in plain language; Siftree builds pipelines, structures the data, and routes models for language, vision, audio, transcription, classification, and enrichment.
- Operate on datasets, tools, reports, and cited insights. You define the rules — what counts, how it's scored, what gets labeled.
- Marketplace: 14,824 sources across 4,169 apps and websites as of October 2026, plus any public website. Search, choose a source, and create an analysis-ready dataset without scraper maintenance.
- Native connectors for help desks, CRMs, and call recorders, plus upload and API. Audio and video are transcribed and labeled with everything else.
- Runs on a schedule or a trigger, and alerts your team in Slack when a threshold is crossed.
- Acts in your systems: writes labels and fields back to the help desk or CRM, opens issues in Linear or Jira, and drafts replies and emails. Each agent runs automatically, drafts for review, or asks first, and every action is logged.
- Ask questions of your data from Claude or ChatGPT through Siftree MCP.
- Enterprise protections: continuous verification of every request, encryption in storage and transit, privilege and identity governance, immutable activity logs.
- Teams use the eight products in place of separate point tools for prospecting data, support analytics, social listening, community triage, ad research, AI search visibility, research repositories, and competitive intelligence.