Productive

The Productive Ultimate plan, with AI features enabled, is required for its official MCP server. Each person connects their own account, one organisation at a time.

In the web appCopy Anchor Link

Connect and map projectsCopy Anchor Link

In Setup, choose Connect Productive and finish sign-in on Productive's page. The connection page shows the organisation and your name from Productive when it answers.

Choose a zonask role for each Productive project you want that role to see. Unmapped projects do not supply tasks.

Map projects on Productive in Setup. A role page links there with Map Productive projects; it does not show the mapping form. Reconnecting saves the new sign-in, then asks Productive to revoke the old one. If revocation fails, the new connection remains available.

Headquarters shows up to five assigned open Productive tasks under each mapped role in Tasks by role, labelled From Productive. The role page keeps the full list of up to 50. Both are live reads with a five second limit. A blank Productive title appears as (no title); a title over 200 characters is shortened for display. Task titles from these reads are not stored in zonask. On the role page you can mark a task done after your Yes; edit or reopen a task in Productive.

Each mapped project is read on its own, with its own five second limit, so one slow project does not hide the tasks of the others. A project that could not be read is named with its reason: Productive was too slow., Productive refused the read., Productive's answer was too large., Productive's answer could not be read. or Productive could not be reached. On Headquarters a role with such a project says Some Productive projects of this role could not be read.

If Productive is unavailable, or none of a role's projects could be read, zonask says Productive did not answer and you can reconnect. Disconnect asks Productive to revoke the sign-in and removes the connection and its project mappings. Local removal still works when the saved sign-in cannot be read or revocation fails.

Create a task from zonaskCopy Anchor Link

On a needs-you email or a zonask task in a mapped role, choose Create a Productive task. Choose a mapped project and its task list, edit the title and due date, then Propose. The assignee is always you. Nothing is created in Productive until you answer Yes on the desk.

The Yes card names the project, task list, title, due date or No due date, and assignee you. It reads the project and list names live. If Productive does not answer, the card says Productive did not answer. and offers no Yes. zonask does not put the email body in the proposed task.

If Productive does not answer during the Yes check, zonask says Productive did not answer. Your proposal is still open. You can try Yes again later. If the project, list or other proposal details are no longer valid, zonask cancels it. Once a proposal is executed or cancelled, its encrypted title is removed from the plan row. Delete all my data removes the remaining row. The current retention purge does not cover these proposal rows.

Mark a task doneCopy Anchor Link

On a role page, each task under From Productive has Mark done. The next page shows the task, its number, its project and the status it will get. When the project's workflow has one closed status, that is the one; when it has several, choose one. Then Propose. Only your own open tasks in a mapped project can be marked done, one at a time.

Nothing is changed in Productive until you answer Yes on the desk. The Yes card says Mark a Productive task done with the task's title, then the project, Status becomes with the status name, and the task's number. It reads them live; if Productive does not answer, the card says Productive did not answer. and offers no Yes.

At Yes, zonask reads the task again. If it is no longer one of your open tasks, because someone closed or reassigned it or its project is no longer mapped, zonask cancels the proposal, says This task is no longer open in Productive. and writes nothing. If Productive does not answer, the proposal stays open. Otherwise zonask sets the task's status, and nothing else, and says Task marked done in Productive. The task then leaves From Productive.

Result not confirmed. Check Productive. means zonask sent the change and got no readable answer, so it cannot say whether Productive saved it. Look at the task in Productive; zonask does not send the change again by itself.

There is no undo in zonask. To reopen a task, or to change its title, date, assignee or anything else, use Productive. zonask closes one task at a time and no subtasks or to-dos.

Log time from an activityCopy Anchor Link

On Time, an approved activity whose role has a mapped Productive project shows Log in Productive. Choose the project, the service (shown as budget and service), optionally one of your open tasks in that project, the minutes and a note, then Propose. The minutes start at the activity's minutes and the note at a meeting's title; a mail session starts with an empty note. The date is the activity's day and the person is always you.

Nothing is written to Productive until you answer Yes on the desk. The Yes card says what will be written: the minutes and the day, the project, the service with its budget, the task or none, the note or none, and person you. It reads the names live; if Productive does not answer, the card says Productive did not answer. and offers no Yes.

At Yes, zonask checks again that the activity is still approved, that the project is still mapped to its role and that the service is still offered. If something is no longer valid it cancels the proposal; if Productive does not answer, the proposal stays open. One activity becomes one time entry: zonask logs it at most once, never several activities together, and never billable time, overtime or a timer.

Afterwards the activity says Logged in Productive. While a proposal waits it says Waiting for your Yes, with a link to the desk.

Result not confirmed. Check Productive. means zonask sent the entry and got no readable answer, so it cannot say whether Productive saved it. Look at your time entries in Productive for that day. zonask does not offer that activity again, so nothing is logged twice; if the entry is missing, add it in Productive.

To correct or delete a logged entry, use Productive. zonask does not change or delete time entries.

See everything zonask createdCopy Anchor Link

Productive in Setup ends with Created by zonask: one line per proposal, created tasks, time entries and tasks marked done together, newest first, up to 50. Each line shows the date and time, where you confirmed it, the project and, when confirmed, the Productive task id or time entry id; a task you marked done reads Task … marked done. A retry of the same proposal stays one line. The list remains after disconnect and holds ids, not titles or notes. If a call to Productive has no confirmed result, the entry says Result not confirmed. Check Productive. Check Productive before taking another action; zonask will not retry an uncertain write. A failure before the write returns the proposal to the desk without a new list entry.

zonask writes to Productive in three ways only, each after your Yes on one proposal: it creates a task, logs a time entry, or marks one of your open tasks done. It never edits any other field of a task, and it never comments, deletes or assigns, or writes for someone else. No agent, schedule, standing order or sync writes to Productive.

In Claude or ChatGPTCopy Anchor Link

list_productive_tasks reads assigned tasks; map_productive_project and create_productive_task ask for confirmation before they write. A created task needs a live task list from its project. Connecting still happens in the browser. Without a role or project, list_productive_tasks lists your projects, their roles and the same Created by zonask list.

log_productive_time proposes one time entry for one approved activity from list_activities, and logs it once after your confirmation. With a project, list_productive_tasks also lists the services you can log time on. After Result not confirmed. Check Productive. it does not offer the activity again.

close_productive_task proposes marking one of your open tasks done, and sets its status once after your confirmation. With a project, list_productive_tasks also lists the closed statuses to choose from when the project has several. A task that is no longer open is not touched.

zonask runs a safety check before a chat may confirm a change, and a change in Productive is something other people see. When the check does not let the chat confirm it, the tool says so and your proposal stays on the desk: open Approvals in zonask and press Yes there.

Example request after mapping a project to a role.

What do I have in Productive for Acme Studio?

Example request after approving yesterday's time.

Log yesterday's workshop in Productive on the Acme Studio retainer.

Example request for one of your open tasks.

Mark my Acme Studio kickoff task done in Productive.

FOLLOW-UP: The general retention purge does not remove answered Productive proposal rows; a future retention work order should decide and implement their lifetime.