sendlane-automation
by ComposioHQsendlane-automation helps automate Sendlane tasks through Composio Rube MCP, with tool discovery, connection checks, and schema-first workflows for Email Campaigns.
This skill scores 66/100, which means it is acceptable for directory listing but should be presented as a lightweight MCP workflow guide rather than a fully developed automation package. Directory users get enough clarity to understand when to use it and how an agent should begin Sendlane operations, but they should expect limited Sendlane-specific examples and no supporting assets beyond SKILL.md.
- Clear trigger and scope: the frontmatter and title identify Sendlane automation through Composio/Rube MCP.
- Operational prerequisites are explicit, including the need for Rube MCP, an active Sendlane connection, and calling RUBE_SEARCH_TOOLS first for current schemas.
- Provides a reusable execution pattern for tool discovery, connection checking, and schema-aware task execution, reducing guesswork versus a generic prompt.
- No support files, scripts, references, or README are provided beyond a single SKILL.md, so adoption depends entirely on the embedded instructions.
- The workflow guidance appears mostly generic to Rube MCP discovery and connection management rather than offering many concrete Sendlane-specific automations or edge-case handling.
Overview of sendlane-automation skill
What sendlane-automation is for
sendlane-automation is a Claude skill for automating Sendlane work through Composio’s Rube MCP server. It is designed for Email Campaigns and lifecycle marketing tasks where the assistant needs to discover the current Sendlane tool schema, confirm an active Sendlane connection, and then run the right MCP tools instead of guessing API fields.
Best-fit users and jobs
This skill is a good fit for marketers, operators, and technical growth teams who already use Sendlane and want an AI assistant to help with campaign, contact, list, tag, or automation-related operations. It is most useful when your task depends on live Sendlane access and current tool definitions, not just writing email copy or planning strategy.
Key differentiator: tool discovery first
The main value of the sendlane-automation skill is its “search tools first” workflow. Before attempting an action, the assistant should call RUBE_SEARCH_TOOLS for the specific Sendlane use case, inspect returned schemas and pitfalls, then execute the selected tool. This reduces failed calls caused by stale field names, missing required inputs, or incorrect assumptions about available Sendlane operations.
Adoption considerations
The skill is lightweight: the repository path contains a single SKILL.md and no helper scripts, references, or local examples. That makes it easy to inspect, but it also means successful use depends on your MCP setup, Sendlane authorization, and prompt specificity. Install it if you want a repeatable operating pattern for Rube MCP Sendlane tasks; do not expect a full campaign management application.
How to Use sendlane-automation skill
sendlane-automation install and setup context
Install the skill from the Composio skills repository with your skills-compatible client, for example:
npx skills add ComposioHQ/awesome-claude-skills --skill sendlane-automation
Then configure Rube MCP in your AI client by adding the MCP endpoint:
https://rube.app/mcp
Before asking the assistant to perform Sendlane work, verify that RUBE_SEARCH_TOOLS is available. Next, use RUBE_MANAGE_CONNECTIONS with toolkit sendlane. If the returned connection is not ACTIVE, follow the auth link and complete Sendlane authorization before running workflows.
Inputs the skill needs from you
For reliable sendlane-automation usage, provide the operational goal and the exact business context. Useful inputs include:
- Target object: contact, list, tag, campaign, automation, segment, or event
- Desired action: create, update, search, add, remove, export, or trigger
- Identifiers you already know: email address, list ID, campaign ID, tag name, automation ID
- Constraints: do not email customers, dry-run first, limit to a segment, avoid duplicates
- Success criteria: “return updated contact IDs” or “show the final tool response”
A weak prompt is: “Update my Sendlane contacts.”
A stronger prompt is: “Use sendlane-automation for Email Campaigns. Search Rube tools for the current Sendlane schema, confirm my Sendlane connection is active, then find contacts with tag webinar-registered and add them to the list named March Nurture. Ask before making changes if more than 500 contacts match.”
Practical workflow for real tasks
A good sendlane-automation guide workflow is:
- Ask the assistant to invoke the skill for a specific Sendlane task.
- Require
RUBE_SEARCH_TOOLSfirst with your use case, not a generic query. - Confirm the Sendlane connection through
RUBE_MANAGE_CONNECTIONS. - Review the selected tool slug, required fields, and execution plan.
- Run read-only or search actions before write actions when possible.
- Execute the write operation only after required IDs and scopes are clear.
- Ask for a concise summary of changed records and any failed items.
This sequence matters because marketing systems often contain similarly named lists, tags, and automations. Searching first prevents the assistant from inventing tool inputs or applying changes to the wrong object.
Repository files to read first
Start with composio-skills/sendlane-automation/SKILL.md. It contains the important setup, prerequisites, tool discovery pattern, and core workflow. There are no README.md, metadata.json, rules/, resources/, or scripts/ files in this skill path, so the SKILL.md is the source of truth. For tool-level details, follow the linked Composio Sendlane toolkit documentation and rely on live RUBE_SEARCH_TOOLS results for schemas.
sendlane-automation skill FAQ
Is sendlane-automation only for email campaign creation?
No. The skill is positioned for Sendlane operations through Rube MCP, which may include campaign-adjacent work such as managing contacts, lists, tags, or automations depending on the tools currently exposed by Composio. For pure copywriting, a normal prompt may be enough. For live Sendlane actions, this skill is more appropriate.
How is it better than an ordinary prompt?
An ordinary prompt can describe what to do, but it may guess Sendlane API fields or skip authentication checks. The sendlane-automation skill instructs the assistant to discover current tool schemas with RUBE_SEARCH_TOOLS and check the Sendlane connection before execution. That makes it safer for operational work where wrong fields or stale assumptions cause failures.
Is this beginner-friendly?
It is beginner-friendly if you are comfortable authorizing Sendlane through Rube MCP and giving clear task instructions. It is not a no-code dashboard. Beginners should start with read-only tasks such as searching contacts, listing available tools, or checking connection status before asking the assistant to modify audiences or campaigns.
When should I not use this skill?
Do not use it when you lack an active Sendlane account, cannot connect Rube MCP, or only need strategic advice. Also avoid write operations when you cannot provide clear identifiers or approval rules. If your task affects subscribers at scale, ask the assistant to preview matches and confirm counts before executing changes.
How to Improve sendlane-automation skill
Make prompts schema-aware and outcome-specific
The best improvement to sendlane-automation results is stronger input. Instead of asking for a broad action, state the exact outcome and require tool discovery:
“Use sendlane-automation. First run RUBE_SEARCH_TOOLS for ‘add existing contacts with a specific tag to a Sendlane list.’ Then check the Sendlane connection. If the list or tag is ambiguous, show options before writing. After execution, summarize successes, failures, and skipped contacts.”
This gives the assistant a path, a safety rule, and a reporting format.
Prevent common failure modes
Common issues include inactive Sendlane connection, ambiguous list or tag names, missing contact identifiers, and assuming a tool supports a field that is not in the current schema. Reduce these failures by asking for: connection status, selected tool slug, required fields, and a confirmation step before bulk changes. For sensitive Email Campaigns work, request a dry run or read-only lookup first.
Iterate after the first output
After the first tool search or execution result, refine the task with the returned schema instead of rephrasing generically. If the tool requires IDs, ask the assistant to search for the relevant object IDs. If a write action fails, provide the error and ask it to re-check the schema and known pitfalls from RUBE_SEARCH_TOOLS. Treat each MCP response as new context for the next step.
Extend the skill for team use
If your team uses sendlane-automation regularly, consider adding local documentation outside the upstream skill: approved naming conventions, safe audience limits, required approval steps, campaign QA checklists, and examples of common Sendlane workflows. The upstream skill gives the Rube MCP operating pattern; team-specific rules make the automation safer and more consistent.