Event:trial.ending· Destinations:ResendIntercomSalesforceHubSpot
The problem
A trial-ending workflow breaks down fast when every destination waits on a different job or export. Email goes out late, Intercom does not know the user is near the end of the trial, and Salesforce never gets the engagement context the rep needs — multiplied by every workspace that has its own mix.
The technical problem is not generating the event. It is delivering that signal to each workspace on time with the fields each destination expects. When those paths drift, your customers see their conversion workflows become inconsistent exactly when timing matters most.
Teams often discover this after a workspace's campaign underperforms or a rep says they never saw the account in time. Reliable per-workspace delivery is what makes a trial-ending workflow usable in practice.
The event flow
Meshes receives the source event once, maps it to the right destinations per workspace, and keeps delivery visible when downstream APIs fail.
Event payload
trial.ending{
"user_id": "usr_8803",
"email": "maria@lighthouse.io",
"trial_end_date": "2026-03-24",
"plan_viewed": "growth",
"features_used": ["exports", "alerts", "crm_sync"],
"days_active": 11
}Meshes triggers the conversion email template the workspace has connected, with trial context and next steps.
Each workspace's email path fires from the actual trial-ending event instead of a delayed batch job.
Meshes tags the user through the workspace's Intercom connection for targeted in-app messaging.
Product and support in each workspace align in-app nudges with the same trial timeline the email system sees.
Meshes updates engagement-related fields using the workspace's Salesforce credentials and mapping.
Reps inside each workspace see who is active, what plan they viewed, and when the trial ends without a manual export.
Meshes updates lifecycle or list state in the workspace's HubSpot connection for conversion-oriented workflows.
Marketing in each workspace keeps audience state in sync with the real trial-ending signal.
How Meshes handles it
Instead of maintaining separate workers, retry logic, and visibility per destination, Meshes gives you one event path, destination-aware routing, and built-in delivery guarantees.
From your product
trial.endingenters Meshes onceimport MeshesEventsClient from '@mesheshq/events';
const meshes = new MeshesEventsClient(
process.env.WORKSPACE_PUBLISHABLE_KEY!,
);
await meshes.emit({
event: 'trial.ending',
resource: 'membership_level',
resource_id: 'growth',
payload: {
user_id: 'usr_8803',
email: 'maria@lighthouse.io',
trial_end_date: '2026-03-24',
plan_viewed: 'growth',
features_used: ['exports', 'alerts', 'crm_sync'],
days_active: 11,
},
});Across destinations
trial.ending event and Meshes resolves the destinations per tenant.On every delivery
Why this matters
A trial-ending workflow only works if the signal arrives when the customer can still act on it. Delayed delivery erases the advantage — in any tenant.
Resend, Intercom, Salesforce, and HubSpot should all react from the same trial context so messaging and outreach do not contradict each other inside a workspace.
Cron jobs and spreadsheet exports are a poor fit for conversion signals. Event routing with retries and replay is easier to reason about and easier to operate across workspaces.
Related
Docs
See the full event-routing flow behind a time-sensitive conversion use case.
Open linkDocs
See the event-ingestion pattern behind this trial-ending workflow.
Open linkIntegration
Update lifecycle state per workspace from event-driven rules instead of delayed CRM syncs.
Open linkIntegration
Tag trial-ending users so in-app messaging and support context stay current in every workspace.
Open linkIntegration
Push engagement and trial context to reps inside each workspace before the trial window closes.
Open linkBlog
Why time-sensitive conversion workflows break when you hand-roll the delivery infrastructure per tenant.
Open linkCompare
Compare event-driven trial routing with maintaining cron jobs and webhook glue yourself.
Open linktrial.ending through Meshes once and keep each workspace's email, CRM, support, and lifecycle tools aligned around the conversion window.