> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/sections-1.md). # Todoist Sections Blocks for managing sections within Todoist projects. ## Todoist Delete Section ### What it is Deletes a section and all its tasks from Todoist ### How it works Uses section ID to delete via Todoist API. ### Inputs | Input | Description | Type | Required | | ----------- | ----------------------- | ---- | -------- | | section\_id | ID of section to delete | str | Yes | ### Outputs | Output | Description | Type | | ------- | ---------------------------------------- | ---- | | error | Error message if the operation failed | str | | success | Whether section was successfully deleted | bool | ### Possible use case Removing unused sections or reorganizing projects. *** ## Todoist Get Section ### What it is Gets a single section by ID from Todoist ### How it works Uses section ID to retrieve details via Todoist API. ### Inputs | Input | Description | Type | Required | | ----------- | ---------------------- | ---- | -------- | | section\_id | ID of section to fetch | str | Yes | ### Outputs | Output | Description | Type | | ----------- | ------------------------------------- | ---- | | error | Error message if the operation failed | str | | id | ID of section | str | | project\_id | Project ID the section belongs to | str | | order | Order of the section | int | | name | Name of the section | str | ### Possible use case Looking up section details for task management. *** ## Todoist List Sections ### What it is Gets all sections and their details from Todoist ### How it works Connects to Todoist API to retrieve sections list. ### Inputs | Input | Description | Type | Required | | ----------- | -------------------------------------- | ---- | -------- | | project\_id | Optional project ID to filter sections | str | Yes | ### Outputs | Output | Description | Type | | -------------- | ------------------------------------------ | ---------------------- | | error | Error message if the operation failed | str | | names\_list | List of section names | List\[str] | | ids\_list | List of section IDs | List\[str] | | complete\_data | Complete section data including all fields | List\[Dict\[str, Any]] | ### Possible use case Getting section information for task organization. *** --- # 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://agpt.co/docs/integrations/block-integrations/sections-1.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.