Ingestion
Glossary
Learn the meaning of key terms used in Sprinto Ingestion, including plans, entities, webhooks, workflows, YAML, execution, and ingestion-specific concepts.
This glossary explains commonly used terms within Sprinto’s Ingestion module.
Use this reference to understand ingestion concepts, workflow terminology, and configuration language used across plans, entities, and webhooks.
| Term | Definition |
|---|---|
| AI Editor | A conversational workspace that allows you to create or modify ingestion plans using prompts instead of manual configuration. |
| Attached Plan | A plan linked to a webhook that determines how incoming payloads are processed. |
| Cache | Stored step output reused during execution to improve performance and reduce repeated requests. |
| Checkpoint | A workflow marker that defines execution boundaries inside a plan. |
| Credential | Authentication information used to connect to an external service or API. |
| Custom Field | A user-defined field added to an entity type to store additional metadata. |
| Data Fetching | A category of workflow steps used to retrieve information from external systems. |
| Data Processing | A category of workflow steps used to transform or restructure incoming data. |
| Data Storage | A category of workflow steps used to save or delete entity records. |
| Debug Run | A controlled execution mode used to test workflows without running a full production workflow. |
| Entity | A stored record created through ingestion processing. |
| Entity Record | An individual data instance stored under an entity type. |
| Entity Type | A schema definition that determines how ingestion records are structured. |
| Execution Interval | The schedule that determines how frequently a plan runs automatically. |
| Filter Expression | Logic used to decide whether an incoming webhook event should trigger processing. |
| Ingestion | Sprinto’s framework for receiving, processing, and storing external data. |
| JSONATA | A query and transformation language used for filtering, mapping, and processing JSON data. |
| Output | A value generated during plan execution that can be referenced after workflow completion. |
| Parameter | A reusable input value used within an ingestion plan. |
| Payload | The incoming request body sent to Sprinto through a webhook or API workflow. |
| Plan | A workflow definition that controls how ingestion data is retrieved, processed, and stored. |
| Provider | A connected integration or external system associated with an ingestion workflow. |
| Rate Limiting | A control that restricts how many requests a webhook can receive within a defined period. |
| Recent Events | A webhook activity log showing received requests and processing outcomes. |
| Reference Field | A field that creates a relationship between one entity type and another. |
| Revision History | A log of saved plan versions that allows comparison and rollback. |
| Rollback | The process of restoring a previous plan version. |
| Run History | A historical record of plan executions. |
| Runtime Parameter | A dynamic value passed into a workflow during execution. |
| Step | A single action performed within an ingestion workflow. |
| Step Range | A debug execution option that runs only a selected portion of the workflow. |
| Template-Based Plan | A plan created from a preconfigured ingestion template. |
| Verbose Logging | Detailed execution logs generated during a run or debug session. |
| Webhook | A unique endpoint URL that receives data from external systems. |
| Workflow | The sequence of steps, logic, and configuration that defines ingestion processing. |
| YAML | A human-readable configuration format used to define ingestion workflows. |
| YAML Editor | A direct configuration editor that allows advanced editing of ingestion workflow YAML. |