> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/reference/glossary.md). # Glossary Alphabetized definitions of every term used across the Fastn platform and documentation. | Term | Definition | Where to find it | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | | **Connector** | A pre-built integration with a third-party system (Salesforce, Slack, Shopify, etc.). Handles authentication and exposes that system's actions. | Integrations → Connectors | | **Connection** | An authenticated instance of a connector for a specific account. One connector can have multiple connections (e.g., two Slack workspaces). | Integrations → Connections | | **SaaS connector** | Your product's connector, registered with its connection scopes. | [Settings → SaaS Connectors](/manage/saas-connectors.md) | | **Connection scope** | One capability of your API, such as `billing`. Each customer holds one connection per connection scope. | [Settings → SaaS Connectors](/manage/saas-connectors.md) | | **System** | Any other software a customer uses, such as a CRM, Jira or Slack. | [Integrations → Connectors](/build/connectors/the-catalogue.md) | | **Workflow** | An automation that moves and transforms data between systems. Built by AI agents from a plain-language description; the generated code can be inspected. | Integrations → Workflows | | **Integration** | Connectors plus a workflow and its trigger, doing a job between your product and a customer's system. | [Onboarding → Choose integrations](/fastn/readme/onboarding/choose-integrations.md) | | **Trigger** | What starts a workflow. Three types: Webhook, Scheduler, App Event. | Integrations → Triggers | | **Customer** | An end user organization of your SaaS product. Each customer's connections and data are isolated. | Settings → Customers | | **Organization (customer organization)** | A customer/tenant of your product that will access embedded integrations. It can have multiple users. Each customer organization has a string identifier, the org id, created when the org is registered in the Fastn platform through the UI or the [Create a Customer Organization](/embed/embedding/integration-flow.md#create-a-customer-organization) API. It is represented in APIs as "org-id". | Settings → Customers | | **User** | An end-user who is part of the customer organization that will access embedded integrations. Each user is expected to have a unique user id, represented as "user-id". Sending a "user-id" is optional. | The `x-user-id` header | | **Identity hash** | Also written Identity-hmac, or the `x-identity-hmac` header. An HMAC-SHA256 of the org ID and user ID (newline-joined), signed with your identity-verification secret. It proves that your backend authorized that specific org and user pair. | [API keys → Identity hash](/manage/api-keys.md#identity-hash) | | **Widget** | The embedded interface your customers use to connect apps and manage integrations inside your product. | Widgets → Widget Builder | | **Setup Assistant** | The AI-guided onboarding wizard that configures a new SaaS partner's integration platform (Use cases → Connectors → Workflows → Embed → Live). | Home page | | **Build with AI** | The label for the AI integration/workflow builder. | Workflows tab; embedded widget | | **Agent** | The Integrations sub-tab where you describe an integration and the AI agents build it. | Integrations → Agent | | **AI tools** | Claude, ChatGPT, Gemini, Cursor and similar, connected to fastn through its MCP server. They use no AI credits. | [MCP gateway](/build/mcp-gateway.md) | | **AI credits** | What the fastn agent uses. Your plan includes a monthly allowance, and finishing onboarding adds 50 on top of it. | [Onboarding](/fastn/readme/onboarding.md) | | **AI Assistant** | A toggleable widget section that lets your customers describe an automation and have it built inside the widget. | Widget sections | | **MCP Gateway** | The endpoint that exposes integrations as tools for AI agents, over the Model Context Protocol. Has a Control Plane (Admin MCP) and a Data Plane (Customer Gateway). | Widgets → Embed → MCP | | **Embed token** | A short-lived token (15-minute expiry, `emb_` prefix) generated from your backend that scopes an embedded widget to a specific customer. | Generated via the embed token API | | **API key** | A credential in `fsk_` format (`fsk_test_` or `fsk_live_`) used to authenticate backend API calls, including generating embed tokens. | Settings → API Keys | | **Execution tier** | A workflow's runtime mode: Instant (synchronous, ≤60s), Standard (async, ≤15min), or Long (async, ≤6hr). | Workflow editor → Configuration | | **Dead Letter Queue (DLQ)** | An option on webhook triggers that captures failed events for later inspection or replay. | Triggers → Webhook → Advanced options | | **Org-level / User-level** | The two ways a connection can be scoped: shared across a customer's whole organization (org-level) or isolated to an individual user (user-level). | Set via the embed iframe URL | --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.fastn.ai/reference/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 `automate deployments from our CI pipeline` 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.