Heffl

Get one synced email thread with its most recent messages in chronological order. Message bodies are quote-stripped and bounded for agent use. Results are truncated above 40000 characters; select only the fields you need.

email_thread_details

Save an unsent reply draft in the mailbox that owns an existing synced message. The draft remains in the mailbox for review and is not sent. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

email_thread_draftReply

List synced email threads from the connected mailbox — the inbox, sent, archived or all mail. Use `quick: "unread"` for unread mail, `search` for a sender or subject, and `folder` to pick the mailbox. Returns subjects, participants, snippets and thread ids; pass a thread id to email.thread.details for the full messages. This is the ONLY way to read the mailbox — email is not a records.* object. Paginated: pass "cursor" from the previous result's data.meta.nextCursor. Pages above 40000 characters are rejected; retry the same cursor with a smaller pageSize or narrower selection.

email_thread_list

Build a complete form in one call: pages of fields (any type — text, email, phone, number, date, single/multiple choice, file upload, signature, rating, opinion scale, duration), conditional logic, calculated variables and CRM mappings. Give fields a `key` and reference those keys from logic/variables/mappings in the same call. Validated as a whole before anything is written; all problems are returned together. Call forms.guide first for types, operators and an example. Returns `fieldKeys` (your key → stored cf_* key) and the saved form with publicUrl. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_create

Permanently delete a form together with ALL of its responses. Its public link stops working. Cannot be undone. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_delete

Fetch one form's full structure in the same shape forms.create takes: pages with their fields (stored cf_* keys, types, options, scales, defaults, widths), logic (pages as 1-based numbers), variables, mappings, settings, theme, publicUrl and editUrl. `warnings` lists broken references. Read this before forms.update or any field/page edit.

forms_details

Add one or more fields (questions) to an existing form's page. Same field shape as forms.create (see forms.guide). `key` only seeds the stored cf_* name — the result returns the stored keys to use from then on. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_fields_create

Remove a field from a form. Answers already collected for it are kept on past responses. Refused while logic, variables or mappings still reference the field — update those first with forms.update. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_fields_delete

Edit a form field and/or move it. `changes` patches only what you pass (null clears description, placeholder, scale, duration or defaultValue); `options` replaces the whole option list and is refused if logic or mappings still use a removed option. The type cannot change — delete and re-add instead. `moveTo` moves it to another page and/or after another field. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_fields_update

Read this BEFORE building or editing a form. Returns the complete form-authoring reference: every field type with its answer shape, settings and allowed condition operators; logic rules; calculated-variable formulas; CRM mappings; form settings; and a full worked forms.create example.

forms_guide

List the workspace's forms (newest first) with id, title, page/field/response counts and public URL. Use forms.details for one form's full structure.

forms_list

Append a new page to the end of a form, optionally with its fields (same field shape as forms.create). Returns the page with stored field keys. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_pages_create

Delete a form page (not page 1). Its fields are kept and moved to the end of the previous page, or of `moveFieldsTo`. Later pages are renumbered down by one. Refused while logic still shows, hides or jumps to the page. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_pages_delete

Change a form page's title, description, button text or header visibility. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_pages_update

Read one form response with every answer labelled by its question, plus calculated variable values.

forms_submissions_details

List a form's responses, newest first. `answers` are keyed by stored field key (cf_*); `fields` maps each key to its question label; `calculated` holds variable values. Follow `meta.nextCursor` as `cursor` for older responses. Paginated: pass "cursor" from the previous result's data.meta.nextCursor.

forms_submissions_list

Change a form's title, description, theme, notifications, display or thank-you settings, and REPLACE its logic, variables or mappings. Omitted properties are untouched; displaySettings/submissionSettings are merged; logic/variables/mappings arrays replace the saved ones entirely, so send the full list (read forms.details first). Reference fields by stored cf_* key and pages by number. Fields and pages themselves change through forms.fields.* / forms.pages.*. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

forms_update

Convert an accessible, unarchived lead into a deal. Uses integer leadId. Describe deals for values; title defaults to the lead name. The existing conversion handler transfers history and archives the lead. Inspect receipts on failure; conversion is a multi-step workflow. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

leads_convert

Create a lost reason for leads, deals, or quotations. Use the returned id as `lostReasonId` when marking a record lost. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

lostReasons_create

Delete a lost reason. Blocked while records still reference it unless `replaceWithId` is passed (or null to clear those fields). Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

lostReasons_delete

Fetch one lost reason by its numeric id.

lostReasons_details

List reasons a lead, deal, or quotation was lost. Filter with `type`. Use the numeric id as `lostReasonId` when marking a record lost.

lostReasons_list

Rename a lost reason or change the object type it applies to. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

lostReasons_update

Add a note to a CRM record so the work and its rationale remain visible. Pass `note`, `entity`, and the record's numeric `entityId`. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

notes_create

Permanently delete a note. This destructive action always requires approval. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

notes_delete

Fetch one note by its numeric id.

notes_details

List notes on one CRM record using integer entityId. Ordered pinned first, then newest, then id. Follow meta.nextCursor as cursor to read older notes; pageSize defaults to 25. Paginated: pass "cursor" from the previous result's data.meta.nextCursor. Pages above 24000 characters are rejected; retry the same cursor with a smaller pageSize or narrower selection.

notes_list

Edit a note's text or pin state. Pass `id` and the fields to change. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

notes_update

Create a pipeline with its stages for deals or projects. Leads and clients cannot have pipelines; add stages directly to their team-wide stage list. Deal pipelines need at least one ACTIVE, WON and LOST stage; project workflows need at least one closed stage. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_create

Delete a deal or project pipeline. By default the delete is blocked when records still sit in its stages; pass validateReferencesBeforeDelete=false to skip that check. Deleting a project workflow also removes its task statuses, templates and recurring profiles. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_delete

Fetch one pipeline and its ordered stages by internal numeric id. Omit pipelineId for the team-wide lead or client stage list.

pipelines_details

List the pipelines configured for a CRM object type, each with its ordered stages and internal numeric ids. Leads and clients return one id-less envelope around their team-wide stages.

pipelines_list

Reorder an object type's pipelines. Pass every pipeline id in the desired order; array position becomes the new display order. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_reorder

Add a stage to a pipeline. pipelineId is required for deals and projects; for leads and clients it is optional and the stage joins the team-wide list. Lead stages must supply metadata.nativeStageType. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_stages_create

Delete a pipeline stage. When records still sit in the stage the delete is blocked unless replaceWithStageId is supplied, in which case those records move to that stage first. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_stages_delete

List the stages of a pipeline in display order. Omit pipelineId to list every stage across the object type's pipelines.

pipelines_stages_list

Reorder stages. Pass every stage id in the desired order; array position becomes the new display order. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_stages_reorder

Update a pipeline stage. Only the fields you supply change — omitted metadata keeps its current value rather than resetting to a default. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_stages_update

Rename, reorder, re-icon or archive a deal or project pipeline. Stages are managed through the pipelines.stages.* actions. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

pipelines_update

Update an explicit bounded list of integer recordIds with the same values. Never expands a changing filter into write targets. Returns per-record results through the shared batch execution contract. Describe update fields before calling. Consequential: this executes immediately under the credential permissions. Obtain any confirmation required by the user or client policy before calling it. For retries, supply a stable idempotencyKey for this operation and reuse it with identical input. Inspect partial results before starting a new operation.

records_bulkUpdate