SleekView Kanban for Freshsales for WordPress
SleekView reads the Freshsales contacts and deals the WordPress connector caches locally, groups every deal by the Freshsales deal stage, and lets a sales rep drag a card from Qualified to Negotiation to Won and write the change back through the Freshsales REST API in one motion.
♾️ Lifetime License available
Freshsales is a kanban product, this board lives in WP
Freshsales for WordPress caches Freshsales contacts and deals locally under fs_contacts and fs_deals. Each deal carries a deal_stage_id that maps to a stage on the Freshsales sales pipeline, typically Qualified, Discovery, Quotation, Negotiation, and Won. The default connector admin shows the rows as a list with filters, which is fine for finding one record but never gives a rep the pipeline shape Freshsales itself ships natively.
SleekView reads the same cached rows and the related accounts table the connector keeps. The natural status column is deal_stage_id on the deal, resolved through the cached fs_pipelines table so stage names render correctly. Card meta shows the contact, the account, the amount, and the close date so a rep can run pipeline review without clicking into the Freshsales product itself for every change.
Dragging a card calls the Freshsales connector endpoint, which talks to Freshsales through its CRM REST API. The remote deal updates with the new stage, the activity timeline records the change with the editing user, and any Freshworks workflow rules that key off the stage transition run as they would on a manual edit. Failed writes snap the card back and the API error renders inline.
Workflow
From Freshsales cache to a live kanban
Connect to Freshsales data
fs_deals or its meta companions, and SleekView reads them directly with no extra sync to babysit.
Pick the status column to group by
deal_stage_id column as the kanban grouping. SleekView reads the distinct values currently on rows and builds one column per value in the order you arrange them.
Choose what shows on each card
Enable drag-and-drop writeback
deal_stage_id on the record. SleekView fires the same freshsales_deal_synced hook the plugin uses, so emails, webhooks, and reminders stay attached.
Sample board
Sample Freshsales deals kanban board
Comparison
Default Freshsales connector vs SleekView Kanban
Default Freshsales list
- Freshsales dashboard lives outside WordPress, switching is a context cost every time
- Connector list shows rows with filters, no pipeline shape across the deal stages
- Changing stage means opening Freshsales, editing the deal, and waiting for sync back
- Card fronts do not exist, deal amount and close date hide behind every row link
- Forecast reviews on the connector list end up exported to a slide deck every week
SleekView Kanban
-
Native read of
fs_dealswith Freshsales deal stage detection on every row -
Drag a card to push the new
deal_stage_idto Freshsales via the REST API - Card front shows deal, contact, account, amount, and close date for forecast review
- Filter the board by owner, lead source, or any custom field the connector already syncs
- Lives next to the Freshsales connector admin, no duplicate database, no offline copy
Features
What SleekView Kanban gives you for Freshsales for WordPress
Pipeline by deal stage at a glance
See the count of records in each state the moment the board loads. Freshsales usually buries this behind list filters, but the kanban surface puts it up front so a manager can spot a pile-up in seconds.
One board per record type
Build a separate kanban per Freshsales table. Pair a deals board by stage with a contacts board by lifecycle. Each board remembers its own card template and column order.
Drag-and-drop writeback
Cards do not just show pretty data. Drop one in a new column and SleekView writes back to the Freshsales record, runs the same hooks the admin uses, and the Freshsales remote and timeline update on the next connector sync.
Audience
What sales teams build with SleekView and Freshsales
Weekly forecast review
Open the deals board, drag stuck rows into the right stage, and read totals off the column counts. The default connector list never lays the forecast out this clearly in one screen.
Contact lifecycle triage
Group contacts by lifecycle stage. New inbounds sit ready for a rep to pick up. Dragging the card writes back through the connector so Freshworks rules fire as usual.
Owner load balancing
Filter by owner and you see exactly how much each rep is carrying. Dragging a card from one owner to another reassigns it on the Freshsales deal on the next sync.
The bigger picture
Why a kanban view fits Freshsales in WordPress
Freshsales is itself a kanban product, with stages on a board and deals as cards. The WordPress connector brings the data into WordPress so the marketing site can read deal and contact context, but the connector admin only exposes the cached rows as a flat list. That works for cross referencing a contact next to a form submission, but it loses the pipeline shape that the Freshsales product itself sells.
With SleekView Kanban the cached rows become a board again. Stages are columns, deals are cards, and the count on each column shows how the pipeline is loaded today. Drag-and-drop writeback uses the connector REST endpoint the plugin already exposes, so a card move on the WordPress board updates the Freshsales remote and the activity timeline records the same change a manual edit would.
The marketing team gets the pipeline view they expect from Freshsales, without leaving the WordPress admin they already work in.
Questions
Common questions about SleekView Kanban for Freshsales for WordPress
Both. SleekView reads Freshsales for WordPress tables and the deal_stage_id column at the database level, so whichever tier you run the board still builds. Paid add-ons that add custom fields or extra status values are picked up automatically because SleekView scans the live schema on render.
SleekView calls the Freshsales connector update endpoint, which talks to Freshsales through its CRM REST API. The plugin fires its normal deal synced hooks, so any local listeners and any Freshworks workflow rules that key off the stage transition run exactly as they would on a manual edit in Freshsales.
Yes. Card layouts are per board. A deals board can show deal title, contact, account, amount, and close date. A contacts board can show name, lifecycle stage, owner, and last activity. Each board remembers its own card template so the team does not reconfigure when switching.
Yes. SleekView respects every capability check the connector plugin registers. A user who can read but not write deals will see cards but the writeback only fires for users whose role matches the same checks the connector enforces when a manual save is attempted from its admin.
Add the new stage in Freshsales the normal way, by editing the pipeline settings. The connector syncs the new stage into the local cache, and SleekView picks it up on the next board load because columns come from the distinct stage values currently present on rows.
No. SleekView paginates cards per column rather than fetching every row at once. The cache table carries an index on the stage column so counts and a window of cards stay fast even on a Freshsales tenant with tens of thousands of deals flowing through the connector each year.
Yes. Any cached Freshsales table with a status like column can render. Contacts grouped by lifecycle stage, accounts grouped by tier, and tasks grouped by status are common boards once you point SleekView at the right table and pick the column you want to group on.
It stays in sync because there is no separate database. SleekView reads the cached fs_deals rows the connector reads. Writes call the connector endpoint that talks to Freshsales REST, so the kanban board and the Freshsales remote stay aligned without any extra cron sync drift.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout