mail:send, which you grant on the Authorize access page when you connect.
This page is generated from the connector’s tool catalogue. It describes 1 tool. Every tool reads or writes only your own account.
Permissions this page needs
mail:send: Send a thank-you email you already drafted, to the address stored on the contact linked to that meeting, when you read the exact message and approve it, and send one stored outreach draft you already wrote, and queue a checked table of your own outreach drafts
meeting_thank_you_send
Your agent host shows this tool as “Propose sending a thank-you email”.
What this changes: Propose sending one thank-you email the authenticated student has already drafted for a meeting, to the one address stored on the contact linked to that meeting, at a time within the next forty-eight hours.
Nothing is sent until the student reads the exact message in a browser and approves it, and this tool can never name a different recipient or change the text.
Permissions: This tool needs mail:send, which the Authorize access page describes as “Send a thank-you email you already drafted, to the address stored on the contact linked to that meeting, when you read the exact message and approve it, and send one stored outreach draft you already wrote, and queue a checked table of your own outreach drafts”.
Risk: consequential. This tool cannot change anything on its own. It proposes the change, and nothing happens until you open the Coffee Chats page it points to and approve exactly what is shown.
Input
The agent sends one object, and the table below is that object exactly as the connector publishes it. The connector accepts the object in one of these 2 forms and refuses any mixture of them. A published schema cannot state that rule, which is why the Required column readsno on every property and why each form is written out under the table. Within a form, every property the form does not name is refused.
Form 1, sending idempotencyKey, meetingId
Send idempotencyKey and meetingId. They are required in this form. sendAt may be sent beside them, and nothing else may be.
Form 2, sending operationId
Send operationId. It is required in this form. No other property is accepted with it.
Example calls
Result
A result is never larger than 4,096 bytes. This tool’s result takes one of these 6 forms, and one call returns exactly one of them. The field named beside each form below says which one you are looking at. Open a form to read its top-level fields.Shape 1, where tag is completed
Shape 1, where tag is completed
Top-level fields
Shape 2, where tag is requires_confirmation
Shape 2, where tag is requires_confirmation
Top-level fields
Shape 3, where tag is accepted
Shape 3, where tag is accepted
Top-level fields
Shape 4, where status is failed
Shape 4, where status is failed
Top-level fields
Shape 5, where status is cancelled
Shape 5, where status is cancelled
Top-level fields
Shape 6, where status is uncertain
Shape 6, where status is uncertain
Top-level fields