Yadulink and MCP workflows should let teams inspect the plan before action: search criteria, exclusions, retained profiles, proposed messages, and human approvals.
Outreach dry-run
Use preview to frame a LinkedIn search, a company-to-people pipeline, a sequence, or an email campaign before execution. The goal is to detect broad filters, poor ICP fit, and duplicates before creating the final list.
Outreach dry-run
A dry-run should not send a message, contact a prospect, publish an action, or consume a campaign as if it had launched. It should return a readable plan, risks, and the required decisions.
Outreach dry-run
Once the plan is approved, Yadulink can import the list, create a sequence, or connect events to CRM. The transition should remain explicit so the user knows what changes status.
Verified facts
PurposeYadulink and MCP workflows should let teams inspect the plan before action: search criteria, exclusions, retained profiles, proposed messages, and human approvals.
Workflow proofUse preview to frame a LinkedIn search, a company-to-people pipeline, a sequence, or an email campaign before execution. The goal is to detect broad filters, poor ICP fit, and duplicates before creating the final list.
Assistant promptHelp me audit a Yadulink workflow before launch: search criteria, exclusions, no-send dry-run, human approval, and transition to execution.
Verification method
Docs linking
AI agent
Configure the Yadulink AI agent before delegating LinkedIn prospecting.
MCP tools
Understand which Yadulink tools to expose to an AI assistant.
MCP
Connect Yadulink to Claude, ChatGPT, or an MCP-compatible assistant.
Webhook events
Choose which Yadulink events should leave the app.
AI prompts
Ready-to-adapt prompts for running Yadulink with AI.
