The short answer
Deal history answers two questions: what changed, and when. Keep interaction notes separate from structured audit records: notes capture human context, while audit events record changes such as a stage move with an event type, source, prior value, new value, timestamp, and user reference. Tasks and buying-committee associations are separate deal records to review alongside that history. A documented API route lets an authenticated client request a deal’s timeline by ID.
Source check: Deal and audit field names, the timeline endpoint, stage-change audit behavior, notes on the deal timeline, and audit tracking were checked August 30, 2026 against the canonical Deal Flow domain specification, the published REST endpoint table, the published deal API documentation, and the published release notes. This guide distinguishes documented records and does not infer an undocumented timeline response.
Read history and current work as different questions. Historical records explain activity and changes. Open tasks tell you what needs attention now. Contact associations tell you who is currently involved and the role each person holds.
Four records that support a deal review
Deal Flow keeps several kinds of information on the same deal without treating them as interchangeable. Start by choosing the record that answers the question in front of you.
| Record | What it carries | Question it answers |
|---|---|---|
| DealNote | Body, activity type, deal, and author reference | What interaction or context did someone record? |
| DealAuditEvent | Event type, source, prior value, new value, timestamp, and user reference | What structured change was recorded, and when? |
| DealTask | Title, status, priority, due date, reminder, and owner | What follow-up remains open or has been completed? |
| DealContactAssociation | Mautic contact, deal, and buying-committee role label | Who is involved in the deal right now? |
A note can use an activity type such as note, call, email, meeting, or task completion. A task remains its own follow-up record. A contact association remains the current link between a Mautic contact and the deal. Keeping those meanings separate makes handoffs easier to read.
What a DealAuditEvent records
The underlying DealAuditEvent belongs to one deal. Its documented fields identify the event type, the source of the change, prior and new values, the creation time, and the Mautic user reference when available.
- Event type names the kind of change recorded.
- Origin identifies the documented source category. The domain specification defines user, campaign, webhook, and API values.
- Prior and new values hold the before-and-after context supplied for that event.
- Creation time supplies the event timestamp, while the user reference identifies the associated Mautic user when one is recorded.
These fields let a reviewer separate a user-originated change from an API-originated one and read the values recorded for that event. Their exact meaning still depends on the event type, so a missing value should not be filled in by assumption.
How stage moves create audit history
The published deal API documentation says that moving a deal to another stage triggers a stage-change audit event and synchronizes the deal status.
That gives a review a concrete starting point: identify when the stage changed, read the recorded prior and new values, and check the event source. Then review deal notes separately for relevant human context.
Use the timestamp as the anchor. It answers when the structured change was recorded. Review notes separately for any recorded call, email, meeting, or written context.
A practical deal-history review
Suppose a deal is in the Proposal stage and a teammate needs to take over. Review the records in a deliberate order:
- Locate the relevant stage event. Read its timestamp, source, and recorded prior and new values.
- Review deal notes separately. Use the interaction type, author, and body to understand any context that was recorded.
- Inspect open tasks separately. Their status, priority, due date, reminder, and owner describe the next work rather than the past event.
- Check the current buying committee. Contact associations show which Mautic contacts are tied to the deal and the role label stored for each association.
This sequence keeps evidence, next actions, and current participants distinct. It also helps a reviewer avoid attributing an event to a contact merely because that person appears on the deal today.
Request the documented timeline endpoint
Deal Flow documents GET /api/dealflow/deals/{id}/timeline for requesting timeline events for one deal. The request uses the same Mautic API authentication as the other Deal Flow routes. This Basic Auth example follows the Deal Flow REST API guide.
export MAUTIC_URL="https://mautic.example.com"
export MAUTIC_USER="your-username"
export MAUTIC_PASSWORD="your-password"
curl --user "$MAUTIC_USER:$MAUTIC_PASSWORD" \
--request GET \
"$MAUTIC_URL/api/dealflow/deals/42/timeline"
Replace 42 with an existing deal ID. Keep credentials in environment variables rather than placing working values in a shared command. The published route establishes the request path; this guide does not define response fields, ordering, filters, or pagination that the current public reference does not document.
Keep deal context inside Mautic
Deal Flow adds deal records, structured history, tasks, and buying-committee roles to the Mautic instance your team already uses.
See Deal Flow Options Try free for 7 daysFrequently asked questions
What does a Mautic deal timeline show?
The public documentation names a deal timeline endpoint but does not enumerate its response contents. Separately, DealNote records hold human context and DealAuditEvent records hold structured change details.
Is a task the same as a timeline event?
No. A DealTask is a separate follow-up record with its own status, priority, due date, and owner. Review open tasks separately from the deal's historical records.
Are buying-committee contacts part of the audit history?
Contact associations are separate records linking Mautic contacts to a deal with role labels. Use the current association list to see who is involved; this page does not treat that list as timeline output.
How do I request timeline events through the API?
Authenticate with Mautic and send GET to /api/dealflow/deals/{id}/timeline, replacing {id} with an existing deal ID. Consult the published API documentation for authentication options.