receive schedule events and get all your team s tickets and get next page
Configured with Google Sheets, Graphql, Schedule Trigger, Split Out. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Routing
- Transform
- Data store
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Every day at 06:00 | Trigger | Schedule Trigger | See node parameters |
| Get all your team's tickets | Web / API | Graphql | See node parameters |
| if has next page | Routing | If | See node parameters |
| Get end cursor | Transform | Edit Fields | See node parameters |
| Get next page | Web / API | Graphql | See node parameters |
| Split out the tickets | Transform | Split Out | See node parameters |
| Set custom fields | Transform | Edit Fields | See node parameters |
| Write tickets to Sheets | Data store | Google Sheets | appendOrUpdate |
| Flatten object to have simple fields to filter by | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleSheetsOAuth2ApihttpHeaderAuth
Workflow notes
Sticky Note1
👇🏽 Set your team name here in the filter. (Our team's name is Adore)
Sticky Note
👈🏽 Set your team name here in the filter. (Our team's name is Adore)
Sticky Note2
👇🏽 Adjust any custom fields. Here we set labels and default estimate of 1
👨🎤 Setup
👨🎤 Setup
- Add Linear API header key
- Add Google sheets creds
- Update which teams to get tickets from in Graphql Nodes
- Update which Google Sheets page to write all the tickets to. You only need to add one column, id. Google Sheets node in automatic mapping mode will handle adding the rest of the columns.
- Set any custom data on each ticket
- Activate workflow 🚀
Sticky Note4
👆🏽 Update which Google sheet to write to
receive schedule events and get all your team s tickets and get next page
receive schedule events and get all your team s tickets and get next page
Purpose and structure
This folder contains the receive schedule events and get all your team s tickets and get next page workflow. Its executable nodes use code, googleSheets, graphql, if, scheduleTrigger, set, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Every day at 06:00
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/0445_Splitout_Code_Import_Scheduled.json MIT; preserve source notices.