Integration Validation

See what is worth validating before you connect it.

Each lead shows a primary source, observed date, data boundary, and next check. A source review confirms that documentation exists; it does not prove compatibility, security, or production readiness for your workflow.

Primary source linkedObserved date shownTest still required

How to use it

Turn a lead into a documented validation.

Open the primary source, map it to a real workflow, check permissions and data, then record the test result and next review date.

1. Open the primary source

Confirm it comes from the product owner and record the observed date.

2. Map the real job

Define the exact input, action, and output this capability must support.

3. Check permissions and data

Record scopes, sensitive fields, credential ownership, and human approval.

4. Run and record a test

Save results, failures, stop conditions, and the next review date.

Validation leads

Move from source review to a real test.

These records link to primary sources. An adoption decision still requires a test against your plan, region, permissions, and data.

SignalObjectStatusEvidence & next action

Claude Code MCP connectionsClaudeVerification in progress

Anthropic documents MCP connections for Claude Code. WoooAIHub has reviewed the source, but has not independently tested a production workflow.

Evidence: Anthropic Claude Code documentation
Signal type: Primary-source review
Last checked: 2026-07-23
Data boundary: Confirm connector permissions, workspace data access, and human approval points before operational use.
Next action: Review current primary documentation and record plan, permission, and availability limits.

Zapier MCP access and usageZapierVerification in progress

Zapier documents MCP servers, tool calls, and usage accounting. WoooAIHub has reviewed the source, but has not tested a live business workflow.

Evidence: Zapier Help Center
Signal type: Primary-source review
Last checked: 2026-07-23
Data boundary: Confirm connected-app scopes, credential ownership, transferred fields, and approval requirements.
Next action: Verify current agent and MCP documentation against a bounded business-app workflow.

GPT workspace access controlsChatGPTVerification in progress

OpenAI documents workspace controls for GPT access, sharing, and governance. Availability still depends on plan and workspace permissions.

Evidence: OpenAI Help Center
Signal type: Primary-source review
Last checked: 2026-07-23
Data boundary: Confirm workspace roles, connector scopes, retained data, and review ownership for each workflow.
Next action: Check current workspace-agent availability, plan requirements, and data-control documentation.

Cursor Agent tools and approval controlsCursorVerification in progress

Cursor documents Agent tools for search, edits, terminal commands, MCP, and configurable auto-run behavior. This is not production-readiness evidence.

Evidence: Cursor documentation
Signal type: Primary-source review
Last checked: 2026-07-23
Data boundary: Confirm repository access, secret handling, command approval, generated-code review, and deployment ownership.
Next action: Run a bounded repository task and document permissions, review gates, failures, and rollback behavior.

Agent workflow templates

Structured workflows are the adoption bridge.

Use workflow objects to define inputs, approvals, outputs, and QA before considering automation.

View all recipes

Reusable template