MAKE + JODOO
AI Meeting Notes to Action Tracker with Make + Jodoo
Use Make with Jodoo to receive meeting-note webhooks, send structured action fields through an HTTP module, and keep owners, due dates, blockers, and follow-up status trackable.
VIDEO WALKTHROUGH
What happens in the demo
The video shows one meeting follow-up loop: Make receives a meeting-note webhook, the HTTP module posts to the Jodoo writeback layer, and Jodoo keeps the owner queue and follow-up record.
Meeting notes enter Make
A Custom webhook receives a synthetic customer onboarding review with meeting title, date, decisions, risks, and follow-up context.
Make posts action fields
The HTTP module sends structured action fields to the Jodoo writeback layer and receives a successful response.
Jodoo creates the record
The writeback step maps the structured fields into a Jodoo meeting action record.
Follow-up stays visible
Teams can review open actions, due-this-week work, blocked items, owner queues, and the original workflow output.
DEMO SUMMARY
Make runs the scenario, Jodoo tracks the meeting action
The walkthrough shows how a meeting summary becomes a Jodoo action record with owner, due date, priority, blocker, status, confidence, and original workflow output.
Meeting follow-up problem
Meeting decisions often stay in notes instead of becoming tracked work.
Make webhook trigger
The meeting-note payload enters the Make scenario through a Custom webhook.
HTTP writeback
Make posts the structured action fields into the Jodoo writeback step.
Jodoo action record
The test run creates a meeting action record with owner, due date, priority, blocker, and status.
Team queue
The record can move into due-date views, owner queues, and blocker review.
Reusable kit
Use the handbook, blueprint, and recipe to adapt the workflow.
PLATFORM SETUP NOTES
What is specific to Make
The Jodoo record model can stay consistent, but each agent platform has a different build style, testing view, and production handoff.
Run once review
Make is strongest when an operations builder wants to watch the Custom webhook bundle, module operations, credit use, and HTTP response before scheduling the scenario.
HTTP module handoff
The Jodoo writeback is isolated in one HTTP module, so headers, JSON body, status 200, response body, and retry behavior are easy to inspect.
Visual scenario ownership
This version fits teams that prefer Make History and a visual canvas for handoff reviews instead of node-by-node or code-first debugging.
WORKFLOW KIT
Build the same Make meeting follow-up loop
Review the field mapping, copy the Make workflow recipe, and use the Jodoo action tracker model before adapting the scenario to your own meeting source.
What your team can reuse
Make receives the meeting-note event and posts one structured action item. Jodoo keeps the durable action record: owner, due date, priority, blocker, status, confidence, and audit context.
REUSABLE WORKFLOW
The workflow decides. Jodoo keeps work moving.
- 01
Meeting source
Transcript, note app, form, webhook source, or manual test note
- 02
Make scenario
Receives the webhook, sends the HTTP writeback, and confirms status 200
- 03
Structured output
One JSON object with the fields Jodoo needs
- 04
HTTP writeback
Posts the JSON to the Jodoo writeback layer
- 05
Jodoo action record
Fields, views, owner queue, blocker status, and original output
WORKFLOW LOOP
From Make webhook to owner queue
Meeting notes arrive from a transcript, note app, form, webhook source, or manual test payload.
A Make Custom webhook receives the meeting title, date, and source notes.
A transformation, code, or agent step returns structured fields for decision summary, action item, owner, due date, priority, blocker, status, and confidence.
The Make HTTP module posts the structured result into the Jodoo writeback layer.
Jodoo creates the meeting action record and keeps original workflow output attached for review.
Teams work from owner queues, due-date views, blocked-item views, and follow-up dashboards.
FIELD MAPPING
Agent output becomes Jodoo fields
| Agent or source data | Jodoo record fields |
|---|---|
| Custom webhook bundle: meeting_title, meeting_date, source_notes | Meeting Title, Meeting Date, Source Notes |
| Make mapping panel: decision_summary, action_item | Decision Summary, Action Item |
| HTTP module JSON: owner, due_date, priority | Owner, Due Date, Priority |
| HTTP module JSON: risk_or_blocker, follow_up_status | Risk or Blocker, Follow-up Status |
| Make run output: agent_confidence, response body, operation status | Agent Confidence, Original Agent Output |
AGENT RECIPE
Prompt and structured output
Agent role
You are a meeting follow-up assistant. Read meeting notes and return one structured action item that a team can track in Jodoo.
Make instruction
Use the webhook payload as context, then return JSON fields that the Make HTTP module can map into the Jodoo writeback request.
Required output
Return meeting_title, meeting_date, source_notes, decision_summary, action_item, owner, due_date, priority, risk_or_blocker, follow_up_status, source_platform, and agent_confidence.
{
"meeting_title": "Customer onboarding risk review",
"meeting_date": "2026-06-04 10:30",
"decision_summary": "Keep the June 10 training date if the import sample is approved this week.",
"action_item": "Confirm data import owner and send the import sample approval request.",
"owner": "Maya Chen",
"due_date": "2026-06-05",
"priority": "High",
"risk_or_blocker": "Training date may slip if the import sample is not approved by Friday.",
"follow_up_status": "Needs owner confirmation",
"source_platform": "make",
"agent_confidence": "0.86"
}JODOO STARTER APP
AI meeting action tracker starter app
Use the field model, suggested views, and automation rules when you adapt the Make meeting action workflow for your team.
Included fields
- Meeting title
- Meeting date
- Source notes
- Decision summary
- Action item
- Owner
- Due date
- Priority
- Risk or blocker
- Follow-up status
- Source platform
- Agent confidence
- Original workflow output
Suggested views
- Open action items
- Due this week
- Blocked or at risk
- Owner queue
- All meeting actions
Automation rules
- Create a Jodoo meeting action record after Make returns structured output.
- Move high-priority or blocked actions into a review queue.
- Notify the owner when the due date is near.
- Keep the original workflow output in the audit trail.
ROLLOUT CHECKLIST
What to confirm before production
- Choose the meeting source and decide which transcripts are safe to process.
- Keep the output contract narrow before adding more action items per meeting.
- Map every output field to a stable Jodoo field.
- Test with synthetic meeting notes before using production calls.
- Create review queues for blocked items, missing owners, and low-confidence results.
- Add Make error handling and owner notifications after the field model is stable.
IMPLEMENTATION REFERENCES
Keep the setup details for your team
WORKFLOW
From Make webhook to tracked action item
Make is useful when teams want a visual automation path. The Custom webhook and HTTP module make the trigger and Jodoo writeback easy to inspect before production use.
Meeting notes arrive from a transcript, note app, form, webhook source, or manual test payload.
A Make Custom webhook receives the meeting title, date, and source notes.
A transformation, code, or agent step returns structured fields for decision summary, action item, owner, due date, priority, blocker, status, and confidence.
The Make HTTP module posts the structured result into the Jodoo writeback layer.
Jodoo creates the meeting action record and keeps original workflow output attached for review.
Teams work from owner queues, due-date views, blocked-item views, and follow-up dashboards.
JODOO RECORD
What Jodoo stores
Jodoo keeps the follow-up fields the team needs after the Make run: meeting title, decision summary, action item, owner, due date, priority, blocker, status, and confidence.
TEST RUN
A Make test run wrote the meeting action into Jodoo
The screenshots use synthetic meeting notes and show the Make scenario, a successful HTTP module response, and the Jodoo table row created by the workflow.
Make workflow configuration
A Make Custom webhook and HTTP module form the meeting-note action tracking flow.
Successful Make run
The HTTP module completed with status 200 after posting the meeting action to Jodoo.
Jodoo writeback
The action item, owner, due date, priority, blocker, and status were written into Jodoo.
FAQ
Common questions
Answers about using agent platforms with Jodoo records, workflows, and app templates.
Was this Make workflow tested end to end?
Yes. The proof run used synthetic meeting notes, completed the Make HTTP module with status 200, and created a meeting action record in Jodoo.
Does this require a paid Make plan?
The test used a compact free-plan-friendly scenario shape. Production use may need a paid plan depending on operations volume, scheduling, connected apps, and error-handling needs.
Can the meeting notes come from a transcript tool?
Yes. The source can be a transcript, note app, form, webhook, or manual test payload as long as the workflow sends predictable text into the Make scenario.
What does Jodoo store after Make runs?
Jodoo stores the meeting title, date, source notes, decision summary, action item, owner, due date, priority, blocker, follow-up status, confidence, and original output.
How is this different from the Zapier Agents version?
The Jodoo record model is similar, but this page shows Make-specific setup: Custom webhook, HTTP module, Run once proof, status 200 response, and Make production caveats.
NEXT STEP
Turn meeting notes into operational follow-up
Start with one meeting action item, then adapt the same pattern to onboarding calls, project reviews, support escalations, and vendor follow-up.