Attaché

Whether one of this business's own connections is actually working — their mail, the address campaigns go out from, texting, WhatsApp, or taking payment. Call this at the end of a setup walkthrough instead of asking them whether it worked.

verify_connection

Has a person approved a queued action yet, and what happened when it ran.

check_action

Save a draft of a marketing email. Use it when they want an email written for a list or a campaign — this saves the draft, it does not send anything. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

marketing_draft_email

Every comment one person has left, newest first, by their YouTube channel id — the id `list_comments` returns, not their display name, which two fans can share and one fan can change. Use it before drafting a reply, so the answer knows whether this is the first thing they have said or the fifth. Same 30-day window as `list_comments`.

comments_from

Hand over comments you have read on a TikTok or Instagram post, so they land in this business's comment inbox beside the ones Attache collects itself. Attache cannot read either network — there is no commercial way for a product like this to see the comments on a small business's posts — so the only way these arrive is for you to read them where the creator is signed in and file them here. Once filed they are sorted, answered and shown exactly like the rest: `list_comments` returns them, `comments_from` groups one person's, and `draft_reply` writes an answer the creator pastes back themselves. Filing the same screen twice is safe and changes nothing — each comment's id is worked out from what it says, so a second filing updates rather than duplicates. Send the commenter's @handle as `author`, since that is what tells two people apart and what groups one person's comments together. Only the last 30 days are kept, as for every other comment here, so an older one is deleted rather than hidden. YouTube and Bluesky are refused on purpose: Attache reads those itself.

file_comments

File an email onto a person or company record. Use it when an outside assistant has an email thread in front of it and wants it kept on the customer's record — it has the contact or company id. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

note_file_email

Documents and files in the business's library, optionally only the ones attached to one company, person or deal.

list_files

Find companies, people or deals, and get the WHOLE matching set a page at a time — never only the first few. A PERSON matches on their name, their email address, their job title, or any tag filed on them — so the business's own shorthand ("P1", a supplier code, a city) finds the people it was filed on. A COMPANY matches on its name, its legal name or its web domain. A DEAL matches on its name or its purchase-order number. Narrow it further with tags, where every tag listed has to be on the record, so you can ask for two at once; or with field and value, which look inside the columns of the file the records were uploaded from — get_record lists those columns on a record under imported_fields. total says how many match in all, so you always know what you have not seen. Returns ids to pass to get_record.

search_records

The forecast by quarter and by owner: pipeline, best case, commit, booked, closed and the weighted total, read off this workspace's own funnel.

forecast_rollup

Import a file that is already in the workspace. Use it when an outside assistant has a file id and wants the rows in that file imported. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

import_run

Invoices with their balances, and the total outstanding.

list_invoices

Make an invoice for a customer. Use it when they want to bill somebody and they know the name, the date and the payment terms — the priced lines are added to the draft afterwards. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

invoice_create

The written history on one company, person or deal, newest first — notes, logged calls and meetings, and any email that has been filed onto the record (forwarded in, or copied to the workspace address when it was sent — Attache puts that address on the CC line of every message it sends, so the customer's reply is filed too). This is the only way to read the words of an email through this connection: Attache does not open anybody's mailbox, so an email that was never filed onto a record is not here and cannot be fetched. If you can reach the customer's mailbox yourself, read it there and file what matters with note_create — that is the route, not a mail permission here.

read_history

One company, person or deal in full: its own fields, who in the workspace owns it, and the ids of the records it is attached to. It also carries imported_fields — every column of the file the record was uploaded from, keyed by the header that file used, so a column like "priority tier" is readable here even though Attache has no field of its own by that name.

get_record

The places in this workspace somebody does a thing by hand, each with its web address — adding a user, connecting a mailbox, setting up a web form, opening today's work. Nothing here runs: these are pages to send a person to. Narrowed to what this connection's scopes and this person's permissions allow.

list_pages

Quotes with their totals, who they are for, which deal they belong to, and how far through approval they are.

list_quotes

What people have been saying on the YouTube channels this business watches, newest first. Each one carries the commenter's channel id, which is the only stable way to tell two people with the same display name apart. Each also says how it was sorted -- question, buying, complaint, praise or other -- and, in one line, why the sorting pass chose that, so the reason can be read back to the person instead of restated as a guess; both are empty on a comment nothing has sorted yet and on one sorted before reasons were recorded. READ ONLY, and not because of a permission: Attache holds no credential that can post to YouTube, so a reply is something the person copies and posts themselves. Only the last 30 days are kept — that is YouTube's condition on holding them at all — so an older comment is gone rather than missing. Pass `needs_you` to get only what is actually waiting on a person -- still open, and not simply someone being nice -- which is what to ask for when the question is what wants an answer rather than what came in last. It leaves out praise and anything already dealt with, and it keeps an unsorted comment in, because nothing has read that one yet.

list_comments

Tell this business's own assistant something true about the business, so it is still known next time — who owns what, how they work, what they never do. One short sentence. Read what is already known from business_context first.

remember

Make a to-do for yourself. Use it when they want to be reminded to do something, or to note a follow-up. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

task_create

Change what your assistant is called. Use it when they want to call the assistant something else, or ask what its name is and offer a new one. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

agent_rename

Every deal — what stage it is at, how likely that stage is, what it is worth, and who in the workspace owns it. Closed deals are included unless you filter them out by stage.

list_deals

Send an email. Use it when they want to write to ONE named person from their own email account — a reply, a follow-up, a note to a customer; not a list or a campaign. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

email_send

Send your expense report for approval. Use it when they are done with a report and want it sent in, approved, or paid back. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

expense_submit

Get a link that opens one file without signing in, so it can be attached to something or sent on. A person in the business approves each one.

share_file

Start a deal on a person you already have. Use it when they want to track a sale against somebody who is already in here, and they have that person's id. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

deal_create

Start a quote on a deal, with its first line. Use it when they want a quote written against a deal they already have, and they know the product code. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

quote_create

Start an expense report. Use it when they want to start or name a report itself — NOT when they are claiming something they paid for, which files itself. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

expense_start_report

Stop emailing someone. Use it when they name an email address that should not be marketed to again. It is queued for a person in the business to approve, and returns an approval id — poll it with check_action. Nothing happens until somebody approves it.

marketing_suppress

How one of this business's setups actually works, step by step: what they do, which screen it happens on, and how they know that step worked. Read this before talking anybody through connecting their email, verifying a domain to send campaigns from, texting, WhatsApp, taking payment, a form on their website, or getting their price book in from a spreadsheet — it is the same wording their own assistant uses, and it names the traps. Where there is a connection to check, finish with verify_connection rather than asking them whether it worked.

setup_walkthrough

What this workspace's most recent file upload did: how many records it saved, updated, skipped and failed, and the problems it recorded row by row. Ask this FIRST when somebody says an upload did not work, instead of asking them to describe the file — it is already written down. Each problem names a row, a column and a reason and deliberately does NOT include what was in the cell, so do not quote or guess a value back as though you had seen it; say which row and column to open and what the file needs there. Row numbers count the way the spreadsheet does, with the heading row as row 1, so row 2 is the first row of data.

last_import

What is on this person's desk: their tasks, their meetings and their deals, soonest first.

my_work

Who this connection is acting as, which business it is in, and what it is allowed to do. Call this first.

whoami

Put a drafted reply on one comment, for the person to read and post themselves. Attache cannot post to YouTube — the reply appears on the comment in their inbox marked "written by your own agent", and they copy it under the video if they want to send it. One comment holds one draft, so writing again replaces what was there, which is how you redraft. Up to 4000 characters. It does not mark the comment handled: only the person does that, after they have posted it.

draft_reply