Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,13 @@ prints JSON (indented; compact with `--json`) and says what happened in a stable
| `reply inbox mark-read <thread-id>` · `reply inbox mark-unread <thread-id>` | → `read` / `unread` |
| `reply account list [--channel email\|linkedin]` | the email and LinkedIn accounts a send can go from, whose each is, and the state of each |
| `reply schedule list` | the sending schedules the account can use, each with its time zone and its windows by weekday |
| `reply account connect --channel email --provider gmail\|office365 [--name N]` · `--channel linkedin --name N` | a link that connects one new account, for the person who signs in to open → `link`, `expires_at`, `pending_id` |
| `reply account reconnect <id> --channel email\|linkedin` | a link that reconnects an account that lost its connection → `link` |
| `reply account pending [--channel email\|linkedin]` | the connection links made and not used yet, without the links |
| `reply account limits <id> --channel email\|linkedin [--daily N] [--set …]` | read an account's sending limits, or change some of them |
| `reply account pause <id> --channel linkedin` · `resume <id> --channel linkedin` | → `inactive` / `active`, toggled only when it is not already so |
| `reply account unblock <id>` | let a mailbox its provider stopped from sending pick its sequences back up → `unblocked` |
| `reply account delete <id> --channel email\|linkedin --yes [--force]` | → `deleted`; without `--yes` nothing is sent |

`<contact>` is exactly one of `--contact <json>|@file|-`, `--email <address>` (with `--first-name`,
`--last-name`, `--company`, `--title`), or `--contact-id <id>`. The JSON takes the same fields
Expand Down Expand Up @@ -512,6 +519,49 @@ For `inbox reply`, read the thread with `reply inbox get` before trying again. F
`sequence list --name -` first. Every other work command can simply be run again; a `contact delete`
repeated after its first one took effect answers `contact.not_found`.

**Connecting accounts.** `account connect` and `account reconnect` print a link for the person who
signs in to the account: they open it in a browser and sign in on Google's, Microsoft's or LinkedIn's
own page, so no password passes through the CLI. The link is a credential for whoever holds it. It is
printed once, in the stdout field `link`, and never on stderr, in a `--verbose` trace (where it reads
`<link redacted>`), in an error or in a log. A connection link connects one account, works once and
expires, and the attempt is listed by `account pending` until the person finishes; then the account
is in `account list`. An email link needs `--provider`; a reconnect takes the provider from the
mailbox, and the person must sign in with the same address. A LinkedIn connect needs `--name`, which
Reply lists the pending account under.

A Reply without one-mailbox email links answers that route with a 404 and no code. The email
commands then refuse with `email_link.not_available` (exit 1) and print nothing, unless
`--allow-shared-page` is given: then they print the account user's hosted mailbox page, the
provider's connect on it with `--provider` and its index without, with `"link_kind":"shared_page"`,
`"expires_at":null` and a `warning`. That address does not expire and lets its holder manage all of
this user's mailboxes, deletion included, so ask for it only when that is acceptable. For
`account reconnect` the provider's connect is marked as a reconnect, so a user with no free mailbox
slot reconnects the mailbox rather than being refused a new one; on the index, the person opens the
mailbox and reconnects it from there.
`shared_page.not_enabled` means the plan does not include hosted pages. `account pending` then lists
no email entries and answers `"supported":false` with `"unsupported_channels":["email"]`.

```sh
reply account connect --channel email --provider gmail --name "Sales mailbox"
reply account connect --channel linkedin --name "Dana Example"
reply account reconnect 34 --channel linkedin
reply account pending
```

`account limits` prints the limits in Reply's names: an email account's `safety` section, which
`--daily` and `--set '{"minSendingDelaySeconds":90}'` change, and a LinkedIn account's `limits`,
which `--set` changes as Reply's limits update does. `account pause` and `account resume` act on a
LinkedIn account; Reply's only call flips the state, so it is read first and left alone when it is
already the one asked for. The flip turns an enabled account off and any other on, so `pause` flips
only an enabled account and `resume` only a disabled one. An account at its daily limit is active:
`resume` leaves it alone, and `pause` refuses it with `account.pause_unavailable` before any write. A
state the CLI does not know is refused with `account.status_unknown`, also before any write. Reply
has no way to pause a mailbox through its API. `account delete`
needs `--yes`, and `--force` deletes a LinkedIn account sequences still use. Reply's refusals come
under the CLI's codes, as every work command's do (`linkedin.account_in_use`, `email_account.not_found`,
`linkedin.invalid_cookie`), with Reply's own code in `reply_code`. After exit 3 from `account connect` or `account reconnect`, read
`account pending` before running it again: a link may already have been made.

**Errors.** With `--json`, a failure is one line on stderr:
`{"error":{"code":"contact.opted_out","title":…,"status":…,"reply_code":…,"ids":{…}}}`. `ids` is
whatever the command learned before failing, for example the id of a contact it created before
Expand Down
10 changes: 9 additions & 1 deletion skills/reply-adapter/reply-cli/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: >
Use when executing any Reply.io operation from a shell, setting up authentication,
or when another Reply skill needs commands executed.
metadata:
version: 1.3.2
version: 1.4.0
pack: reply-adapter
category: execution
maturity: reviewed
Expand Down Expand Up @@ -149,6 +149,12 @@ exit codes with their error `code` slugs.
`contact`, `inbox`, `account`, `schedule`, `direct-send`); `reply --help` lists them and each
command's `--help` gives its result and error codes. Don't invent one: reach any other operation
through `reply api`, using the endpoint mapping in `reply-operations-mapping`.
- `reply account connect` and `reply account reconnect` print a link for the person who signs in to
the account to open. The link is a credential: it is in the stdout field `link` once and nowhere
else (a `--verbose` trace shows `<link redacted>`). Hand it to that person and do not store, log
or repeat it. `email_link.not_available` means this Reply has no one-mailbox email link yet; pass
`--allow-shared-page` only when the user accepts the hosted mailbox page, whose address does not
expire and lets its holder manage all of that user's mailboxes, deletion included.

## Safety

Expand All @@ -165,6 +171,8 @@ explicit confirmation its Safety section requires.

## Changelog

- 1.4.0 (2026-11-11): *Failure modes* says how to treat the link `account connect` and `account
reconnect` print, and when `--allow-shared-page` is right.
- 1.3.2 (2026-11-06): *Failure modes* no longer says the work commands don't exist: it names the groups
(`sequence`, `contact-list`, `live-data`, `contact`, `inbox`, `account`, `schedule`, `direct-send`) and
keeps `reply api` for every other operation.
Expand Down
Loading
Loading