90466908a8
<!-- Clearly explain the need for these changes: -->
we met some reality when merging into the docs site but this fixes it
### Changes 🏗️
updates paths, adds some guides
<!-- Concisely describe all of the changes made in this pull request:
-->
update to match reality
### Checklist 📋
#### For code changes:
- [x] I have clearly listed my changes in the PR description
- [x] I have made a test plan
- [x] I have tested my changes according to the test plan:
<!-- Put your test plan here: -->
- [x] deploy it and validate
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Aligns block integrations documentation with GitBook.
>
> - Changes generator default output to
`docs/integrations/block-integrations` and writes overview `README.md`
and `SUMMARY.md` at `docs/integrations/`
> - Adds GitBook frontmatter and hint syntax to overview; prefixes block
links with `block-integrations/`
> - Introduces `generate_summary_md` to build GitBook navigation
(including optional `guides/`)
> - Preserves per-block manual sections and adds optional `extras` +
file-level `additional_content`
> - Updates sync checker to validate parent `README.md` and `SUMMARY.md`
> - Rewrites `docs/integrations/README.md` with GitBook frontmatter and
updated links; adds `docs/integrations/SUMMARY.md`
> - Adds new guides: `guides/llm-providers.md`,
`guides/voice-providers.md`
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
fdb7ff8111. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>
Co-authored-by: bobby.gaffin <bobby.gaffin@agpt.co>
3.8 KiB
Linear Issues
Blocks for creating and managing Linear issues.
Linear Create Issue
What it is
Creates a new issue on Linear
How it works
This block creates a new issue in Linear using the GraphQL API. Specify the team, title, description, and optionally priority and project. The issue is created immediately and assigned to the specified team's workflow.
Returns the created issue's ID and title for tracking or further operations.
Inputs
| Input | Description | Type | Required |
|---|---|---|---|
| title | Title of the issue | str | Yes |
| description | Description of the issue | str | Yes |
| team_name | Name of the team to create the issue on | str | Yes |
| priority | Priority of the issue | int | No |
| project_name | Name of the project to create the issue on | str | No |
Outputs
| Output | Description | Type |
|---|---|---|
| error | Error message if the operation failed | str |
| issue_id | ID of the created issue | str |
| issue_title | Title of the created issue | str |
Possible use case
Bug Reporting: Automatically create issues from error monitoring or customer reports.
Feature Requests: Convert feature requests from forms or support tickets into Linear issues.
Task Automation: Create issues based on scheduled events or external triggers.
Linear Get Project Issues
What it is
Gets issues from a Linear project filtered by status and assignee
How it works
This block retrieves issues from a Linear project with optional filtering by status and assignee. It queries the Linear GraphQL API and returns matching issues with their details.
Optionally include comments in the response for comprehensive issue data.
Inputs
| Input | Description | Type | Required |
|---|---|---|---|
| project | Name of the project to get issues from | str | Yes |
| status | Status/state name to filter issues by (e.g., 'In Progress', 'Done') | str | Yes |
| is_assigned | Filter by assignee status - True to get assigned issues, False to get unassigned issues | bool | No |
| include_comments | Whether to include comments in the response | bool | No |
Outputs
| Output | Description | Type |
|---|---|---|
| error | Error message if the operation failed | str |
| issues | List of issues matching the criteria | List[Issue] |
Possible use case
Sprint Reports: Generate reports of issues in specific states for sprint reviews.
Workload Analysis: Find unassigned or overdue issues across projects.
Status Dashboards: Build dashboards showing issue distribution by status.
Linear Search Issues
What it is
Searches for issues on Linear
How it works
This block searches for issues in Linear using a text query. It searches across issue titles, descriptions, and other fields to find matching issues.
Returns a list of issues matching the search term.
Inputs
| Input | Description | Type | Required |
|---|---|---|---|
| term | Term to search for issues | str | Yes |
Outputs
| Output | Description | Type |
|---|---|---|
| error | Error message if the operation failed | str |
| issues | List of issues | List[Issue] |
Possible use case
Duplicate Detection: Search for existing issues before creating new ones.
Related Issues: Find issues related to a specific topic or feature.
Quick Lookup: Search for issues by keyword for customer support or research.