3.1 Make.com Setup

Make.com is the automation platform RevGravy uses to connect tools together and trigger workflows automatically. It is the engine behind multiple live automations like: agenda drafts, recap drafts, onboarding, SoCo and cycle planner drafts.

Think of Make.com as a visual pipeline builder. Each pipeline is called a Scenario. When something happens in one tool (like a meeting ending in Fellow.ai), Make.com detects it and runs a series of steps across multiple tools automatically.

Access: Go to make.com and log in with the RevGravy team account (admin@revgravy.com). You need to use Google Login.

Once logged in, you will see the Workspaces dashboard. All active RevGravy scenarios are inside the RevGravy 2ND PLAN organization workspace.

Do not create scenarios outside this workspace.

Scenario naming convention:

All scenarios follow this naming format:

Do not rename scenarios without updating this document. Renaming breaks the audit trail.

Key concepts:

Trigger: The event that starts the scenario. For RevGravy automations this is either a Fellow.ai webhook (meeting completed) or a HubSpot deal stage change.

Module: Each step inside a scenario. Modules connect to external tools (Fellow, HubSpot, Slack, Google Docs, the Anthropic API). They run in sequence.

Execution log: The history of every time a scenario has run. If something breaks, check the execution log first. It shows exactly which module failed and why. Find it by clicking a scenario → History tab.

Webhook: A URL that another tool (like Fellow.ai) sends data to when something happens. RevGravy's automations use Fellow webhooks. If a webhook stops working, check the Fellow.ai integration settings first.

What to do if a scenario is broken

1. Go to make.com → open the broken scenario
2. Click History tab — find the most recent failed run (red icon)
3. Click the failed run — identify which module shows the error
4. Read the error message. Most common causes: API key expired, wrong field mapped, Fellow webhook timed out
5. If you cannot fix it: screenshot the error, DM Phil in Slack, do NOT turn off the scenario