- Home
- Resources
- Integrations
- Frontify
Claude Frontify connectorWhat Claude can do in your Frontify account.
The Claude Frontify connector exposes 53 tools. 27 read, 22 write, 4 are undocumented. Claude reads your guidelines, assets and templates, and with the right pack it uploads, tags, organises and routes them. Here: what each group does, which pack unlocks what, and who decides.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for brand and marketing teams
Your brand lives in Frontify: guidelines, logos, fonts, colours, templates. The connector brings it into Claude, so a marketer can ask for the tone-of-voice rules or the right logo while drafting, and a brand manager can have files uploaded, tagged and sent for review without opening the Frontify interface.
On-brand answers while you write. Drafting a launch email, you ask how the brand talks about pricing. frontify_list_guidelines finds the guideline and frontify_get_guideline_page reads the page, so Claude quotes your own rules back.
Creative from approved templates. A regional team needs a social visual in the house style. frontify_export_creative starts an export from a brand template with your text, and frontify_get_creative_export returns the download link when it is ready.
Tidy a messy library. After a photo shoot, frontify_upload_file and frontify_create_asset bring the files in, and frontify_move_assets puts them in the right folder.
What it will not do on its own: Frontify groups tools into packs, and the default one, discovery, only reads. Writing needs a write-capable pack chosen by an administrator, and only one pack is active at a time for the whole account. Nothing runs by itself either: no asset is tagged automatically when it lands. For hands-off routines, an automation tool is the right fit, a different job listed on our Integrations page. To track review work next to it, the Claude asana connector can join the same chat.
The vocabulary in one minute
Five words you will meet while connecting Frontify.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the tools it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use afterwards. Given once per person and revocable.
- Approval
- The confirmation Claude waits for before doing something that changes your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Frontify.
Plug Frontify into Claude in three steps
- 01
Find Frontify in Claude
In Claude's settings, open Customize, then Connectors, and look for Frontify in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; members then sign in one by one.
- 02
Start the connection
Click Connect on its row; you are then sent to your own Frontify login page to authenticate. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Read Frontify's authorization screen before you accept. It belongs to Frontify, not to Claude, and it sets what the access covers. You can withdraw that access later from the Frontify side.
The 53 tools, sorted by what they do
Frontify gives Claude 53 tools: 27 that read your account, 22 that change something in it, and 4 no official source describes.
Twenty-seven tools read, twenty-two change your Frontify content, and four are named on the directory sheet without any description. Which ones Claude actually sees depends on the active pack. Names stay in English, exactly as Claude shows them.
- 27 read
- 22 write
- 4 not documented
Tools index
- frontify_display_assets
- frontify_display_templates
- frontify_generate_url
- frontify_get_asset_comments
- frontify_get_assets_data
- frontify_get_brand
- frontify_get_brand_color_palette
- frontify_get_brand_font_families
- frontify_get_collaborators
- frontify_get_collection_assets
- frontify_get_creative_export
- frontify_get_current_user
- frontify_get_folder_contents
- frontify_get_guideline
- frontify_get_guideline_page
- frontify_get_library
- frontify_get_library_page_assets
- frontify_get_project
- frontify_get_targets
- frontify_get_templates_data
- frontify_get_workflow_statuses
- frontify_list_brand_color_palettes
- frontify_list_brands
- frontify_list_creative_templates
- frontify_list_guidelines
- frontify_read_asset
- frontify_search_assets
- frontify_add_asset_revision
- frontify_add_asset_revision_from_url
- frontify_add_asset_tags
- frontify_add_asset_targets
- frontify_add_collection_assets
- frontify_add_custom_metadata
- frontify_add_workflow_checklist_item
- frontify_cancel_creative_exports
- frontify_create_asset
- frontify_create_asset_comment
- frontify_create_asset_from_url
- frontify_create_collection
- frontify_create_custom_metadata_property
- frontify_create_folder
- frontify_create_project
- frontify_create_workflow_task
- frontify_export_creative
- frontify_move_assets
- frontify_remove_asset_targets
- frontify_remove_workflow_checklist_item
- frontify_update_workflow_checklist_item
- frontify_upload_file
What Claude reads (27)
27 toolsTwenty-seven read-only tools: brands, guidelines, libraries, assets, templates and workflow settings.
frontify_display_assets
Displays Frontify assets in a visual widget inside the conversation. Frontify calls it the only path to download an asset or open it in Frontify.
frontify_display_templates
Presents creative templates in a widget, as a detailed card for one template or a grid for several, so you can pick visually.
frontify_generate_url
Generates a Frontify web address that leads to a specific resource, so Claude can hand you a link rather than directions.
frontify_get_asset_comments
Retrieves the comments and annotations left on an asset, optionally filtered by status, so Claude can summarise the feedback in a few lines.
frontify_get_assets_data
Fetches the metadata of assets without a widget, choosing which groups of properties to return, which suits questions about licences, tags or dimensions.
frontify_get_brand
Returns detailed information about a brand, including its libraries and projects, the natural first step before Claude digs into one specific area of your content.
frontify_get_brand_color_palette
Retrieves a single brand palette with its colours and the values of each one in several formats, ready to quote in a brief or a style sheet.
frontify_get_brand_font_families
Returns the brand's font families and the styles available from each font provider, exactly as they are defined in the brand essentials.
frontify_get_collaborators
Lists the people who can access a library or project, with their names, emails and roles.
frontify_get_collection_assets
Returns a light list of the assets in a collection, IDs and titles only, without a widget, which is enough for Claude to count or compare.
frontify_get_creative_export
Checks where a creative export job stands and, once it has finished, returns the download links for the result.
frontify_get_current_user
Retrieves the profile of the Frontify user currently signed in, so Claude knows whose permissions frame every answer it gives.
frontify_get_folder_contents
Lists the subfolders of a folder and a light list of its assets, IDs and titles only, so Claude can describe what is stored where.
frontify_get_guideline
Retrieves a specific guideline with its page structure, the table of contents Claude needs before reading any page in it.
frontify_get_guideline_page
Reads a guideline page as text with its headings, blocks and image addresses; Frontify adds that visually capable AI can also interpret the images on the page.
frontify_get_library
Returns a library's structure: its folders, assets, collections, licences and the custom metadata fields it uses, in one overview.
frontify_get_library_page_assets
For one page of a library, gives the assets placed on it as a light list, IDs and titles only, without a widget.
frontify_get_project
Retrieves a project's structure with its folders and assets, the working space where a team collaborates on files for a given job.
frontify_get_targets
Retrieves the targets configured in the Frontify account, the categories used to mark which channel or use an asset is meant for, such as print or social.
frontify_get_templates_data
Fetches full data on creative templates without a widget, including their variables and export options, so Claude knows what can be filled in.
frontify_get_workflow_statuses
Retrieves the workflow statuses set up for a given library, the successive stages an asset goes through during review before approval.
frontify_list_brand_color_palettes
Lists summaries of a brand's colour palettes from its essentials, the overview Claude reads before opening any single palette in detail.
frontify_list_brands
Lists every brand available in the Frontify account with IDs, names and visual identities, the starting point on multi-brand accounts.
frontify_list_creative_templates
Lists the creative templates available in a brand, a quick catalogue of ready-made formats before anything gets exported from one of them.
frontify_list_guidelines
Lists all guidelines available for a brand with names, IDs and web addresses, so Claude picks the right one to read.
frontify_read_asset
Fetches Frontify-hosted images as inline content so Claude can analyse them visually, not just read their titles and metadata.
frontify_search_assets
Searches assets in a library, project or brand with advanced filters and returns light matches, IDs and titles, without a widget.
What Claude changes (22)
22 toolsTwenty-two tools that add, organise, route or cancel things in Frontify. No source gives them their own confirmation: the general rule below applies.
frontify_add_asset_revision
Approval: see the ruleAdds a new revision to an existing asset from a file already uploaded, the last step of a three-step upload.
frontify_add_asset_revision_from_url
Approval: see the ruleDownloads a file from a public web address and sets it as the current revision of an existing asset in one go.
frontify_add_asset_tags
Approval: see the ruleAdds tags to assets. Frontify's help centre only describes it in general terms, as part of organising and tagging assets.
frontify_add_asset_targets
Approval: see the ruleAdds targets to one or more assets to categorise them for a channel or a use case.
frontify_add_collection_assets
Approval: see the rulePuts assets into a collection. Frontify's help centre covers it only as part of building collections, without a dedicated description.
frontify_add_custom_metadata
Approval: see the ruleApplies custom metadata values to assets. Frontify's help centre only mentions it within assigning metadata, with no finer detail.
frontify_add_workflow_checklist_item
Approval: see the ruleAdds an item to the checklist of an existing workflow task, so reviewers know what still has to be verified.
frontify_cancel_creative_exports
Approval: see the ruleStops one or more creative export jobs that are still processing or rendering. Frontify files it among its destructive tools.
frontify_create_asset
Approval: see the ruleCreates the asset record in Frontify from a file uploaded beforehand, the third and last step of the upload sequence.
frontify_create_asset_comment
Approval: see the ruleAdds a comment, an annotation or a reply to a Frontify asset, visible to the people reviewing it.
frontify_create_asset_from_url
Approval: see the ruleCreates an asset from a public web address: Frontify downloads the file, uploads it and creates the asset in one step.
frontify_create_collection
Approval: see the ruleCreates a collection, a virtual grouping of assets in a library that does not move the files themselves.
frontify_create_custom_metadata_property
Approval: see the ruleDefines a new custom metadata property on a library, without going through the admin interface.
frontify_create_folder
Approval: see the ruleCreates a folder inside a library, a project or another folder to organise assets.
frontify_create_project
Approval: see the ruleCreates a project within a brand for collaborative file work, the space where a team gathers files for a given job.
frontify_create_workflow_task
Approval: see the ruleCreates a workflow task. Frontify's help centre only describes it in general terms, as part of routing assets for review.
frontify_export_creative
Approval: see the ruleStarts an export job that generates a design from a creative template with the text and values you give, delivered once processing ends.
frontify_move_assets
Approval: see the ruleMoves one or more assets to another folder within the same library or workspace. Frontify labels it destructive.
frontify_remove_asset_targets
Approval: see the ruleRemoves specific targets from one or more assets while keeping the other targets assigned to them. Frontify's pack page tags it as destructive.
frontify_remove_workflow_checklist_item
Approval: see the ruleRemoves an item from a workflow task's checklist. Frontify puts it in its destructive category.
frontify_update_workflow_checklist_item
Approval: see the ruleUpdates the content, the assignee or the completion state of a checklist item in a workflow. Despite the word update, Frontify marks it destructive.
frontify_upload_file
Approval: see the ruleOpens a file upload to Frontify and returns temporary addresses where the file content is sent, the first of three upload steps.
Undocumented (4)
4 toolsThe directory publishes these four names and nothing more. No official text says what they do, and this page will not guess from the names.
frontify_delete_workflow_task
The directory sheet lists this name, and that is all anyone has published. Neither Frontify's help centre nor its pack page describes it, so this page adds nothing.
frontify_move_workflow_task
Same situation here: the name appears in the tool list and no official source documents it. Guessing its purpose from the name would be a claim this page cannot back up.
frontify_reply_to_comment
Listed on the directory sheet, missing from Frontify's help article and from its official pack page: there is simply no text to rely on for this tool.
frontify_update_asset
Only its name is public. Neither Frontify's help article nor its pack page mentions it, so no official source says what it does, nor whether it reads your library or changes it. This page will not fill that gap with a guess.
What Claude asks before acting
By default, Claude stops and asks for your confirmation before each action it takes on an account on your behalf. With Frontify that matters: twenty-two tools can add, organise, route or cancel things, and Frontify labels some of them destructive.
On Team and Enterprise, workspace owners decide whether members can let some actions pass without a prompt, and they can restrict what a connector does for the whole organisation, keeping reads and closing writes for instance. Nobody overrides that from their own account. Claude works with your Frontify rights only: what you cannot open there stays closed to it. On Frontify's side, the active pack decides which tools exist at all.
Which plans include it
Of the 819 sheets in the official directory, none displays availability by plan. The connector-by-connector answer is published nowhere, a genuine gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organisation before members can connect. Frontify's own help article says something more specific, set side by side in the limits section. The connector's sheet in the official directory shows its current state.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing runs by itself when a file lands or a review stage changes.
The tool list is an observed floor, not a promise: an admin can open actions no public sheet shows, and on Frontify the active pack changes the set Claude sees. The partner badge is not a security audit, and Anthropic says on every sheet that it does not pick a publisher's tools. Everything here comes from Frontify's help centre and its official pack page; neither Claude's help centre nor Anthropic's developer docs cover this connector.
Which Claude plans can use the Frontify connector?
- Claude help centre, general rule for connectors ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner must switch each one on first.
- Frontify help article on its server ↗September 2026The publisher says it can be added in Claude, Claude Desktop and Cowork on Free, Pro, Max, Team and Enterprise plans.
What this page followsBoth pages are current and they do not contradict each other so much as speak from different places: Anthropic states the rule for every connector, Frontify names plans for its own. Neither is Anthropic confirming this connector on your account, so check the Frontify sheet in the directory while signed in to Claude.
Need help connecting Frontify to Claude?
A person reads every message.
