One AI admin for Salesforce and HubSpot configuration
Ask for a change in plain language. Wrenk reads the org, plans the change, and asks before it writes to production.
Yes. Wrenk is one AI admin that makes configuration changes in both Salesforce and HubSpot. You ask for a change in plain language in Claude, ChatGPT or the Wrenk app; Wrenk reads the connected org, proposes a plan that names what depends on the thing being changed, and asks for explicit confirmation before it writes to production. Coverage is deeper on Salesforce, where changes can run in a sandbox first and deployments can be rolled back; on HubSpot it creates properties, forms and workflows and manages CRM records, without sandbox routing.
- Salesforce: fields and objects, picklist values, validation rules, record types, permission sets and field-level security, page layouts, flows, Apex deployment, and users.
- HubSpot: properties, forms, workflows (create, turn on or off), and contacts, companies, deals and tickets.
- Both: a health check of the connected org, one sign-in, and a person confirming production changes.
What a configuration backlog is
A configuration backlog is the queue of small change requests that builds up behind whoever administers a CRM. Each one is minor on its own. Together they are the reason a two-line request waits three weeks. In Salesforce and HubSpot the requests are mostly of these kinds:
Fields and properties
Add a field to an object in Salesforce or a property in HubSpot, or change the type, label or length of one that exists.
Picklist values
Add a stage, status or option, including the attributes that make it behave correctly, such as whether an opportunity stage counts as closed or won.
Validation rules
Require a value, block a bad combination, or relax a rule that is stopping people from saving records.
Flows and workflows
Create an automation, turn one on, or turn off one that is misfiring.
Permissions and field visibility
Grant access through a permission set, set field-level security, or work out why a field that exists is not showing for a particular user.
Page layouts
Put a new field where people will see it, or tidy a layout that has grown crowded.
Users and access reviews
Create or deactivate a user, assign a permission set, and review who holds which access.
Cleanup of unused items
Find fields, automation and permissions nobody uses, check what still references them, and plan their removal.
What Wrenk does in Salesforce and in HubSpot
The two columns are not equal, and the table says where. Salesforce coverage is broader and includes sandbox-first deployment. HubSpot coverage is narrower.
| Area | Salesforce | HubSpot |
|---|---|---|
| Health check of a connected org | Security settings, permissions, automation, data model, Apex, licences and installed managed packages. Managed-package metadata is attributed to its vendor, not scored as yours. | Health check of the connected portal. Items HubSpot does not grant access to are reported as not assessed, not as passing. |
| What it reads | The org's configuration and records, including what references a given field. | Contacts, companies, deals, tickets, properties, pipelines, forms, marketing emails, owners, users, teams and roles. Some reads depend on the portal's HubSpot tier; workflows and teams, for example, are available on Professional tiers. |
| Fields and properties | Creates and changes custom fields and custom objects. | Creates properties. |
| Picklists, validation rules, record types | Adds picklist values, and creates and changes validation rules and record types. | No equivalent operations in Wrenk today. |
| Automation | Creates flows and activates or deactivates them. Deploys Apex classes and triggers. | Creates workflows and turns them on or off. |
| Permissions and visibility | Permission sets and field-level security. Diagnoses why a field is not visible to users. | Reads users, teams and roles where the portal's tier allows it. Does not change them. |
| Page layouts and forms | Updates page layouts. | Creates and updates forms. |
| Users | Creates, updates and deactivates users, and assigns permission sets. | Reads users and owners. Does not create or deactivate them. |
| Records | Creates and updates records. | Creates and updates contacts, companies, deals and tickets. |
| Planning before a change | Before a field change, reads what references the field and returns an ordered plan. | Reads the portal's existing properties, forms and workflows before proposing a change. |
| Sandbox first | Yes. A production deployment needs a connected-sandbox check plus explicit confirmation. | No. Wrenk has no sandbox-first routing for HubSpot. |
| Tracking and rollback | Deployments are tracked and can be rolled back. | Changes are recorded. Deployment rollback applies to Salesforce only. |
| Known gaps | Large-team release pipelines with Git-based CI/CD are better served by a dedicated DevOps tool. | HubSpot has no API for SSO settings or login history, so Wrenk cannot read or change them. |
More detail on each health check: Salesforce health check and HubSpot health check.
How a request moves
The path from request to recorded change is the same each time: request, read, plan, sandbox, approval, deployment, record.
Ask in plain language
Describe the change in Claude, ChatGPT or the Wrenk web app, the way you would write a ticket for an admin. For example: add a renewal date field to opportunities and make it required at Closed Won.
Wrenk reads the org
It looks at the connected Salesforce org or HubSpot portal to see what exists today: the object, its fields, the automation and rules around it.
It proposes a plan
The plan lists the steps in order and names what depends on the thing being changed. For a Salesforce field change, that means the formulas, validation rules and other components that reference the field.
It runs in a sandbox first
On Salesforce, when a sandbox is connected, the change is checked there before production. HubSpot changes are made in the connected portal; Wrenk has no sandbox routing for HubSpot.
A person confirms the production write
Wrenk asks for explicit confirmation before it writes to production. Nothing reaches production on the strength of the original request alone.
The change is recorded
Each change is recorded so there is a history of what was done and when. Salesforce deployments are tracked and can be rolled back.
When a different tool is the better choice
Wrenk is for configuration work and org health. Three neighbouring jobs are better done with something else.
- Salesforce release pipelines with Git-based CI/CD at scale
- Gearset and Copado are Salesforce DevOps platforms built for teams that manage releases through version control.
- Record-level dedupe and data cleanup across both CRMs
- Insycle is a data management tool for deduplicating and cleaning CRM records.
- Moving data between the two systems
- The native HubSpot–Salesforce integration syncs records between HubSpot and Salesforce.
FAQ
Is there one tool that manages configuration in both Salesforce and HubSpot?
Yes. Wrenk connects to both a Salesforce org and a HubSpot portal and makes configuration changes in each. On Salesforce it covers custom fields and objects, picklist values, validation rules, record types, permission sets and field-level security, page layouts, flows, Apex deployment and users. On HubSpot it creates properties, creates and updates forms, creates workflows and turns them on or off, and creates and updates contacts, companies, deals and tickets. HubSpot coverage is narrower, and Wrenk has no sandbox-first routing for HubSpot.
Does Wrenk replace a Salesforce administrator?
It does the routine configuration work and health monitoring an administrator would do, with a person approving production changes. It does not remove the need for someone who decides what the business wants and signs off on changes. If you have no one to fill that role, managed hours from a human are available as an add-on.
Does Wrenk change production without asking?
No. A Salesforce production deployment needs a connected-sandbox check plus explicit confirmation, and Wrenk asks for confirmation before a production write. Salesforce deployments are tracked and can be rolled back.
Can I use it from Claude or ChatGPT?
Yes. Wrenk works inside Claude and ChatGPT through an MCP connector, and in the Wrenk web app. You sign in once, and Wrenk only reaches the Salesforce orgs and HubSpot portals that account has connected.
What can Wrenk not do in HubSpot?
Wrenk has no sandbox-first routing for HubSpot, and HubSpot has no API for SSO settings or login history, so Wrenk cannot read or change those. Some reads depend on the portal's HubSpot tier: workflows and teams, for example, are available on Professional tiers. When HubSpot does not grant access to something, Wrenk reports it as not assessed.
How do I try it, and what does it cost?
Start with the free guest health check, a short questionnaire that needs no account and no org connection. A check against live data needs a connected org. Paid plans start at $99 a month.
Related reading
- Salesforce health check — what is checked in a connected Salesforce org.
- HubSpot health check — what is checked in a connected HubSpot portal.
- The Wrenk connector — how to use Wrenk from Claude or ChatGPT.
- Salesforce org health tools compared — how the tools in this category differ.
- Replacing a Salesforce consultant — where software fits and where a person is still needed.
Start with a free health check
A short questionnaire, with no account and no org connection. Connect an org afterwards for a check against live data.