Automation Platforms

Connect workflow automation platforms to graph8 using the Model Context Protocol (MCP). Build powerful automations with your campaigns, accounts, and intelligence data.

Tip

Headless automation platforms authenticate to the remote graph8 MCP server with a personal or org API key sent as an Authorization: Bearer header — not the interactive browser OAuth flow used by Claude Desktop or Cursor. There is no session_id to copy.

Supported Platforms

n8n

Open-source workflow automation. Supported now.

Setup Guide

Zapier

No-code automation platform. Planned.

Integration coming soon

Make

Visual automation builder. Planned.

Integration coming soon

Why Use MCP for Automation?

Benefit	Description
Unified Access	One connection for all graph8 data
Real-Time Data	Always current campaigns, accounts, and intelligence
Secure	Uses your permissions, revocable anytime
Standardized	Same MCP protocol across all platforms

Common Automation Use Cases

Marketing Operations

• Campaign Sync — Push new campaigns to project management tools
• Content Distribution — Auto-share campaign content to social media schedulers
• Performance Tracking — Sync campaign metrics to analytics dashboards

Sales Enablement

• CRM Enrichment — Add graph8 intelligence to CRM records
• Deal Alerts — Notify reps when company intelligence is updated
• Pipeline Sync — Keep deal data synchronized across systems

Research & Intelligence

• Competitive Alerts — Trigger actions when competitive intel is updated
• Company Monitoring — Watch for changes in target companies
• Report Distribution — Auto-send intelligence reports to stakeholders

Getting Started

Step 1: Get an API key

1. Go to Profile → Developer in graph8 for a personal API key, or Settings → API (admin) for an org API key.
2. Copy the key — it starts with g8_.
3. Store it in your automation platform’s credential manager, not inline in a node.

Step 2: Choose Your Platform

Platform	Status	Guide
n8n	Available	Setup Guide
Zapier	Coming Soon	—
Make	Coming Soon	—

Step 3: Configure the Connection

Point the platform at the remote graph8 MCP endpoint and send your API key as a Bearer header:

POST https://be.graph8.com/mcp/
Authorization: Bearer YOUR_G8_API_KEY
Content-Type: application/json

The body is standard MCP JSON-RPC — see the n8n Setup Guide for a full request example.

Available Tools

All automation platforms have access to the graph8 MCP tools your role grants. Tool names are prefixed with g8_. A few common ones:

Note

Exact tool names are mode-dependent. When the endpoint runs in combined all mode, GTM tools are namespaced — e.g. g8_gtm_list_campaigns instead of g8_list_campaigns. The unprefixed names below are the canonical form; confirm the exact names your role grants in the MCP Tool Reference.

Campaigns

Tool	Description
g8_list_campaigns	List campaigns with an optional status filter
g8_get_campaign	Get details for a specific campaign

Companies

Tool	Description
g8_search_companies	Search companies already in your CRM
g8_find_companies	Search graph8’s company index for new accounts
g8_lookup_company	Enrich a single company by domain or name

Deals

Tool	Description
g8_get_deals	List pipeline deals
g8_get_deal	Get deal details

Intelligence

Tool	Description
g8_list_intelligence_data	List intelligence data for the org
g8_tool_search	Discover and activate other tools by keyword

For the complete list, see the MCP Tool Reference.

Best Practices

Credentials & keys

graph8 API keys are long-lived — there is no 24-hour session to refresh.

• Store keys in your platform’s credential manager, referenced by header (Authorization: Bearer g8_...)
• Set up monitoring for 401 authentication failures
• Rotate or revoke keys from Profile → Developer or Settings → API; revocation is immediate

Rate Limiting

• Add delays between high-volume API calls
• Batch operations where possible
• Cache frequently accessed data

Error Handling

• Check for authentication errors and refresh session
• Handle rate limit responses with exponential backoff
• Log failures for debugging

Tip

For production automations, consider setting up a dedicated service account in graph8 Studio with appropriate permissions.

Zapier Integration (Coming Soon)

We’re working on a native Zapier integration that will include:

• Triggers: Campaign created, Account updated, Intelligence ready
• Actions: Create campaign brief, Search accounts, Get intelligence
• Searches: Find campaigns, Find accounts, Find deals

Join the waitlist by contacting [email protected].

Make Integration (Coming Soon)

The Make (formerly Integromat) integration will offer:

• Visual scenario builder with graph8 modules
• Real-time webhooks for instant triggers
• Advanced data transformation tools

Frequently Asked Questions

Which automation platform should I choose?

n8n is available now and offers the most flexibility. Choose Zapier (coming soon) for no-code simplicity, or Make for visual workflow building. All will use the same MCP protocol.

Can I use the REST API instead of MCP?

Yes, graph8 Studio has a full REST API. MCP is optimized for AI-native tools and conversational interfaces. Use REST API for traditional integrations and MCP for AI workflows.

How do I migrate automations between platforms?

MCP tools are standardized, so the same operations work across platforms. You’ll need to rebuild the workflow logic in each platform, but the graph8 calls remain identical.

Is there a way to batch multiple operations?

Currently, each MCP call is individual. For bulk operations, loop through items in your automation platform. Consider adding delays to avoid rate limits.

How do I report issues with the MCP integration?

Contact [email protected] with details about your platform, the operation attempted, and any error messages. Never share your API key.

Related

• MCP Overview
• n8n Setup Guide
• What You Can Ask