TaskRay MCP: Bulk Create and Bulk Update

When someone in your org asks their AI assistant to lay out a Project's Task Groups and Tasks in one go, or to move a whole column of Tasks on Kanban, the assistant uses the bulk tools in this article. Each one runs with the user's own Salesforce permissions, so a record changes only if the user could change it in TaskRay themselves.

What the Assistant Can Do in Bulk

What the assistant can do A user might ask Waits for approval
Create many Projects "Create empty projects for Northwind and Contoso, both starting 1 December." Yes
Update many Projects "Archive the onboarding projects we finished last quarter." Yes
Create many Task Groups "Add Discovery, Design, Build and Launch task groups to the Acme Onboarding project." Yes
Update many Task Groups "Mark the Discovery task group complete on every onboarding project." Yes
Create many Tasks "Add these twelve tasks to the Discovery task group on the Acme Onboarding project." Yes
Update many Tasks "Move every task in the Discovery task group to Done." Yes
Create many Checklist Groups "Add a Kickoff Prep checklist to each kickoff task in the Acme Onboarding project." Yes
Update many Checklist Groups "Show every Kickoff Prep checklist in Collaboration View." Yes
Create many Checklist Items "Add these eight items to the Kickoff Prep checklist on the Kickoff call task." Yes
Update many Checklist Items "Mark all the Kickoff Prep items on the Kickoff call task as done." Yes

Good to Know

  • Every bulk request waits for the user to approve it, as described in TaskRay MCP Tool Reference: Approvals for Delete, Bulk and Elevated Tools. One request handles up to 200 records of one kind.
  • Records succeed or fail on their own, and the assistant is told which ones failed and why. It resends only those, so the user doesn't end up with duplicates. The exception is a bulk Task update: one Task moving to a Kanban column it can't use stops the whole request before anything moves.
  • If someone changes one of the records between the request and the approval, nothing in the request is written, so their edit isn't overwritten.
  • Your org's custom fields can be set only one record at a time.
  • Records in an active template can't be created or changed.

Frequently Asked Questions

Q. A user approved a bulk update, but none of the Tasks changed. Why?

Great question! Most likely, someone changed one of those Tasks between the request and the approval. TaskRay MCP checks each record again right before an approved bulk update runs, and writes nothing if any of them changed.

Where to Go Next

Have a question this reference doesn't answer? Not to worry, our Support Team is ready to help! Contact TaskRay Support with what the user asked their assistant to do, the exact error text, and whether the org is production or sandbox.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request