Changelog
New updates and improvements to Planhat
You can now read and create documents in Planhat directly through MCP, so all users can move work between Planhat and tools like Claude or ChatGPT and bring the output back in for the team to access and collaborate on.
Use it to:
Build enablement material and pipeline analysis across new business, expansion, and upsell
Profile portfolio health, including churn risk and ICP fit
Surface trends across recent reported issues and feature requests
Analyse or brainstorm in Claude or ChatGPT, then pipe the result straight back into Planhat

OAuth connections to MCP now apply the highest allowed permission level automatically, so all users can connect with minimal setup while admins retain control over the maximum scope.
A few highlights:
Users can set up any OAuth connection without configuring permissions manually
Admins define the maximum scope, which OAuth enforces on every connection
Re-connect in Claude or ChatGPT with your existing setup to apply this

The Salesforce integration now supports formula fields alongside lookup fields for populating associations between records.
Use it to:
Map associations between records that lookup fields alone could not support
Bring across the most important data from Salesforce into Planhat with fewer workarounds
Expand what you can import from Salesforce without restructuring your field configuration
Automations have been updated with several UX improvements that reduce manual setup and make steps easier to configure correctly.
You can now:
Set specific fields when using a GET single step, giving you more control over what data is returned
Add, replace, or delete values in Team Members fields directly within a step
Smart-fill field values from earlier steps in the same Automation, including outputs from AI steps
Quick-fill IDs based on your trigger:
companyIdauto-populates in Get Company requests when the trigger is not a Company, and the record ID auto-populates in Update steps when the model matches the trigger model

You can now leave start and end dates unset on tasks in Workflow templates, so ad hoc tasks without a fixed deadline don't skew project timelines or trigger false delay flags.
How it works:
Set 0 in Start After Days / Duration to schedule a task for the same day
Leave Start After Days / Duration empty to create a task with no set dates (similar to "Someday" on standalone tasks)
Existing Workflows and templates are unaffected (previously empty or 0 values continue to be treated as same day)
Monthly scheduling is now available for Automation triggers, letting all users with access to App Center run automations on a chosen calendar day.
For example:
Run end-of-month pipeline reviews automatically on the last working day
Generate monthly summaries of feature requests or upcoming renewals
Trigger recurring AI analysis of customer data on a fixed cadence each month

All users can now sort columns and adjust which columns appear in a Data Table widget from the Dashboard itself, without editing the widget or cloning the page.
How to use:
Click any column header in Explore mode to sort ascending or descending
Right-click a column header to add, remove, or reorder columns
Save your sorting order and column selection as the default for that widget, the same way table preferences work elsewhere
Personalize a shared Dashboard view without creating duplicate pages

You can now configure an automation step to update an existing document instead of creating a new one. This feature is available to all customers using automations.
Making the most of this update:
Maintain a single source of truth in Content Explorer instead of accumulating one document per run
Use the previous content as a baseline for AI-driven analysis, such as portfolio-level pipeline reviews or expansion and upsell tracking
Pair with a fixed Section in your Home to keep recurring insights in one place

The new State field on Tasks lets all users identify which tasks are ready to act on, available across all customers using Tasks.
Use it to:
Surface
Activetasks — those not blocked by an incomplete parent, regardless of whether a dependency existsIdentify
Pending parenttasks blocked by a Finish-to-Start dependency, so you know what to tackle nextFilter out
Hiddentasks where a conditional workflow's criteria are not yet met
All users can now add a Done Date column to Workflows and Workflow Templates, showing the actual day a task was completed rather than its planned End Date.
Using this feature:
Add the column directly in a Workflow Template to have it appear by default in any applied Workflow
Compare planned End Date against actual Done Date to see how delivery tracks against intent
Feed completion patterns back into templates, forecasts, and SOWs


