# SDK Core Concepts ## Core concepts of Integrations SDK A workflow server consists of the following concepts: ### The server The server exposes a REST API that the ebbot platform can interpret. This SDK uses [FastAPI](https://fastapi.tiangolo.com/) to spin up that server. ### Connections Integrating with external systems requires settings and credentials to access that system, and the credentials are different for each client. A connection represents a set of credentials that can be used to connect to the system you integrate with. A server usually has many connections, one for each client that's using it. ### Subscriptions A trigger can be subscribed to by a service, for example the Ebbot Automations platform. The SDK takes care of notifying all subscribers when a trigger is invoked. ### Actions An action is something that can be performed by the workflow server. For example, it could be creating a ticket, updating an existing ticket or adding a reply. ### The Manifest The manifest describes all available connections, triggers and actions. The manifest is automatically generated by the SDK, and it's used by the Ebbot platform to discover what capabilities a workflow server can have. --- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://docs.ebbot.ai/ebbot-docs/developer-resources/ebbot-automations/integrations-sdk/sdk-core-concepts.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.