Make.com¶

Purpose¶

Primary automation and workflow orchestration layer for the eco|monetize™ stack. "Not Zapier" per Rick's decision — Make.com is the canonical automation choice for all integrations.

How we use it¶

Make.com scenarios orchestrate data flows between tools (Airtable → Monday.com sync, signal extraction pipelines, webhook → LLM → write-to-vault flows, etc.). Active scenario examples include the ERI-08 S3 signal extraction pipeline (scenario ID 4352050) and planned ChatGPT → Obsidian auto-capture pipeline (design pack at /Users/rhartley/Downloads/ChatGPT to Obsidian/).

Setup & credentials¶

MCP server installed (mcp__claude_ai_Make__*) — supports scenario management, execution tracking, data store operations, hook configuration, and blueprint validation. Credentials and API keys stored in 1Password (path TBD). Important UI change: "Connections" was renamed to "Credentials" in late 2025 redesign — path is now Credentials → Connections tab in the UI.

Owner¶

code.platform — as the primary integrations owner in the v1.2 roster. code.platform absorbed the former code.integrations role during v1.2 compression.

[[code.platform]] — primary owner
/Claude/scripts/integrations/monday/ — related sync scripts that Make.com scenarios may trigger or ingest
Monday.com + Airtable + Slack — primary integration targets
ERI-08 S3 scenario 4352050 — active signal extraction pipeline

Notes¶

Prefer API/MCP over manual UI guides — agents tend to give outdated Make.com UI instructions (Rick's standing feedback)
Field mapping pattern: Claude outputs signal_text/context_summary but Airtable expects signal_value/evidence_text — mapped in Make.com as translation layer, extraction prompt updates pending
HTTP timeout: 120s for debug, reduce to 60s for production