Request reviews on completion
When a project is completed in Simpro, send a review request from pulseM.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
pulseM Explore pulseM →
TriggersFires when a customer leaves a new review in pulseM.
Fires when a review is edited or answered in pulseM.
Fires when a customer answers a feedback survey in pulseM.
Invites a customer to leave a review with pulseM.
Adds or updates a customer contact in pulseM.
Posts a public reply to a review in pulseM.
Simpro Explore Simpro →
TriggersFires when a new task, job or item is created in Simpro.
Fires when a task in Simpro is marked complete.
Fires when a task's due date in Simpro is coming up.
Fires when a task, job or project changes status in Simpro.
Creates a new task, job or item in Simpro.
Updates a task's status or assignee in Simpro.
Posts a comment on a task in Simpro.
Assigns a task in Simpro to a team member.
More pulseM + Simpro workflows
See all pulseM + Simpro integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Request reviews on completion” between pulseM and Simpro?
Yes — describe it in the box above and Knit's Integrations Agent researches pulseM and Simpro's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can reviews create tasks?
Yes. When a new or low-rated review arrives in pulseM, Simpro can create a task to respond.
Can a finished project ask for a review?
When a project or task is completed in Simpro, pulseM can send a review request.