MintyGo / Intake / System 01 of 02
2023Recorded work
Client-linked batch intake and paced task queue
A client uploads a spreadsheet of article requests. The workflow separates the rows and releases them one minute apart in the recorded setup.
- Noah’s contribution
- Explained the batch integration, client resolution, spreadsheet conversion and paced handoff into task creation.
- Historical stage
- Historical configured walkthrough and narrated two-record test.
- Part of the business
- MintyGo overview ↗
- Typeform
- Google Sheets
- CSV / XLSX
- Webhooks
- Queue-based processing
- ClickUp
Inside this system
The workflow
The handoffs
inside the work.
Follow the main path and its branches. Select a step for context; the account below explains what was built, tested or planned.
- Client-specific batch link
A Typeform upload carries the client identity with the CSV or XLSX batch. - Client record lookup
Retrieve reusable client fields and ownership for the later article tasks. - ClickUp template lookup
Find the client-named template and carry any matching ID in the article payload. - Normalize the uploaded batch
Download the file, convert it to a Google Sheet and list individual article rows. - Paced article queue
Queue each article request separately and release requests one minute apart in this setup. - Client-aware article payload
Combine each row with the client and template lookup results for the next webhook. - Task-preparation webhook
Hand each paced request to the client-template or generic-fallback creation branch.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Client-linked submission | Client-specific intake link and uploaded CSV or XLSX batch. | Associate the batch with the correct client before generating production work. |
| Article row | Article-specific information supplied in one row of the uploaded spreadsheet. | Keep each requested article as an individual unit of work. |
| Queued request | An individual article request passed to task preparation at the configured interval. | Control the pace at which downstream services receive new work. |
Inside the system / 01
Start with client identity, not an anonymous file
The batch links were set up per client. Opening a link connected the submission to a client record and prompted the operator to check for the corresponding ClickUp template. This association mattered because a spreadsheet alone did not carry the full production context: the created tasks also needed the client’s reusable requirements.
After submission, the integration downloaded the CSV or XLSX file from Typeform, retrieved the client record and listed the available ClickUp templates. The uploaded file became a Google Sheet so its article rows could be read and processed individually. The later task-creation stage received both row information and the result of the template lookup.
Inside the system / 02
Separate a large batch from a burst of requests
Each article entered a queue before reaching the next webhook. In the recorded setup, the queue released article requests one minute apart. This created a deliberate pacing point between spreadsheet intake and task creation, rather than making every uploaded row arrive at ClickUp simultaneously.
Noah spaced requests to avoid overloading ClickUp and the separate OpenAI-based generation process. The one-minute interval describes this configuration; sustained production capacity was not tested.
Inside the system / 03
Test the handoff with a small, inspectable batch
The walkthrough used two populated rows and deliberately left an empty row between them. Noah narrated the template lookup, sheet upload and queued requests, then described the first task appearing and the second execution following about a minute later. Both records were present at the end and were described as generating.
A form redirect contained HTTPS twice and still needed correction. That remaining issue sits alongside the successful narrated task handoff: the recording does not establish a finished end-to-end client launch, approved article output or sustained production volume.
Within MintyGo