account_create
ChatGPTAdd a company. Use it when they name a company to add to the CRM. 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.
account_update
ChatGPTChange a company you already have. Use it when they want to tag a company, or fix its website, and they have its 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. One call is one approval, so to change many records send ids and the whole batch is approved once rather than record by record.
agent_rename
ChatGPTChange 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.
business_context
ChatGPTWhat this business is, how it describes itself on its own paperwork, and everything its own assistant has been told about how it works. Read this before answering anything about the business, and add to it with remember.
check_action
ChatGPTHas a person approved a queued action yet, and what happened when it ran.
contact_create
ChatGPTAdd a person. Use it when they name a person to add AND give an email address for them. 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.
contact_update
ChatGPTChange a person you already have. Use it when they want to tag a person, or fix their job title or phone, 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. One call is one approval, so to change many records send ids and the whole batch is approved once rather than record by record.
deal_create
ChatGPTStart 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.
draft_reply
ChatGPTPut 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.
email_send
ChatGPTSend 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.
expense_add_item
ChatGPTAdd an expense to your report. Use it when they name something they paid for out of their own pocket and want it back — a receipt, a lunch, parking, a fare, a hotel, a subscription. 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
ChatGPTStart 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_submit
ChatGPTSend 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.
forecast_rollup
ChatGPTThe forecast by quarter and by owner: pipeline, best case, commit, booked, closed and the weighted total, read off this workspace's own funnel.
get_record
ChatGPTOne 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.
import_run
ChatGPTImport 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.
invoice_create
ChatGPTMake 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.
last_import
ChatGPTWhat 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.
list_campaigns
ChatGPTThe marketing campaigns this person can see, with how many leads are still on each working roster and how many of those look high intent.
list_courses
ChatGPTThe courses in this workspace, most recently worked on first. A course is modules and lessons, and every lesson points at one of the creator's own YouTube videos -- so each row here says how many lessons it has and how many of them still have no video, which is the number the work is actually about. A lesson is bound to a video by its id or by a title that clearly matches one video; a title that could mean two of them is deliberately left unbound and shown as work to do, never guessed. Draft, published or archived: a draft is unfinished, and publishing a course and handing out its link are the creator's to do, not something to ask for here. READ ONLY. YouTube only, for the same reason the video list is: there is nothing else for a lesson to point at.
list_deals
ChatGPTEvery 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_files
ChatGPTDocuments and files in the business's library, optionally only the ones attached to one company, person or deal.
list_invoices
ChatGPTInvoices with their balances, and the total outstanding.
list_pages
ChatGPTThe 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_quotes
ChatGPTQuotes with their totals, who they are for, which deal they belong to, and how far through approval they are.
list_topics
ChatGPTThe topics people keep raising in the YouTube comments on the channels this business watches, biggest first -- the same grouping the business sees on its own comments page, read from one place so the numbers cannot disagree. This is the arithmetic list_comments cannot do: that one hands back the newest comments one at a time, up to 50, with no way to page further, so counting a month of them is not something to attempt from it. Each topic carries FOUR numbers and they are two different questions over two different windows. Comments and people over the last 7 days, and comments and people over the last 30 -- a topic asked twenty times last month can read as zero for the week, which means it has gone quiet, not that it never happened. Comments and people are also not one number twice: forty comments from six people is a handful of regulars, forty from forty is the audience, and only the second is a trend. Each topic also carries one real comment in a fan's own words as its label (there is no minted title, deliberately -- a label a model invented would be a second thing that can be wrong), how it was sorted if anything has sorted it, and the dates of its first and last comment. A group has to have at least 3 comments in the 30 days to count as a topic at all, so a one-off question is absent rather than listed as a finding. READ ONLY. Only the last 30 days exist to group -- that is YouTube's condition on holding comments at all -- so an older topic is gone rather than missing. Empty, honestly, on a workspace whose comments nothing has sorted into groups yet.
list_videos
ChatGPTThe videos on the YouTube channels this workspace watches, newest first -- the creator's OWN uploads, read from each channel's uploads playlist about once a day, which is why a video posted in the last few hours may not be in here yet. YouTube only, and not as a current limitation: nothing reads TikTok or Instagram uploads, so there is no such row to find and no plan that adds one. This is the list a course is built from, so a video's id here is what a lesson points at. READ ONLY -- a video gets into this list by being posted on the channel, never by being named to a tool. Each row carries the title, when it went up, its channel and its YouTube id. It does NOT carry how long the video is: that costs a second call per video which this workspace does not make, so the length is unknown rather than zero. The same 30-day clock as the comments applies -- these are cached YouTube rows, refreshed while the channel is still watched, and deleted rather than archived once they are not.
marketing_draft_email
ChatGPTSave 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_suppress
ChatGPTStop 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.
my_work
ChatGPTWhat is on this person's desk: their tasks, their meetings and their deals, soonest first.
note_create
ChatGPTAdd a note to a record. Use it when they want what happened written down on a company, contact, deal or quote — and they already have that record'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.
note_file_email
ChatGPTFile 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.
pricebook_add_sku
ChatGPTAdd a product or service to your price book. Use it when they want something they sell to be available on quotes and deals — a service, a package, a retainer, a day rate. 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.
put_file
ChatGPTPut a file you made — a deck, a document, a report — onto a company, person or deal, in the business's own file store. A person in the business approves each one.
quote_create
ChatGPTStart 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.
read_history
ChatGPTThe 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.
remember
ChatGPTTell 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.
search_records
ChatGPTFind 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.
setup_walkthrough
ChatGPTHow 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.
share_file
ChatGPTGet 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.
task_create
ChatGPTMake 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.
verify_connection
ChatGPTWhether 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.
whoami
ChatGPTWho this connection is acting as, which business it is in, and what it is allowed to do. Call this first.