> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/get-started/glossary.md). # Distro glossary Use these terms to understand the app and the guides. | Term | Meaning | | ------------------ | ------------------------------------------------------------------------------------------------- | | Workflow | A trigger followed by connected steps and outcomes. | | Trigger | The event that starts a run, such as a new form submission. | | Run | One execution of a workflow for one accepted event. | | Version | The published configuration used by a run. Editing the draft does not rewrite past runs. | | Queue | A pool of members who can receive assignments. | | Routing profile | The rotation, availability and turn-refund rules used by a queue. | | Rulebook | Ordered rules that resolve a lead to an owner or queue. | | Turn | An assignment counted toward a member's rotation. Refunds adjust future rotation when configured. | | Event type | Reusable duration, location, questions and host settings for a meeting. | | Booking link | A shareable route to a personal or group event. | | Show Scheduler | A workflow step that offers times, then continues on Booked or Not booked. | | Field catalog | The reusable person and company fields and their source mappings. | | Enrichment chain | An ordered set of providers used to fill lead data. Behavior varies by surface. | | Connected identity | A mapping between a Distro member and their user, owner or sender identity in another tool. | | Records | The stored people and companies available to Lead fields and record actions. | | Idempotency key | An identifier you reuse when retrying the same API event. | For the overall product journey, see [Welcome](/welcome.md). Coming from the old product? See [Move from the old routers](/migrate.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/get-started/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.