Project and task upkeep
Create and update projects and tasks, adjust statuses and assignments, and keep the plan matching reality, changes shown first.
Workamajig runs the agency: projects, tasks, timesheets, billing, purchasing, the whole machine. It also holds every answer leadership asks on Mondays: what is over budget, who is underwater, which clients are profitable. Getting those answers out has always been its own job.
The Workamajig connector makes the machine conversational. It links the AI you already use, like Claude, ChatGPT, or Copilot, to your Workamajig system through Mad Fish Elements, with read and write reach across projects, campaigns, tasks, timesheets, contacts, billing, purchasing, and financial reports. The operational truth the agency already maintains becomes something anyone permitted can simply ask.
Connect your system, and your AI reads the agency the way Workamajig models it: projects with their tasks, budgets, and status; the campaigns they group into; timesheets and where hours land; contacts; billing and purchasing records; and the financial reports the system already computes, fetched and run by report key.
The Monday questions become sentences. "Which projects are over 80% of budget with open tasks?" "Hours by person last week against target." "Unbilled time by client." "Which projects slipped their dates this month?" The answers arrive as visual reports, from the system of record, without anyone assembling them.
Context compounds: the same Gateway reads Toggl, Bill.com, and the marketing platforms, so hours, costs, billing, and the campaign work itself can appear in one answer when the question spans them.
With Write access and your approval, your AI maintains the machine as well as reading it:
Create and update projects and tasks, adjust statuses and assignments, and keep the plan matching reality, changes shown first.
Surface missing timesheets, misallocated hours, and unsubmitted expenses; fix the batches you approve.
Read and maintain the records that feed invoicing, so month-end starts from clean data instead of a chase.
The reports your finance flow already trusts, run on schedule and delivered as briefs. One permission note handled honestly: report access requires the API user's "run reports" right in Workamajig, and the connector tells you plainly when that is the blocker rather than failing mysteriously.
In practiceThe session that changes the ops meeting: Sunday night, the scheduled brief arrives. Projects over budget threshold: three, listed with percentages. Missing timesheets from last week: four people; unbilled time by client: totaled. Monday's meeting starts at the decisions instead of the data gathering. Mid-meeting someone asks, "What is the margin looking like on the Henderson project?" You ask; the connector runs the report; the answer lands before the topic changes. The meeting got shorter and the operations got sharper on the same day.
The ops brief assembled from the system of record, on schedule.
Over-threshold projects flagged while course-correcting still works.
The missing-hours list generated and handled in a pass.
The reports finance trusts, delivered where the team already reads.
"Which projects are over 80% of budget with open tasks?"Workamajig
The early-warning list, from the system of record.
"Show hours by person last week, and who is missing timesheets."Workamajig
The utilization and discipline answer in one pass.
"Run the monthly client profitability report and chart it."Workamajig
The finance report as a visual brief, by report key.
"Unbilled time by client, totaled, for month-end."Workamajig
The billing prep that used to start the scramble.
"Create a task on the Henderson project: revise the media plan, due Friday, assigned to Sam."Workamajig
The plan updated from the meeting, on approval.
Internal creative teams on Workamajig get the same relief: capacity, budgets, and intake status answerable by the people who need them, without a trip through the ops manager's queue.
For marketing teamsThis is the agency operating system, and now it talks. Ops leads get standing briefs, account leads get project truth mid-call, and finance gets clean inputs at month-end, all from one connection under per-person permissions.
For agenciesAsk in chat and share the dashboard without building exports or taking screenshots.
Over-budget projects, missing time, slipped dates. Built for Monday, delivered Sunday.
The finance report, charted and trended. Built for the quarterly business review.
Hours by person against target. Built for resourcing decisions.
The charts do the talking: bar for project and client comparison, gauge for budget consumption, table-first for the finance detail. And when leadership wants these anytime, the Data Visualization add-on turns your reports into always-current dashboards they open from a link. Ask in chat; share the dashboard.
Agency operations compress into a short list. Budget consumed by project, against completion: the early-warning pair. Hours by person against target: capacity, honestly. Missing timesheets: the hygiene figure everything else stands on. Unbilled time by client: the cash sitting in the system, waiting on month-end. And client profitability, from the finance reports, the number the whole machine exists to produce. The rhythm: budgets and time weekly, billing prep mid-month, profitability monthly. Every one of these is a question here, and the Sunday brief carries the first three automatically. The Monday meeting stops gathering and starts deciding, which was always the meeting's actual job.
Day one: connect the system and pull the picture. "Projects over 80% of budget with open tasks." Day two: check the discipline. "Missing timesheets last week." Send the list where it needs to go. Day three: run one finance report by key. "Client profitability, last month, charted." Verify a number with finance to build the trust. Day four: prep month-end early; "Unbilled time by client." Two weeks early, for once; day five: schedule the brief. "Sunday nights, send the ops brief: budgets, time, slips." By Friday, Monday's meeting has changed shape: it starts at decisions, because the gathering happened while everyone slept. The agency's operating system was already keeping score; now it reports the score without being asked.
Pair Workamajig with Toggl Track where time lives outside the system, and with Bill.com for the ops-to-cash line. Add the marketing connectors when the question spans the work itself. Agency operations, hours, and money: one Gateway, one conversation.
The deeper point of the pairing: agency profit hides in the seams between systems. Hours in one tool, projects in another, cash in a third. Margin leaks in the gaps; put all three on one Gateway and the gaps close. The question that spans systems stops being a quarter-end project and starts being a Tuesday sentence.
It will not replace your finance controls. Billing runs the way your finance team runs it; the connector cleans inputs and reads outputs, and money-moving stays where your controls put it. It will not approve time or expenses for anyone; it surfaces and routes, humans approve. It will not invent margins; every financial number comes from the system's own reports. And it will not exceed the API user's rights inside Workamajig itself.
Access is set per person, not per account, so Read seats see everything and change nothing while Write seats create and edit with your approval flow in front of every change. Delete access goes only to people you trust to clean up, and many teams start read-only, check answers against the platform, then widen access as the audit trail earns it.
You choose the level of human review and can change it at any time, while every action records what changed, when, and who approved it. Per-user access means Elements never stores your Workamajig password, and your data is never harvested or resold.
Plans, account limits, and the multi-client Agency plan are on the pricing page .
The rights matching what you want available, including the "run reports" security right for financial reporting. When a permission is the blocker, the connector says so specifically instead of failing vaguely.
It can create and correct entries under Write permissions and approval, which teams mostly use for fixes and migrations. The daily habit of logging time stays with the humans doing the work.
They share the Gateway. Teams tracking time in Toggl, running ops in Workamajig, and paying through Bill.com can ask questions that span all three in one conversation.
No. Your AI acts only with the permissions you set, and changes follow the review level you choose. Read-only seats cannot change anything, because the approval flow is the product working as designed.
Your team can use Claude, ChatGPT, and Microsoft Copilot, while other AI tools can likely connect when they support MCP, the open standard for linking AI assistants to outside tools.
No. Your data stays yours, so nothing is harvested and nothing is resold.
The teams winning with AI are not handing their accounts to a black box; they keep the strategy and delegate the hands-on-keyboard work, while approvals and an audit trail make it safe to move fast. Connect the account you already have through the Gateway and ask the question you would normally build a report to answer.
Your first 14 days are free. Add your card to start, and cancel before the trial ends to pay nothing.