Cora monitors your connected integrations and automatically detects lifecycle events — things like renewal risks, stakeholder changes, expansion opportunities, and onboarding milestones. Detected events appear on the Signals page and can trigger agent workflows automatically.

Cora uses two detection modes:

Beyond automatic detection, you can also add a lifecycle event to an account yourself. This is useful for capturing moments that happened offline or outside your connected tools. See Adding an Event Manually below.

Before Signals can detect events from a source, Lifecycle Events must be enabled on that integration.

When you enable an integration, its source is automatically added to matching event types.

Integrations that support Signals:

The Signals page shows all lifecycle events Cora has detected, with severity, source, and timestamp.

You can filter events by:

Click any event to see full details, a link to the original source record, metadata, and to provide feedback.

Beyond the events Cora detects automatically, you can record a lifecycle event yourself. This is useful for moments that happened offline or outside your connected tools, such as a kickoff meeting, a go-live, or an executive change you heard about directly. Manually added events appear in the same Signals list as detected events and can feed configured columns and rollups.

Click Create event in the top-right of the Signals tab, then fill in the form:

Click Create event to save. The event is processed in the background, so a short "being processed" banner may appear before it lands in the list a moment later.

Manually added events are marked with the Cora logo in the Source column instead of an integration icon, labeled Added in Cora when you hover over it. The person who added the event, or an org admin, can remove it using the delete option on the event.

You can also record a lifecycle event just by asking Cora in chat, for example "log a go-live for Acme on Friday." Cora creates the same manual event, and it appears on the account's timeline like any other.

Note: Manually added events are recorded on the timeline but do not start agent workflows by default. This is different from the trigger icon described in Agent Triggers below, which re-fires an event that already exists.

Cora comes with a default set of event types organized into categories like Commercial, Stakeholder Changes, Onboarding, Adoption, Value Delivery, Sentiment & Risk, and Support & Product. Each category groups related event types — for example, Commercial includes events like renewal risks, expansion opportunities, and competitor mentions.

You can see the full list by navigating to the Lifecycle Events tab in your organization settings. Every event type has a prompt that describes what Cora should look for, and you can edit any of them to better fit your business.

To customize how Cora detects events, go to your organization’s Lifecycle Events tab (admin access required). Click any event type to open its settings.

For each event type, you can configure:

If the defaults don’t cover a lifecycle moment you care about, you can create your own:

Custom event types are marked with a “Custom” badge in the list.

Detection conditions let you define precise rules for when an event should fire. This is primarily used for rule-based event types.

Rule-based conditions match current field values — not necessarily when those values changed. Without a date window, records that already match your rules can still produce Signals (including when you first enable Signals, or when unrelated fields are updated). Add a date compare on the date field that represents the event, and combine it with your other conditions using ALL.

Example (CRM): close date within the last 14 days plus stage or pipeline. Prefer the business event date over last modified; any edit can update last modified and re-match state-only rules.

A record may keep matching your rule while it stays inside a date window (for example, “close date within the last 14 days”), but Cora deduplicates Signals so the same event is only detected once. You’ll typically see another Signal only when something is genuinely new — a different record, a different event type, or a rule change. See the Signals FAQ for more.

Detected events automatically fire signals that can activate agent workflows. Agents can be configured to listen for specific event types — for example, “run this playbook when a Renewal At Risk event is detected.”

You can also trigger an event manually from the Signals page by clicking the trigger icon on any detected event.

This is different from Adding an Event Manually above: the trigger icon re-fires an event that already exists, while adding an event records a new one on the timeline. Manually added events do not start agent workflows by default.

You can give thumbs up or thumbs down on any detected event. This feedback helps Cora improve classification accuracy over time.

When marking an event as incorrect, you can specify why: incorrect classification, miscategorized, not useful, misattributed, or other.

If you want to start over, click Reset to Defaults on the Lifecycle Events tab. This restores all categories and event types to their original configuration.

Warning: Resetting permanently deletes any custom event types you’ve created.

Having trouble with Signals? See the Signals FAQ for common questions about why events may not appear, sync timing, rule-based detection noise, and how matching works.