Saleslumen

View saved version →

---
name: saleslumen-apps-script
description: >-
  Author Saleslumen Apps Script projects via MCP: projects, file content,
  versions, deployments, metrics, and process history. Use when the user wants
  to create or edit a script project, cut a version, or manage a deployment.
  Do not use for inbox email, campaign enrollment, or running a function.
---

# Saleslumen Apps Script

Use the Saleslumen MCP connector to author Script projects. Keep the conversation natural; read and update project files with tools.

## Concepts

A project is identified by `script_id`. Content version `0` is the editable draft. Positive version numbers are immutable snapshots.

Content is a full file set (`SERVER_JS`, `HTML`, `JSON`), including `appsscript.json` for runtime, timezone, libraries, and `enabledServices`.

A deployment points at a numbered version (not draft `0`).

Processes are the user-facing run history. Use them to answer whether a past run finished.

This plugin does not run a script function, fetch callable contracts, or call a Marketplace operation. Author the project here. Execution stays in Saleslumen.

## Workflow

1. Clarify the goal (create, edit, version, deploy, metrics, or process history).
2. Read the project and `apps_script_get_content` before you overwrite files.
3. Ship with update content, then create version, then create or update deployment.
4. Confirm with the user before content replace and delete.
5. Report the project, version, or deployment that changed.

## Tools

| Task | Tools |
| --- | --- |
| Projects | `apps_script_list_projects`, `apps_script_create_project`, `apps_script_get_project`, `apps_script_update_project`, `apps_script_delete_project` |
| Content | `apps_script_get_content`, `apps_script_update_content` |
| Metrics | `apps_script_get_metrics` |
| Versions | `apps_script_create_version`, `apps_script_get_version`, `apps_script_list_versions` |
| Deployments | `apps_script_create_deployment`, `apps_script_get_deployment`, `apps_script_update_deployment`, `apps_script_delete_deployment`, `apps_script_list_deployments` |
| Processes | `apps_script_list_processes`, `apps_script_list_script_processes` |

## Guidance

- `apps_script_update_content` replaces the whole file set and requires `draft_etag` from `apps_script_get_content`. Send every intended file.
- Deploy only numbered versions.
- Stay in the Apps Script tools for this skill.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: saleslumen-campaigns
description: >-
  Manage Saleslumen campaigns via MCP: campaigns, people, variables, sequences,
  rules, schedules, deliveries, and suppressions. Use when the user wants
  outreach campaigns, enrollments, or sequence steps. Do not use for inbox
  email, workflows, or running a people script.
---

# Saleslumen Campaigns

Use the Saleslumen MCP connector for campaign setup and enrollment. Keep the conversation natural; change structure and people with tools.

## Concepts

A campaign holds settings, variables, people, one immutable entry sequence, additional sequences, and rules. Variables define the schema; people hold values for those variables. Create already includes `given_name` and `family_name`.

Sequences are trigger-free `SEND_EMAIL` trees. `campaigns_create` returns `campaign` and `entry_sequence`. The entry sequence is named Main. Its first email stays `START_NEW`. Later steps are `CONTINUE`. A non-entry sequence may start `START_NEW` or `CONTINUE`. Enabled `START_NEW` variants require `subject`. `CONTINUE` variants omit `subject`. `body_document` is `schema_version` 1 and `doc`. Omit step and variant names on create.

Rules are a separate resource. A rule matches one event type: `MESSAGE_OPENED`, `MESSAGE_CLICKED`, `MESSAGE_REPLIED`, `MESSAGE_REPLY_SENT`, `THREAD_LABEL_ADDED`, `THREAD_LABEL_REMOVED`, or `SEQUENCE_COMPLETED`. `srl_expression` is Saleslumen Rule Language. Priority is unique within the event type; lower runs first. Actions are `ENTER_SEQUENCE` (with `target_sequence`), `RESUME_SEQUENCE`, `STOP`, and `CANCEL_PENDING_TRANSITION` (`delay_seconds` 0). Rule changes apply to future events.

`campaigns_get_task` and `campaigns_get_operation` report async work. Parent statuses are `PENDING`, `PROCESSING`, `RETRYING`, `COMPLETED`, and `FAILED`. Poll until `COMPLETED` or `FAILED`. Treat `RETRYING` as still in progress.

This plugin does not run a campaign people script.

## Workflow

1. Clarify the goal (settings, people, variables, sequences, rules, metrics, deliveries, or task status).
2. Read with `campaigns_list` / `campaigns_get` before you change an existing campaign. A create does not need a prior read.
3. `campaigns_create` returns a draft and its entry sequence. Add other sequences with `campaigns_create_sequence`. `campaigns_update_sequence` replaces that sequence's display name and step tree. There is no step tool and no sequence trigger.
4. Write a rule's `srl_expression` in SRL; do not substitute prose.
5. Confirm with the user before delete, `campaigns_set_variables`, archive, unsubscribe, and stop.
6. Summarize the new resource names and the next useful step.

## Tools

| Task | Tools |
| --- | --- |
| Campaigns | `campaigns_list`, `campaigns_create`, `campaigns_get`, `campaigns_update`, `campaigns_delete`, `campaigns_archive`, `campaigns_unarchive`, `campaigns_activate`, `campaigns_pause`, `campaigns_resume`, `campaigns_complete` |
| Variables and senders | `campaigns_set_variables`, `campaigns_set_sender_accounts` |
| Metrics | `campaigns_get_metrics` |
| People | `campaigns_list_people`, `campaigns_create_person`, `campaigns_get_person`, `campaigns_update_person`, `campaigns_delete_person`, `campaigns_batch_delete_people`, `campaigns_import_people`, `campaigns_pause_person`, `campaigns_resume_person`, `campaigns_unsubscribe_person`, `campaigns_stop_person`, `campaigns_list_person_activity` |
| Sequences | `campaigns_list_sequences`, `campaigns_create_sequence`, `campaigns_get_sequence`, `campaigns_update_sequence`, `campaigns_delete_sequence`, `campaigns_preview_sequence` |
| Rules | `campaigns_list_rules`, `campaigns_create_rule`, `campaigns_get_rule`, `campaigns_update_rule`, `campaigns_delete_rule` |
| Schedules | `campaigns_list_schedules`, `campaigns_create_schedule`, `campaigns_get_schedule`, `campaigns_update_schedule`, `campaigns_delete_schedule` |
| Deliveries and suppressions | `campaigns_list_deliveries`, `campaigns_get_delivery`, `campaigns_resolve_unkno

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: saleslumen-emails
description: >-
  Manage Saleslumen email via MCP: messages, threads, drafts, labels, accounts,
  and address discovery. Use when the user wants to read, send, draft, trash,
  label, or find email in Saleslumen. Do not use for campaigns, workflows, or
  Apps Script.
---

# Saleslumen Emails

Use the Saleslumen MCP connector for mailbox work. Keep the conversation natural; call tools to act.

## Concepts

Tool arguments are snake_case. Fields inside a message, draft, or label object stay Emails JSON: `accountId`, `threadId`, `labelIds`, `payload`, `raw`, and `scheduleTime`.

A thread is a conversation. A draft wraps an unsent message. Labels categorize messages and threads.

An account is an org mailbox. `emails_list_accounts` tells you which mailboxes exist. Put the chosen account id in the message `accountId`.

`emails_discover` takes `domain` and `name`. Report what the tool returns; do not invent addresses.

## Workflow

1. Clarify the goal (read, reply, draft, send, label, trash, discover, or account lookup).
2. Resolve identifiers with list/get before you change anything. Filter lists with `account_ids`, `query`, or `label_ids`.
3. For replies and forwards, call `emails_generate_quoted_content` with `reply_to_message_id` and `quote_type` (`reply` or `forward`), then draft or send.
4. When composing, pass a `message` object and a `request_id` UUID. Inside the message set `accountId`, and `payload` or `raw`. Set `scheduleTime` (epoch milliseconds) on that message only if the user asks to schedule. `emails_send_draft` takes the same `request_id`. Reuse it on a retry.
5. Confirm with the user before send and before permanent delete.
6. Summarize the result in plain language.

## Tools

| Task | Tools |
| --- | --- |
| Messages | `emails_list_messages`, `emails_get_message`, `emails_get_attachment` |
| Send | `emails_send_message`, `emails_generate_quoted_content` |
| Message lifecycle | `emails_trash_message`, `emails_untrash_message`, `emails_delete_message`, `emails_modify_message` |
| Threads | `emails_list_threads`, `emails_get_thread`, `emails_trash_thread`, `emails_untrash_thread`, `emails_modify_thread`, `emails_delete_thread` |
| Labels | `emails_list_labels`, `emails_get_label`, `emails_create_label`, `emails_update_label`, `emails_delete_label` |
| Drafts | `emails_list_drafts`, `emails_get_draft`, `emails_create_draft`, `emails_update_draft`, `emails_send_draft`, `emails_delete_draft` |
| Accounts | `emails_list_accounts`, `emails_get_account`, `emails_create_account`, `emails_update_account`, `emails_delete_account` |
| Discovery | `emails_discover` |

## Guidance

- `emails_update_label` renames a label. There is no separate patch tool.
- Prefer trash over permanent delete unless the user asks to purge.
- Stay in the Emails tools for this skill.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: saleslumen-workflows
description: >-
  Build and run Saleslumen workflows via MCP: create and update structural
  drafts, publish, activate, and manage executions. Use when the user wants a
  workflow graph, a version, or a workflow run. Do not use for inbox email,
  campaigns, or naming a script function or marketplace operation inside the
  graph.
---

# Saleslumen Workflows

Use the Saleslumen MCP connector to define structural graphs and run workflows that already exist. Keep the conversation natural; push workflow JSON and manage executions with tools.

## Concepts

A workflow has metadata and append-only versions. Create seeds the first version. Update appends a draft. Publish makes a version current. Revert copies a past published definition into a new draft.

Executions pin a version and run asynchronously. Status is a number: `1` ACTIVE, `2` PAUSED, `3` COMPLETED, `4` ERROR, `5` CANCELLED.

`workflows_create` and `workflows_update` accept structural nodes and connections. They reject a node that names a script function or a marketplace operation. Do not put either in the graph. Author those calls in Saleslumen, then start the saved workflow by id.

`agent` and `wait` pause the run. Resume continues at the main-flow successor; it does not re-execute the pause node.

## Workflow

1. Clarify the goal (design, publish, activate, run, resume, cancel, or inspect).
2. Read with `workflows_list` / `workflows_get` before you change a graph.
3. Ship a structural draft with create or update, then publish, then activate, then `workflows_start_execution`.
4. Confirm with the user before publish, activate/deactivate, start/resume/cancel, and delete.
5. Poll with `workflows_get_execution` or `workflows_list_executions`. Resume only when status is `2`.

## Tools

| Task | Tools |
| --- | --- |
| Definitions | `workflows_list`, `workflows_get`, `workflows_create`, `workflows_update`, `workflows_delete` |
| Versions | `workflows_publish`, `workflows_revert_version`, `workflows_get_history`, `workflows_get_version` |
| Lifecycle | `workflows_activate`, `workflows_deactivate` |
| Executions | `workflows_start_execution`, `workflows_resume_execution`, `workflows_cancel_execution`, `workflows_get_execution`, `workflows_list_executions` |

## Guidance

- Default start (no `version_id`) requires Publish then Activate. `version_id` is a preview and may run a draft while inactive.
- Keep graphs acyclic and include `start` and `end`.
- Edit Script source with the Apps Script skill. Do not name a script function or a marketplace operation in a workflow node.

Referenced files: 1 — file references are metadata, not package contents.