Get the Megaplan deal summary ready before the stand-up

The agent calls the third version of the Megaplan API at your account address: deals, tasks, projects and contractors — four sections that almost any report is assembled from. On them it totals the value in play by stage and manager, stalled deals, tasks overdue or nearing a deadline, and employee activity for the period. The card of a particular deal or task is read with a separate request when the details are needed, rather than pulled in wholesale.

Megaplan has its own request style: filters, fields and sorting are passed as a JSON structure right inside the address, and related entities arrive as references — the contractor on a deal is an identifier, not a name. So the agent lists the fields it needs and pulls relations deliberately, otherwise the response swells and the report shows a number where the client should be. Megaplan combines a CRM and a tracker, and the owner of a task is far from always the manager of the deal — the agent does not confuse the two.

As writes the agent creates deals and tasks, changes statuses and assigns owners: it can sort incoming requests and open cards for them by your rules. A deal status change is confirmed separately — in Megaplan that is an event with notifications and transitions hanging off it. New, changed and deleted deals and their status changes arrive from Megaplan as signed webhooks, so a reaction does not wait for the next poll.

The connection runs on the login and password of an account: the agent exchanges them for a token that lives about an hour and renews itself, with no keys to copy by hand. Megaplan hands out long lists in pages with a cap on the selection size, so the agent walks the period page by page and adds the total up itself instead of cutting the report off at the first hundred. Requests to deals, tasks, contractors and projects go at a gentle pace, and bulk operations rarer still. If there are no records for the period, the agent says so directly instead of showing an empty table.