- Home
- Resources
- Integrations
- Productised
Claude Productised connectorWhat Claude can do in your Productised workspace.
The Claude Productised connector exposes 73 tools: 34 read your workspace, 38 change it, 1 is undocumented. Here: what Claude can build, edit and publish, what it reads about your leads, what it asks first, what it cannot touch, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude works inside Productised
Productised hosts AI products such as assessments and lead magnets: a respondent answers questions, gets an AI-generated result and becomes a lead in your pipeline. With this connector you build, edit and publish them by talking to Claude. Its authorization screen says Claude asks to read products, leads and brand and to write changes, and every call is logged.
A product from a description. You describe the product you want: plan_product recommends the outcome type and funnel stage, create_product opens an empty record, generate_product builds the conversation flow and workflow, and publish_product returns the public link.
Leads worked from the chat. get_morning_briefing sums up new leads and hot prospects, get_hot_leads surfaces the most promising ones, and update_response_status moves a lead along your pipeline, from new to contacted and beyond.
Result pages reworked without the canvas. get_page pulls the current HTML of a result page, you discuss a new version with Claude, and update_page replaces it.
Now what the directory sheet does not say. Productised documents what the connector cannot do: delete a lead, change billing or subscription state, read or send personal email, or reach another workspace. Deleting a product is possible but needs an explicit confirm flag. And nothing runs on its own: no tool fires when a new submission arrives. For that kind of background reaction you need an automation tool, a different job; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while connecting Productised.
- 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 in that account. Claude picks the ones it needs; the directory sheet lists them by name.
- Authorization
- Productised's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes your workspace, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to a service outside it.
Setting up the Claude Productised connector in three steps
- 01
Find Productised in Claude
Open Claude's settings, go to Customize, then Connectors, and look for Productised in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector before each member can sign in on their own.
- 02
Connect from its row
Click Connect on the Productised row, then sign in to Productised in the window the service opens itself. If the link breaks later, Disconnect and connect again.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Productised, not to Claude, and it is what decides how far the access reaches. Productised says that access can be withdrawn from its own settings.
The 73 tools, split by what they do
Productised gives Claude 73 tools: 34 that read your account, 38 that change something in it, and 1 no official source describes.
Three groups: what Claude reads in your workspace, what it builds or changes there, and the one tool no source classifies. Names stay exactly as Claude displays them.
- 34 read
- 38 write
- 1 not documented
Tools index
- brain_ask
- generate_outbound_url
- generate_outbound_urls_from_csv
- get_analytics
- get_credits
- get_design_system
- get_domain_status
- get_form_questions
- get_hot_leads
- get_landing_page_template
- get_morning_briefing
- get_page
- get_plan_status
- get_product
- get_product_insights
- get_product_structure
- get_product_url
- get_recent_activity
- get_response
- get_segment_breakdown
- get_started
- get_talking_points
- get_template_share_link
- get_variables
- get_welcome_html
- get_workspace_stats
- list_brain_sources
- list_marketplace_templates
- list_products
- list_result_templates
- list_themes
- plan_product
- preview_outbound_personalisation
- search_responses
- add_brain_memory
- add_brain_source
- add_mcp_connection
- add_node
- apply_theme
- clone_product
- create_page
- create_product
- delete_brain_item
- delete_node
- delete_page
- delete_product
- enable_outbound_personalisation
- generate_product
- publish_product
- revise_product
- save_idea
- set_agent_fields
- set_custom_branding
- set_custom_domain
- set_design_system
- set_product_slug
- set_submission_cap
- set_variable
- set_webhook
- set_welcome_html
- set_workspace_domain
- tag_response
- update_branding
- update_form_questions
- update_mcp_connection
- update_node
- update_page
- update_product
- update_product_settings
- update_response_status
- update_seo
- upload_image
What Claude reads (34)
34 toolsThirty-four tools that look at products, leads, pages, plans and Brain, and leave them untouched.
brain_ask
Puts a strategic question to Brain, Productised's advisor, which loads your workspace context automatically before it answers. Claude relays the question and brings Brain's answer back into the conversation.
generate_outbound_url
Produces one link to a product with any key and value parameters you choose, and warns when a parameter is not wired into the product. Productised says it replaces the older get_product_url for outbound use.
generate_outbound_urls_from_csv
Takes a list as CSV text and returns it enriched with a new column of outbound links, one personalised link per row; an optional key mapping lets a header such as First Name match the token firstName.
get_analytics
Returns a product's response count, last submission, 14-day trend and completion rate, which Productised offers for any product. The trend covers the last 14 days of submissions.
get_credits
Shows a visual credit gauge: plan title, balance, usage this period and all time, per-product breakdown and BYOK status, meaning whether you bring your own AI key. Productised says Claude uses it for questions on credits, usage or cost.
get_design_system
Reads the workspace design-system tokens, brand colours, fonts and corner radius, with platform defaults filled in for anything left unset.
get_domain_status
Checks whether DNS has propagated for a product's custom domain, so Claude can tell you whether the address is ready to use.
get_form_questions
Lists the current intake questions of a product, with their names, labels and the flag that says whether each one is required. Productised returns the set as it stands today, required fields marked.
get_hot_leads
Returns your most promising leads across all products, those tagged hot-lead or carrying a high AI score, with optional filters on product, score threshold and lookback period.
get_landing_page_template
Fetches the designer-built default landing page, in grid or signature style, already themed to your product's brand colour. Productised presents it as the starting point for a custom welcome page.
get_morning_briefing
Delivers a full daily briefing: new leads today against yesterday, hot prospects needing attention and a per-product activity breakdown, with no parameters to give. Productised suggests starting each session with it.
get_page
Retrieves the current HTML and tokens of the output pages of a product's Page node, the result screens respondents reach. The HTML comes back with the tokens the page uses.
get_plan_status
Reports your current Productised plan, usage of every gated feature such as live products and AI credits, and the links to upgrade or bring your own key.
get_product
Returns the full details of one product: its form questions, its workflow structure and the identifiers of its nodes, which the node tools then need.
get_product_insights
Brings back AI-generated insights across all the submissions of a product: patterns, surprises and opportunities. Productised generates them; Claude retrieves them. They are built across all submissions of the product, not response by response.
get_product_structure
Shows a product's node graph: which nodes exist, how they connect and what each one does in the flow.
get_product_url
Returns a shareable link to a product, optionally pre-filled with a contact's name and email so it is ready to paste.
get_recent_activity
Returns a feed of recent submissions across all products, with contact details, product, segment, pipeline status and tags. The feed spans all the products of the workspace at once.
get_response
Opens one response in full detail: all form answers, the AI outputs, tags, status and contact information. It is the full record behind one line of the activity feed or of a search.
get_segment_breakdown
Shows how respondents segment by the persona or tier the AI determined for them, across products. The persona or tier comes from the product's AI, not from a manual label.
get_started
Displays the personalised welcome and getting-started panel, which Productised describes as useful on a user's first interaction. It shows a panel and leaves products and leads as they are.
get_talking_points
Produces ready-to-use conversation starters for a sales follow-up, generated from one end user's data. They are meant for a sales follow-up conversation, ready to use as they come.
get_template_share_link
Gives you a marketplace link to share one of your own products. Anyone with the link reaches its install page and can copy the product into their own workspace, while your original stays untouched.
get_variables
Lists every token available in a product, form fields, node outputs, objects and custom values, with labels and syntax ready to copy.
get_welcome_html
Fetches a product's current custom landing page, which Productised says is so Claude can iterate on it. It returns the page currently attached to the product, code included.
get_workspace_stats
Returns account-wide totals, products created, live products, responses and leads, plus ready-made links to settings, billing and subscription management, members and variables. Productised pairs it with get_plan_status to show value next to usage.
list_brain_sources
Lists every source Brain currently has in its knowledge base, so Claude can tell you what Brain is drawing on. Each source is a URL or a text, as Productised describes them.
list_marketplace_templates
Browses public marketplace templates inside Claude as a visual gallery with filter chips for industry, GROW stage and search. Install and Preview buttons on each card lead to the marketplace page, opened in a new tab.
list_products
Lists all your AI products with their names, response counts, visibility and public links. The public URLs it returns are the ones to share for each product.
list_result_templates
Shows the gallery of result-page designs, such as Dimensions, Radar, Persona or Narrative Report, to preview before choosing.
list_themes
Lists all 20 visual theme presets with their name, description, primary colour and font. The names listed are the ones apply_theme expects when a preset goes on a product.
plan_product
Analyses a product idea in plain words and recommends an outcome type and funnel stage, shown as a blueprint card.
preview_outbound_personalisation
Renders the welcome text, subtitle, custom HTML and starters twice, with sample details and with none, so you see both versions before anything is saved.
search_responses
Filters responses by date, segment, status, tags, keyword or contact details. Productised calls it the general-purpose find tool. Contact details count among the filters, so a name or an email works too.
What Claude changes (38)
38 toolsThirty-eight tools that build, edit, publish or delete. No source spells out their confirmation, so the general rule below applies.
add_brain_memory
Approval: see the ruleStores a fact or preference in Brain's long-term memory, so its later answers take it into account.
add_brain_source
Approval: see the ruleFeeds Brain's knowledge base with a new source, a URL or a block of text.
add_mcp_connection
Approval: see the ruleConnects a product to an outside service, such as a CRM or a note-taking tool, so the product's AI can use that service's tools live during conversations with respondents.
add_node
Approval: see the ruleInserts a node into a product's canvas, an AI step, a document builder, a design page or an advisor chat, and wires it into the flow.
apply_theme
Approval: see the ruleApplies one of the named theme presets to a product in a single call.
clone_product
Approval: see the ruleCopies an existing product so it can serve as a template for a new niche or audience.
create_page
Approval: see the ruleAdds a new HTML page to a product's design node, one more personalised screen at the end of the flow.
create_product
Approval: see the ruleOpens a new, empty product record; its conversation flow and prompts stay blank until generation runs.
delete_brain_item
Approval: see the ruleRemoves a memory or a knowledge source from Brain.
delete_node
Approval: see the ruleTakes a node off the canvas and cleans up the connections around it.
delete_page
Approval: see the ruleRemoves a single output page from a product's design node.
delete_product
Approval: see the rulePermanently deletes a product along with all its responses, pages and digital card links.
enable_outbound_personalisation
Approval: see the ruleWires address-based personalisation into a product, adding tokens with fallback text to its content and recording which fields it accepts.
generate_product
Approval: see the ruleRuns AI generation on a freshly created product to build its conversation flow, collection goals, system prompt and canvas workflow.
publish_product
Approval: see the ruleSets a product to public and returns its live shareable link.
revise_product
Approval: see the ruleRuns generation again on an existing product from a revised prompt, replacing the whole workflow.
save_idea
Approval: see the ruleSaves a product idea straight to the Ideas tab of Brain.
set_agent_fields
Approval: see the ruleConfigures the structured outputs of the product's AI agent, the score, tier, dimensions and insights it produces for each respondent; this is how scoring is set up.
set_custom_branding
Approval: see the ruleReplaces the Productised footer badge with your own logo and click-through link, distinct from the chat-header logo.
set_custom_domain
Approval: see the ruleConfigures a custom hostname for one product and returns the exact CNAME record to add at your registrar.
set_design_system
Approval: see the ruleSaves workspace-wide design tokens that every brand-aware surface inherits, from new themes to result-page chrome, or clears them.
set_product_slug
Approval: see the ruleNames the path of a product under your workspace domain, so the address reads like a real page of your site.
set_submission_cap
Approval: see the ruleCaps how many submissions a product accepts; new sessions are blocked once the cap is reached, while conversations already under way finish.
set_variable
Approval: see the ruleAdds or edits a workspace variable that every product can then use as a custom token.
set_webhook
Approval: see the ruleAdds, replaces or removes an outgoing webhook that pushes full response data to your URL on each submission.
set_welcome_html
Approval: see the ruleSaves a custom HTML landing page on a product, the first screen respondents see.
set_workspace_domain
Approval: see the ruleConfigures a hostname for the whole workspace, under which every product is served unless it has its own override.
tag_response
Approval: see the ruleAdds, removes or replaces tags on a response, such as hot lead, booked call or converted.
update_branding
Approval: see the ruleSets a custom logo and an optional click-through link for a product's chat header.
update_form_questions
Approval: see the ruleReplaces the whole set of intake questions of a product.
update_mcp_connection
Approval: see the ruleAdjusts an existing connection node: its server address, its token, or which of its tools are on or off.
update_node
Approval: see the rulePatches the configuration of any canvas node, by its identifier or its type, for targeted edits.
update_page
Approval: see the ruleReplaces the HTML, and optionally the CSS, of an existing result page.
update_product
Approval: see the rulePatches a product's top-level settings: name, visibility and AI chat settings such as welcome message, button text, button colour and system prompt.
update_product_settings
Approval: see the ruleLocks submissions after a set number of responses and switches email notifications on or off.
update_response_status
Approval: see the ruleMoves a lead through your pipeline, from new to contacted, in progress, converted or lost.
update_seo
Approval: see the ruleSets the page title, meta description, share card, favicon and keywords of a product's public page.
upload_image
Approval: see the ruleRe-hosts an image, from a URL or encoded data, on Productised's own delivery network and returns a permanent link.
Unclassified (1)
1 toolProductised describes this tool, but no source says whether it saves anything. We leave it unclassified rather than guess.
generate_plan
Productised describes this tool as producing a full-funnel journey plan from Brain, with product recommendations at every stage. No source says whether that plan is stored in the workspace or only shown, so we do not classify it as reading or changing. The general approval rule covers it.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account on your behalf. The request shows up in the conversation at the moment it matters.
No source says whether Claude asks before a given Productised tool, so that default rule covers the thirty-eight changing ones. Productised adds a second step of its own only for deleting a product, which requires an explicit confirmation flag. Every call Claude makes is recorded in the workspace's API logs with the tool, parameters, result and origin. On Team and Enterprise workspaces, owners can restrict what a connector may do for the whole organization.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: a real 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 enables a connector for the organization before members can sign in. For the current state, check the Productised sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a respondent submits, a lead turns hot or a cap is reached.
This connector has no Claude help article of its own; what we know comes from the directory sheet and from Productised's documentation of its Claude connector, including its pages on tools and on privacy and security. The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The directory's verified badge is not a security audit, and Anthropic writes on every sheet that it does not control which tools a publisher exposes.
Need help connecting Productised to Claude?
A person reads every message.