MintyGo / Business overview
2023Recorded work
A client spreadsheet.
A queue of
production-ready tasks.
MintyGo’s workflow turned client spreadsheets into individual article assignments, released at a controlled pace. Each assignment carried the client’s requirements and the writing, editing and delivery steps—even when a client-specific setup was missing.
Explore the workflow01 / Business context
A spreadsheet of work.
A structured production queue.
A batch of article requests is only the beginning of a content-production process. Each spreadsheet row needs to arrive with the right client requirements, the right task structure and a clear next step for the team. Sending every row through at once also creates unnecessary pressure on the services that create and process those tasks.
Client-specific intake, a paced queue and reusable work structures connected the batch to production preparation. A recorded two-request test showed tasks created about a minute apart. The studies below explain batch handling and task preparation separately.
02 / Inside the workflow
One batch.
Two paths.
A useful handoff.
Follow an article request from client-linked intake to a prepared production task. Explore the template decision that keeps the structure intact.
Choose a system, then select a component for its details and connections.
- 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.
03 / System directory
Explore the two
system studies.
Go inside the workflow, key records, implementation decisions, human handoffs, historical tests and known boundaries.
Intake
Production
04 / Contribution & scope
The role behind
the system work.
Noah’s work covered batch intake and task preparation: carrying client fields into production, assigning subtasks and creating a fallback template. Article generation followed as a separate component of the production process.
The recorded test used two populated spreadsheet rows with an empty row between them. The walkthrough describes two ClickUp tasks being created about a minute apart, populated client fields and assignees on the production subtasks. Both tasks were described as generating at the end.
A missing client-specific template had a defined fallback: preserve the writing, editing and delivery subtasks and copy the client’s requirements onto the article task.
This is a historical narrated test. Completed articles, editorial quality, production activation, sustained volume and measured savings were not independently verified. A duplicated-HTTPS redirect still needed correction at the end of the recording. The queue provider’s name is unclear in the transcript.