Connectv1

Obligations and reminders

Keep track of what your contracts say you owe, by when, and who looks after it. Nexra reminds the owner before each due date and when one is missed.

Updated 11/10/2026

On this page

Contracts and agreements are full of promises: send a monthly volume statement, renew insurance every year, report usage each quarter. An obligation is one of those promises, written down in Nexra with its due date, how often it repeats and who looks after it. Nexra reminds the owner before it is due and again if it is missed, so nothing slips.

Open Connect → Obligations in the console to see them all, soonest first, with how many are due soon and overdue.

Add an obligation

Choose Add obligation and fill in:

FieldWhat to enter
Contract or agreementIts reference, for example "Gas supply agreement GSA-2024-07"
CounterpartyWho it is owed to or by
What is owedIn plain words, for example "Send the monthly volume statement"
Due dateThe next due date
RepeatsOnce, every week, every month, every quarter or every year
Source clauseOptional: the clause it comes from, for example 7.2
OwnerA workspace member, or a team such as Finance
Remind this many days before14 unless you choose otherwise (1 to 365)
Evidence linksOptional: up to 20 links to the contract or proof it was done

You can also ask Nexra Agent in plain words, for example "remind Finance 14 days before the monthly volume statement under clause 7.2 is due". It prepares the obligation and a different person who manages records approves it. Flows can add obligations too, for example from each newly signed contract (see Built-in steps).

Statuses

StatusMeaning
OpenWaiting for its due date
Due soonThe due date is within the reminder time
OverdueThe due date has passed and it isn't marked done
DoneCompleted
WaivedNo longer needed; the reason is kept

Choose Mark done when it is met, and add evidence links if you have them. A repeating obligation moves on to its next due date and stays open, so you never need to add it again. Waive it with a reason when it no longer applies, and Reopen it if that changes.

Reminders

Once a day, early in the morning (UTC), Nexra checks every open obligation:

When it comes within its reminder time, the owner gets a due soon reminder in the console inbox.

When its due date passes without it being marked done, the owner gets an overdue reminder.

Each reminder is sent once per due date, so nobody is reminded twice about the same thing. If the owner is a team rather than a person, the workspace owners and admins are reminded. When a repeating obligation is marked done, the reminders start again for its next due date.

The same reminders reach:

The daily digest: an Obligations section lists what is overdue and due soon, with links.

Your own systems: the obligation.due_soon and obligation.overdue webhook events, so you can open a ticket or post to a channel.

Who can do what

Everyone who can see Connect, apart from documentation editors and billing administrators, can see obligations.

Owners, admins, Connect operators and developers can add, change, complete and waive them.

Over the API

All routes are under /api/console/connect and are in the API reference under Records.

Method and pathWhat it does
GET /obligationsList, with counts. Filter by status (open, due_soon, overdue, done, waived or active), q, reference, ownerUserId, limit
GET /obligation-ownersMembers who can own an obligation, by name
POST /obligationsAdd one
GET /obligations/:obligationIdRead one
PATCH /obligations/:obligationIdChange it. Send only the fields to change; status: "waived" with waivedReason waives it, status: "open" reopens it
POST /obligations/:obligationId/completeMark the current due date done, with optional evidenceLinks
http
POST /api/console/connect/obligations
Content-Type: application/json

{
  "reference": "Gas supply agreement GSA-2024-07",
  "counterparty": "Northfield Power",
  "text": "Send the monthly volume statement",
  "dueDate": "2026-10-31",
  "recurrence": "monthly",
  "sourceClause": "7.2",
  "ownerTeam": "Finance",
  "reminderLeadDays": 14
}

ownerUserId (from GET /obligation-owners) makes a member the owner instead of a team. Owners are shown by name only, never by e-mail address.

Need a hand?

Ask Nexra Agent for implementation steps or error guidance.

Ask Nexra Agent