Automo

Apply column decisions for a proposal_token from preview_feed_mappings in one all-or-nothing step. Each decision links an existing placeholder (placeholder_id), creates a new one (name and kind), or skips the column. A placeholder already filled by another source is never taken over, and anything changed since the preview cancels the whole step so it can be previewed again. Applies only decisions the person has reviewed and approved. Returns how many placeholders were created, linked and skipped.

apply_feed_mappings

Change who can see a media-library folder: mark it confidential or open it back up to the workspace, and limit it to specific groups. Opening a folder exposes everything already inside it to everyone, so state the intent before calling. Owner or admin only.

set_folder_access

Check the status of a generate_video_clip job. While it runs, returns status 'processing' — poll every ~20s. On completion returns the permanent video URL and (when the credential can write files) registers the clip in the media library so it shows up in list_files and can be used in video projects.

get_video_generation

Check whether a design prints correctly as a given print product: whether the page's physical size matches the product's print area (the editor's own fit check — fits as is, needs one uniform resize, or needs cropping or margins, with the fixes the print wizard offers), which text, logos and other readable elements sit inside the safe zone where trimming may cut them, and which backgrounds and pictures reach the page edge without running into the bleed. Reads the design and the catalog and changes nothing. Image resolution is checked by the editor's print wizard, which reads each picture's real pixels.

check_print_fit

Report whether one teammate can open a document in Automo, and why: as its owner, through a share with them by name, because it is shared with the whole workspace, or not at all. `member` is a member id from list_workspace_members or the email on their Automo account. Also returns the document's owner and general `access` (private, workspace or anyone_signed_in). A link that opens for the connected Automo user does not open for a teammate whose can_open is false. Changes nothing; share_document changes access.

check_document_access

Connect a knowledge base folder to an AI chat bot so the bot answers from the pages in it. Pass set_kb_mode: "selected" to switch the bot to "Selected sources only" (only what is connected) — without it a bot in websites_only or none mode will not read the folder. Website sources are added from the bot's Knowledge screen. Requires an editor/admin/owner role.

add_bot_knowledge_source

Convert dates and times from one time zone to others with the time zone database, daylight saving included. Use it for any time quoted in a different zone from the one you answer in: a match kick-off, a flight, a webinar, a meeting in another city. Pass each time as the local wall-clock time with the zone it is in, and the zones to show it in. Returns the weekday, date and 24-hour time in each zone (the date can differ from the source date), the UTC instant, and whether it is already in the past relative to now.

convert_time

Create a brand kit in the workspace, with its colours, fonts, and written guidelines. Give each colour a `role` (primary, background, secondary, accent, text) — that is what makes the rest of the connector and the editors use it correctly. Fonts take a role too (heading, body, …). Logos and images are attached afterwards with add_brand_asset. Setting is_default makes this the kit everything uses when no kit is named, and clears the flag on the previous default.

create_brand_kit

Create an event on your own calendar, optionally inviting people — workspace members by id, anyone by email; Automo emails every invitee an invitation they can accept or decline. Meetings get an Automo meeting link by default; pass meeting_link to use the person's own Zoom, Teams or Meet link instead, or video_call: "none" for time blocked for yourself, reminders or in-person meetings. Blocking time for yourself runs immediately. Inviting people is TWO STEPS, ALWAYS: call once WITHOUT user_approved to see exactly who would be invited — this creates nothing and emails nobody — read it back to the person in full, and only call again with user_approved: true plus that response's approval_token if they explicitly agree.

create_calendar_event

Create a data feed from a proposal_token returned by preview_data_feed. Creating a feed links no Brand Hub placeholders; preview_feed_mappings and apply_feed_mappings do that. Always show the preview counts and wait for a yes before calling this.

create_data_feed

Get a short-lived signed URL to upload a large file's bytes DIRECTLY to storage, bypassing the model entirely — the way to add video too big for import_asset_from_url. Steps: (1) call this with the filename and mime_type; (2) HTTP PUT the raw bytes to the returned upload_url with header 'content-type: <mime_type>'; (3) call finalize_upload with the returned path to register it in the media library and get the public URL. Pass folder_id here to file it; when omitted on a personal credential, finalize files it under your own My Files folder instead of the shared library root, and a shared service token still files into the workspace library root.

create_upload_url

Create a new document in the workspace from an HTML `content` body (headings, paragraphs, lists, tables, links, bold/italic — the editor parses standard HTML). Returns the new document's id and an edit_url that opens it in the Automo document editor. Styling contract: put font-family in an INLINE style — <span style="font-family: Poppins">, on <p>/<h1>-<h6>/<blockquote>, or on a table cell <td>/<th>. A font on <font face>, a <div> wrapper, <b>/<a>, a list item, or a CSS class in a <style> block is NOT preserved by the editor and is dropped silently. Get exact family names from get_brand_kit. The response returns a `warnings` array when the body uses a placement that will not survive. Ownership: the document is created as, and owned by, the Automo user this connection acts as (whoami names them), even when a different person is the one chatting. It starts private to that user, so its edit_url opens for nobody else until share_document grants a named teammate or the whole workspace. The response carries `owner`, `access`, the `workspace` and an `access_note` saying who can open the link.

create_document

Create a public view link for a design, website or email project and return its URL. Anyone holding the URL can open the project without signing in, so say clearly that the link is public when handing it over. Optional expiry; downloads and comments are off unless asked for. revoke_share_link turns a link off again.

create_share_link

Create a new spreadsheet in the workspace from a compact `rows` (a row-major 2D array of cell values for ONE tab — the easy way to build a table; a string starting with = is a formula), from `tabs` (several named tabs in one go, each with its own rows and optional column pick-lists/dropdowns; formulas may reference other tabs, e.g. =VLOOKUP(E2,Icons!A:B,2,FALSE)), or from a full editor `data` document (e.g. one previously returned by get_spreadsheet). To bring in an existing .xlsx or .csv file, use import_spreadsheet_file instead. A spreadsheet whose first row holds column headers can feed run_batch_generate directly. Returns the new spreadsheet's id and an edit_url that opens it in the Automo spreadsheet editor. Styling contract: a cell has NO inline colour or font. Appearance lives in a top-level `styles` registry and each cell points at it — styles: { s1: { background: "#FEF3C7", textColor: "#111827", bold: true } } with `styleId: "s1"` on the cell. Colour written directly on a cell is stored but never rendered. The response returns a `warnings` array when the workbook styles something in a way the editor will not show.

create_spreadsheet

Open a new support ticket on this workspace's desk: a subject, a description, and who it is for (customer name and email), with optional priority, tags and CRM contact/company links. The desk's own intake runs on it — routing, auto-assignment, classification — and the creation is recorded on its timeline. This files a ticket; it never sends anything to the customer. When the person attached screenshots or files in this chat for the ticket, pass their file ids as attachment_asset_ids so the team sees them on the ticket (images, PDFs and text files, up to 5, 50 MB each); the result lists any file that could not be attached and why, so tell the person.

create_ticket

Set up a new POS venue — a store, restaurant, café or other site. Takes its name and optionally the business type, currency, timezone and contact details. The venue starts with an empty menu; build it with create_menu_category and create_menu_item.

create_venue

Create a new editable video project from a video template (from list_video_templates). Clones the template's composition with template lineage preserved, so any editing restrictions its author set keep applying. Returns the new project's id and an edit_url that opens it in the Automo video editor; use get_video_project/update_video_project to iterate on it.

create_video_from_template

Create a new video project in the workspace from either a `storyboard` (recommended: scenes with media + durations, captions with word timings, text overlays, image overlays like a brand logo/end-card, music/voiceover) or a raw editor `timeline` document. Pass brand_kit_id to style storyboard text with the brand's font and color. All media must already be uploaded https URLs (use search_brand_assets / search_dam_assets / upload_file). Returns the project id and an edit_url that opens it in the Automo video editor.

create_video_project

Create a new Automo Connect campaign brief: who to reach, what to say, on which channels, with which actions and daily caps, grounded in a knowledge base folder. Created as a DRAFT — it does not start working until someone starts it in Automo (start_campaign, with their approval).

create_campaign

Build a flow: one trigger, optional conditions on the trigger's data, and an ordered list of action steps. Every key must come from list_automation_building_blocks. The flow is saved switched OFF — tell the person to open it in Workflows to review and turn it on, because once armed it runs unattended on real records.

create_automation

Create a new empty project in the workspace, in whichever editor the person asked for. Pass `mode`: 'design' (default), 'website', 'email', 'presentation' (slide deck / Slides), 'pro_design' (Pro Design WebGL canvas), 'figma' (Spread: the layout for imported Figma files), 'prototype' (phone-sized canvas; clickable links between screens are not available yet, so never promise them), 'whiteboard' (infinite brainstorming board), or 'photo' (photo editor). Give a canvas size as a named preset (e.g. instagram_post, a4_portrait) OR explicit width+height — not both; modes with a natural size (website 1440×900, email 600 wide, presentation 1920×1080, whiteboard 4000×4000, prototype 390×844, photo 1920×1080) default it if you pass none. Returns the new project's id and an edit_url that opens it in the right editor — give the person that link. When the person asks for several pages of one design (a multi-page brochure), create ONE project and add each page with add_design_page; start with this call, not with a folder. App or web UI screens, UI/UX mockups, wireframes and anything Figma-style or 'pro design' with screens go to design_ui_screens instead (one Pro Design project, a frame per screen); only when that tool is unavailable, use mode 'pro_design' at the device size (e.g. 390×844 for a phone) with one named page per screen. A blank project is EMPTY until you fill it: canvas modes take add_element, and website/email take update_website. Don't hand over a link to a shell you haven't filled. Canvas designs also have no thumbnail until someone opens them — after filling one, call set_design_thumbnail once (after your LAST element write) so the project card shows a real preview. A print product from list_print_products (print_product_id, optional print_area_id) sizes the canvas to its print area so the design prints at that size, and check_print_fit verifies the finished design against it.

create_blank_project

Add one company (account) to the workspace CRM. Search first with search_companies — duplicates are not merged. Returns the new company's id so you can attach contacts and deals to it.

create_company

Add one person to the workspace CRM. Search first with search_contacts — this does not merge duplicates, and a second record for someone who already exists is worse than no record. Needs at least a name or an email. Creates a single contact; there is no bulk import.

create_contact

Open a deal in the workspace CRM against a company and/or a contact. Use list_deals first to see which stage names this workspace actually uses — stage is free text and an invented one silently creates a column nobody is looking at.

create_deal

Create a folder in the workspace media library (DAM), optionally inside an existing one, so uploads can be filed instead of landing loose. Returns the folder's id for use with upload_file. If a folder with the same name already exists in the same place, that one is returned instead of creating a duplicate.

create_folder

Create a knowledge base folder (optionally inside another one) and get its id and path. Returns the existing folder instead of a duplicate when one with the same name already exists at that level. Requires an editor/admin/owner role.

create_kb_folder

Create a folder on the projects page (the same folders /create/projects shows) and get its id. Only for a task that produces several SEPARATE projects — design variants, an ad set, best-of-N videos. Several screens or pages of ONE design (e.g. an app's home, chat and profile screens, or a multi-page brochure) are frames or pages of a single project (design_ui_screens for app or web UI screens, otherwise create_blank_project then add_design_page), never a folder: do not call this for them, and never as the first step of a single-design request. For a genuine multi-project task, create ONE folder named after the task, then pass its id as folder_id to create_blank_project, create_project_from_template, create_video_project and create_video_from_template so every variant lands together. Folders are personal to the acting user. Returns an existing folder instead of a duplicate when one with the same name already exists at that level.

create_project_folder

Create a new project in the workspace from a template (from list_templates). Clones the template's content into a new editable project, preserving any editing restrictions its author set. The canvas size comes from the template. Pass brand_kit_id to record the brand kit on the project (open it in the editor to apply the brand's colors/fonts/logo). Returns the new project's id and edit_url — a link the person opens to edit the design themselves (they sign in if they aren't already). Give them that link.

create_project_from_template

Add one task to the workspace. When the person asks for a task for themselves — 'for me', 'remind me to' — pass assigned_to "me" so it lands in their own My Tasks with its reminders. Use a teammate's member id only when the person named that teammate — assigning a task puts it in someone's queue and can trigger their reminders. Link it to a contact, company or deal when it came out of that conversation.

create_task

Render one page of a design and have Automo's design critic score it the way a senior art director would: hierarchy, composition, colour, typography, brand and craft (1–10 each), an overall verdict (ship or refine), the single biggest improvement, and up to 8 concrete fixes keyed to real element ids. It applies taste caps a linter cannot see — no idea, a website pasted onto a graphic, a small cluster in an empty frame. Read-only; uses a vision model, charged to the workspace. Returns the rendered image too. To apply the fixes, call improve_design.

critique_design

Remove an event you organise from your calendar; invitees lose it from theirs too. TWO STEPS, ALWAYS: call once WITHOUT user_approved to see exactly what would be removed — this deletes nothing — read it back to the person, and only call again with user_approved: true plus that response's approval_token if they explicitly agree. Automo does not email invitees a cancellation — offer send_email if they need one. Repeating series must be changed in Automo, not here.

delete_calendar_event

Soft-delete a data feed. First call without confirm to see how many fields use it, then call again with confirm true.

delete_data_feed

Move a design, website or email project to the trash — use it to clean up test or stub projects. It stops showing in list_projects and the app (recoverable from the app's trash). Pass the project_type that matches how it was created (default design). For video, spreadsheet or document projects, delete them from the Automo app instead. Irreversible from the connector's side.

delete_project

Delete a file from the workspace media library (DAM) — removes both the stored object and its library entry. Takes a file id from list_files or search_dam_assets. This cannot be undone through the connector, so read the library first and be sure of the id. Files in another member's personal folder or a restricted folder can't be deleted here.

delete_file

Remove an element from a design. Takes an element id from get_project_elements. Nothing else on the page moves to fill the gap. This cannot be undone through the connector, so read the design first and be sure of the id.

delete_element

Create a finished design from a written brief with Automo's design engine — the same pipeline as the in-app AI designer: the selected workspace brand kit only when the piece is for that workspace (otherwise genre-appropriate art direction without its logo), matching templates as layout references, an art-direction layer (concept first, the whole frame, no website clutter on a graphic), several candidates ranked by a quality gate, and automatic fixes for overlaps, overflow and contrast. Saves it as a NEW design project and returns its edit_url. Prefer this over create_blank_project + add_elements for any new poster, flyer, social post, story, ad, invitation or cover. Pass a specific brief (what, for whom, the key facts and the tone), and the size it is for (preset or width/height): a screen, a poster and a story are different canvases. When the design needs a QR code, pass qr_content: a real, scannable code is placed for you (never draw one with shapes or import a QR picture). When the brief describes a scene, setting or illustration (a castle library, a beach at dusk, a city at night), pass background_scene: a fitting free stock photo is placed full bleed behind the design, with the text over it (without it, the engine names the photo itself for a scene, character, product or photo brief). Always decide the imagery and pass it as imagery, with a short image_prompt, so the person sees it on the card and can switch it: generated_image for a scene, character, creature or illustration (a gothic library with violet tendrils, a girl with a bandaged face, Oshun and Shango artwork): it is generated at the canvas shape with room for the title, the brief's rules honoured (no faces, silhouettes only, no animals, never text in the image), 2 to 4 options picked by the critic, and its cost is on the card; stock_photo for real products, food, places or people where a photo is better (a hero photo of the drink); your_upload with background_image_url for the person's own picture; type_only only when the brief asks for a flat, typographic or infographic look. The result's background_image says whether a photo was placed: never tell the person their scene is in the design unless it says placed. Takes up to a minute. Afterwards use critique_design to see it scored, or improve_design to refine it.

design_from_brief

How a design performed where it was published through Automo (social posts, email campaigns, ads): impressions, clicks, CTR, engagement, conversions and opens, per page and A/B variant, with the leading variant of each set.

get_design_performance

Disconnect one knowledge source (by its id from get_bot) from an AI chat bot. The folder, pages or website content stay in the knowledge base; the bot just stops answering from them. Requires an editor/admin/owner role.

remove_bot_knowledge_source

Space three or more elements evenly, horizontally or vertically — the editor's distribute buttons. The outermost two stay where they are and the rest are placed between them with equal gaps. The elements must share a container (all directly on the page, or all in the same group). Returns the ids that moved.

distribute_elements

Create a marketing email sequence as a DRAFT: its name, sender, and an ordered list of steps, each with a delay, a subject and an HTML body. The connector cannot activate a sequence — an active sequence emails enrolled contacts on a schedule, unattended, so the person reviews and turns it on in Marketing. Nothing is sent by this call.

create_email_sequence