Hi Pocket team,
First of all, I really love Pocket. I’m using it every day and I’m trying to make it the center of my workflow.
I’m trying to integrate Pocket with ClickUp and I’m wondering if I’m approaching this the wrong way.
My ideal workflow is:
- I record a voice note with Pocket.
- Pocket generates the summary and action items.
- Every action item becomes its own ClickUp task.
- Each ClickUp task should contain:
- the Action Item title
- the complete Pocket summary in the description
- due date (if Pocket extracted one)
- priority (if available)
- assignee (if available)
I first tried the built-in ClickUp integration but I couldn’t find a way to include the complete summary inside every generated task.
Then I tried using Make.com:
Pocket → HTTP API → Iterators → ClickUp
Unfortunately I ran into another issue:
The API sometimes returns an empty actionItems.actions array even though the summary has already been generated.
Sometimes running the same request later returns the actions correctly, which makes me think there is an asynchronous processing step.
My questions are:
- Is the built-in ClickUp integration capable of creating one ClickUp task per Action Item while also including the complete Pocket summary?
- If not, is this planned?
- Is there a recommended API endpoint or workflow to reliably wait until Action Items are fully generated before reading them through the API?
- Is there an official Make.com example for this workflow?
I would really appreciate any guidance from the Pocket team.
Thanks!