If your agency runs client work out of Jira, the PPC TNT side of that work can log itself. Link a client workspace to a Jira issue and PPC TNT comments on it every time a tool runs for that client — plus a weekly stats summary — so the issue reads as a running account history instead of a stub someone forgot to update.
What gets posted
When a PPC TNT tool runs for a linked client — a sync, an agent session, a keyword pull — the issue gets a comment saying what ran and what it found.
A scheduled roll-up of the week's numbers for that client, posted as a comment, so the issue carries the trend and not just isolated events.
With the Claude connector, you can ask Claude to post a summary to a linked issue in conversation — the only thing the connector is allowed to write.
Comments queue and retry rather than vanishing, so a Jira outage or an expired token doesn't silently drop a week of history.
Setup
Jira is configured per client rather than once for the whole agency, because the point is that each client's activity lands on that client's own issue.
Add your Jira Cloud site and API credentials in PPC TNT under Agency → Integrations.
On the Agency page, open the client row and choose Jira. Point it at the Task issue you use for that client's work.
From then on, tool runs for that client post comments to the issue, and the weekly summary joins them. Nothing else in Jira is touched — PPC TNT only comments.
Common workflows
The issue already has a dated record of what ran and what changed, so the monthly update is a link rather than a document.
An issue with no comments for a fortnight is a client nobody has touched. The connector's activity log answers the same question across the whole portfolio at once.
Ask Claude for the account's numbers and then to post that summary to the client's issue. It asks you to confirm first, and it can only post to issues already linked to that client.
Link a client to its issue once and the account history writes itself. Setup walkthrough lives in the docs.