Productivity · Integration
TaskRay
Add TaskRay to your product for your customers, and give your AI agents governed access to it.
TaskRay is project management that lives inside Salesforce rather than beside it, which changes the integration in one important way: there is no separate TaskRay API or login. Its projects, tasks, task templates and assignments are custom objects in the customer's own Salesforce org, reached through that org's API, governed by that org's sharing rules and counted against that org's request allowance. So the customer authorises Salesforce, and what your product maps are TaskRay's managed package objects plus whatever fields that org added to them. Because TaskRay is usually used for customer onboarding and implementation work, a project normally hangs off an account or an opportunity, which is what makes it worth reading alongside the CRM records rather than on its own.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer authorise their Salesforce org, then read and write the TaskRay projects and tasks that live inside it.
Create a project from a template when a deal closes, so onboarding starts without anyone opening Salesforce.
Read task status, assignee and due date so your product shows where an implementation has stalled.
Pace calls inside the org's Salesforce request allowance, since TaskRay shares it with every other tool that customer connected.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which onboarding projects are behind and which task is blocking each.
An agent creates or reassigns a task within the permissions the connected user holds, with the change logged.
An agent answers what stage a customer's implementation is at by reading the project against its account.
Example prompt
Which onboarding projects are past their due date, and who owns the task holding each one up?
Set up TaskRay in 4 steps
- 01Enable the TaskRay connector in your fastn dashboard.
- 02Have each customer authorise their own Salesforce org, since TaskRay is reached through Salesforce rather than a separate login.
- 03Map the TaskRay project, task and assignment objects with any fields that org added, and confirm its sharing rules allow the reads you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the TaskRay integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a TaskRay integration without building it. Your customers connect their own TaskRay account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a TaskRay update is not your on-call problem.
- One integration serves your product and your agents. The same governed TaskRay connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Rocketlane
AsanaWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to TaskRay, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceTaskRay integration FAQ
How do I add a TaskRay integration to my product?
Enable the TaskRay connector in your fastn dashboard, then let each customer authenticate their own TaskRay account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no TaskRay client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own TaskRay account?
Yes. Every connection is scoped to the individual customer, so each authorises their own TaskRay account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this TaskRay integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which onboarding projects are behind and which task is blocking each.
Who maintains the TaskRay integration?
fastn does. When TaskRay changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in TaskRay automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in TaskRay can trigger your workflows in return.
Does it adapt to each team's own TaskRay setup?
Yes. However a team has configured TaskRay, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the TaskRay integration?
A common starting point: let each customer authorise their Salesforce org, then read and write the TaskRay projects and tasks that live inside it. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the TaskRay integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding TaskRay does not change your per-connector cost. You can start free with 3 connected accounts.
Add TaskRay to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.