Truto added Salesforce Events for Workweek in 16 hours
Workweek runs a B2B ad platform for newsletters and promises advertisers that every engagement it verifies lands in their CRM. It is building that on Truto's unified CRM API, for Salesforce and HubSpot.
hours to add Salesforce Events
minutes from CLI tip to working calls
minutes to diagnose a HubSpot access problem
Workweek
I made a change on our sandbox using the CLI. I listed and deleted an Event.
Key facts
Workweek at a glance
- Customer
- Workweek
- What they do
- Newsletters, events and a B2B ad network across HR, healthcare, fintech, marketing and ecommerce
- Truto products used
- The unified CRM API, the Proxy API, environment-level overrides and the Truto CLI
- Integrations
- Salesforce, HubSpot and Google Analytics
- Salesforce Events
- Available 16 hours after Workweek asked (Sep 10, 2026)
- Google Analytics
- Switched on in all of Workweek's environments (Sep 18, 2026)
- HubSpot permissions
- Cause confirmed 90 minutes after Workweek reported it (Oct 1, 2026)
Overview
How Truto worked with Workweek
The challenge
Workweek promises advertisers that every engagement it verifies lands in their CRM. It wrote that engagement into Salesforce as Tasks and wanted to write Events instead, which Truto's unified CRM API didn't yet cover for Salesforce.
What Truto did
Truto added Salesforce Events to its unified CRM API, then archived events in Workweek's staging environment when Workweek asked, and switched on Google Analytics in all of Workweek's environments. Requests go through a shared Slack channel.
The result
Salesforce Events arrived 16 hours after Workweek asked, and archived events 19 hours after it asked for them, in Workweek's staging environment. Before Events arrived, Matt Kindy had already listed and deleted one himself with the Truto CLI, minutes after asking.
Timeline, 2026
From Salesforce Events to HubSpot permissions
-
Workweek asks for Salesforce Events. Truto points Matt Kindy to its CLI, and 8 minutes later he has listed and deleted an Event in Workweek's sandbox.
-
Salesforce Events arrive on the unified CRM API: list with a subject filter, create and delete. Workweek asks for archived events too.
16 hours after asking
-
Archived events, such as backdated ones, come back on list calls in Workweek's staging environment.
19 hours after asking
-
Google Analytics is switched on in all of Workweek's environments.
-
One of Workweek's HubSpot connections can't read CRM data. Truto finds HubSpot granted it only 2 permissions: the HubSpot account had optional ones switched off.
Cause confirmed in 90 minutes
Asked → delivered
How fast Truto delivered Workweek's requests
-
90 minutes
Find out why one of Workweek's HubSpot connections couldn't read CRM data, and how to fix it without deleting the account
-
16 hours
Salesforce Events on the unified CRM API: list with a subject filter, create and delete
-
19 hours
Archived Salesforce events, such as backdated ones, on list calls in Workweek's staging environment
For engineers
Under the hood
APIs, permission checks and self-serve tools
Salesforce
- Events through the unified CRM API, as
unified/crm/engagementswithengagement_type=meeting: list with a subject filter, create and delete - List filters on contact, account,
created_atandupdated_at include_archived(default true) andinclude_deleted(default false) onunified/crm/engagementsandunified/crm/tasks, read through Salesforce'squeryAll, withis_archivedandis_deletedon each record, in Workweek's staging environment- Contacts read with
FIELDS(STANDARD), so hidden fields are skipped
HubSpot
- Accounts, opportunities, contacts and pipelines through the unified CRM API
- Scope checks: which permissions HubSpot actually granted a connection, against the ones requested
- Reconnect links that pick up new permissions without deleting the account
Google Analytics
- Installed in Workweek's development, staging and production environments
Self-serve tools
- The Truto CLI, which works with Claude or Cursor through Truto Skills, for environment-level overrides and new unified APIs
- The Proxy API for anything the unified CRM API doesn't cover yet
- Changes reach Workweek's staging environment first, then development and production once Workweek confirms
FAQ
Questions about Workweek and Truto
What does Workweek use Truto for?
Workweek promises advertisers that every engagement it verifies lands in their CRM, and is building that on Truto's unified CRM API for Salesforce and HubSpot. It wrote that engagement into Salesforce as Tasks and wanted Events instead, so Truto added Salesforce Events to the unified CRM API. Workweek has also connected Google Analytics through Truto's Proxy API.
How fast did Truto add Salesforce Events for Workweek?
In 16 hours. Workweek asked on Sep 9, 2026, and by the next day Truto's unified CRM API could list Salesforce Events with a subject filter, create them and delete them. Workweek then asked for archived events, such as backdated ones, and Truto returned them in Workweek's staging environment 19 hours later.
Can Workweek add what it needs without waiting for Truto?
Yes. When Workweek asked for Salesforce Events, Truto pointed Matt Kindy to the Truto CLI, which adds environment-level overrides and unified APIs. Eight minutes later he had listed and deleted an Event in Workweek's sandbox with it. Until the unified endpoint arrived 16 hours after the request, Workweek could use Truto's Proxy API instead.
How did Truto diagnose a HubSpot permissions problem for Workweek?
On Oct 1, 2026, one of Workweek's HubSpot connections couldn't read CRM data. Truto checked which permissions HubSpot had actually granted and found only 2, because optional permissions were switched off in that HubSpot account. Workweek confirmed the cause 90 minutes after reporting it. Truto's recommended fix was to switch those permissions on and reconnect the same account.
Customers
More customer stories
13 integrations live, the first three within a month
Slack, Jira, Google Calendar and more feed 15Five’s AI features for managers, with a public launch about 3 months after kickoff.
Read case study →6 CRMs live within a month of signing
Dynamics 365, HubSpot, Salesforce, Zoho CRM, Pipedrive and Attio through a single API, with each customer’s custom fields mapped both ways.
Read case study →10 more apps in about 2 weeks, ServiceNow HR data in 4 days
Reads users, roles and groups from the apps its customers use, including a long tail of smaller tools, through Truto’s unified user directory.
Read case study →Launched native integrations faster
Leverages Truto’s integrations to enrich its compliance automation platform for SOC 2, ISO 27001, and 16 other frameworks.
Read case study →Want integrations shipped like this?
Tell us which integrations your customers keep asking for. We will show you how Truto would build them, and how long it would take.