How to Use the Make.com Webhook Trigger MCP in CrewAI

Q: How do I use the Make.com Webhook Trigger with my CrewAI agents?

You pass the Vinkius endpoint URL into the mcps list when you define an Agent. Your agent can then directly call the triggermakewebhook tool by name. CrewAI handles the rest.

Q: Can different agents use the Make.com Webhook Trigger for separate scenarios in CrewAI?

Yes. The webhook URL is a parameter for the triggermakewebhook tool. One agent can trigger a scenario to post on social media, while another agent in the same crew can trigger a different webhook to add a row to a database.

Connect your CrewAI agent teams to thousands of apps. This MCP server lets your agents trigger any Make.com scenario with a simple tool call.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Make.com Webhook Trigger MCP to CrewAI

Create your Vinkius account to connect Make.com Webhook Trigger to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Make.com Webhook Trigger with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Trigger Workflows from Any Agent

The `trigger_make_webhook` tool lets any agent in your crew fire off a Make.com scenario. Just give it the webhook URL and a JSON payload. Your agent decides what to do, and Make.com handles the connection to other apps. This is perfect for action-oriented agents. For example, a 'researcher' agent can find data, and once a 'writer' agent summarizes it, a final 'publisher' agent can use this tool to post the summary to a social media account through a Make.com workflow.

Decouple Agent Logic from Execution

Stop coding complex API calls inside your agents. Let them focus on reasoning and decision-making. This tool offloads the actual work of talking to external services to Make.com's visual builder. Your crew's job is just to assemble the right JSON and call `trigger_make_webhook`. If an API endpoint changes, you update the Make scenario—no need to redeploy your agents. It keeps your crew's logic clean and focused on the mission.

Build Autonomous Operations with this MCP Server

Use this tool as the final step in an autonomous process. A monitoring agent could watch a system for errors, and upon detecting one, pass the details to another agent that triggers a webhook. That webhook could create a ticket in your project management tool or send a critical alert. Because CrewAI lets agents collaborate, you can build surprisingly complex operations. This MCP server acts as the bridge, turning your crew's internal conclusions into real-world actions without any human in the loop.

Setup guide

Set up Make.com Webhook Trigger MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Make.com Webhook Trigger tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Make.com Webhook Trigger Analyst",
    goal="Access and analyze Make.com Webhook Trigger data via MCP.",
    backstory="Expert analyst with direct Make.com Webhook Trigger access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Make.com Webhook Trigger transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Make.com Webhook Trigger Analyst",
        goal="Access and analyze Make.com Webhook Trigger data via MCP.",
        backstory="Expert analyst with direct Make.com Webhook Trigger access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Make.com Webhook Trigger transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Make (Integromat). All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Make.com Webhook Trigger now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Make.com Webhook Trigger MCP in CrewAI

You pass the Vinkius endpoint URL into the `mcps` list when you define an Agent. Your agent can then directly call the `trigger_make_webhook` tool by name. CrewAI handles the rest.

The tool accepts a single JSON object as the payload. Your agent can construct this object based on its findings, then pass it to the tool. Make.com will receive that exact data structure.

Yes. The webhook URL is a parameter for the `trigger_make_webhook` tool. One agent can trigger a scenario to post on social media, while another agent in the same crew can trigger a different webhook to add a row to a database.

It sends a standard HTTPS request, so expect network latency. It's ideal for asynchronous tasks where a response time of a few hundred milliseconds to a second is fine. Don't use it for high-frequency trading or other work that needs instant execution.

This MCP server is ephemeral and runs in a V8 isolate sandbox on Vinkius. We only pass the JSON payload through to Make.com; the data is never logged or stored on our platform. Your data's security in transit is handled by HTTPS, and its security within Make.com is subject to their policies.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript