TickTick AI Connector: Governed Task Access

Project Management

TickTick

Connect your AI to TickTick

Individual professionals, team leads, and productivity coaches run their to-do lists, projects, habits, and focus time through TickTick, but the answers they need about what is overdue, what slipped, and where the time went sit across separate lists and views. AI can pull those answers together in seconds, but only if it stays within the connected TickTick account's own data, including shared projects, and never exposes private task content or comments to people without access to that project.

‍

Why it matters

Capabilities that matter most for TickTick

Read tasks, projects and habits

Expose open and completed tasks, projects, habits, habit check-ins, and focus sessions as read tools, returning only the fields an AI needs instead of raw API payloads.

Plan and review from real data

Ready-made prompts cover the daily plan, weekly review, overdue task audit, project status, and focus time report, so answers come from your lists rather than from memory.

Pair TickTick with other systems

Prompts that span TickTick and 28 other connected systems, such as Zendesk, HubSpot, Jira, and NetSuite, check whether work in those tools has a matching TickTick task.

Governed by the connected account

Access is limited to the connected TickTick account's own data, including shared projects, so AI does not reach task content or comments outside that account.

Write tools stay off until you switch them on

The 22 tools that create, update, complete, move, assign, and delete tasks and projects are inactive by default and have not yet been run against a live TickTick account.

Use cases

Example AI Use Cases for TickTick

scenario

Negative survey answers pile up in Simplesat, and nobody checks whether a follow-up task was ever created for each one. You would have to read every unhappy response, then search the task list by customer name or response ID. Unhappy customers end up unanswered because the gap is invisible.

What popdock provides

Name a lookback window, and optionally a survey, and it lists the recent negative Simplesat answers with the customer, survey and any ticket ID. For each response it searches TickTick for a task that carries the response ID, or the customer name created on or after the feedback date. You get two tables, covered and uncovered, with counts. Name-only matches are marked as weak. Nothing is changed in Simplesat or TickTick, and writes are ruled out on both.

Business outcome

---

You see exactly which unhappy customers have no follow-up task, so none go unanswered, without opening either system.

scenario

Before a customer call, you open BigCommerce to read their details and orders, then search your task list for anything that mentions them. Putting the two pictures together by hand takes a while, and a refunded order or an open task is easy to miss.

What popdock provides

Give a customer email and it finds that customer in BigCommerce, stopping if nothing matches or if several do. It reads their orders over a lookback window, then searches TickTick for tasks by last name and by order number and reads the comments on each. A task is included only when it also mentions the email, full name or an order, and it says which one matched. You get a one-page brief with details, orders, totals, tasks and up to three observations. Nothing is written to either system.

Business outcome

---

You walk into the call with orders, refunds and open tasks in one brief, and no ambiguous customer match slips through.

scenario

To see which BigCommerce orders have a follow-up task, someone lists the orders by status and then searches the task app for each order number. Tasks that point at orders in a different status or an older window are just as easy to overlook.

What popdock provides

Give an order status and a lookback window, and it reads the matching BigCommerce orders. It then finds TickTick tasks titled with an order number and matches each order to a task by that number. You get counts for three groups, orders with a task, orders with no task and orphan tasks, plus tables of orders without a task, oldest first, and of orphan tasks. It only reports, and every write on both systems is ruled out.

Business outcome

---

You see which orders have no follow-up task and which tasks point at stale orders, without comparing two systems by hand.

scenario

A person's bug load lives in BugHerd while their own tasks live in TickTick, so the two are checked separately. A day that looks fine in one tool can be overloaded once both are added together, and nobody sees it until work slips.

What popdock provides

Name an assignee and a number of days, and it reads their open BugHerd bugs with project, severity and due date, and their open TickTick tasks due in the same window. It lays out each day with TickTick tasks beside BugHerd bugs, then totals them and flags days with more than 5 items combined and open bugs with no due date. If the two systems spell the person differently it looks up the BugHerd user and says which form matched. If one side is empty it reports the other alone. Nothing is changed.

Business outcome

---

You spot overloaded days and undated bugs before work slips, using one view across BugHerd and TickTick.

scenario

After a release ships, nobody checks whether the errors it introduced have any planned work. You would look up the release in Bugsnag, scan the open errors, then search TickTick for each one. Untracked errors stay unnoticed until a customer reports them.

What popdock provides

Give a Bugsnag project and an app version, and it finds that release, stopping if more than one matches or none is found. It reads the open errors seen since the release date, keeping the ones with the most events, then searches TickTick for tasks naming the version and for each error ID. You get a release summary and a table of errors with the linked task and due date, ending with the count of untracked errors. It only reads, and no write is made on either server.

Business outcome

---

You see which errors from a release have no planned work, so none are left untracked.

scenario

Before a call with a customer, you check their balance and open invoices in Business Central, read the internal notes and look at open opportunities. Then you search your task list for anything that mentions them. Stitching that together by hand takes time and misses things.

What popdock provides

Give a customer number and company, and it finds the customer in Dynamics 365 Business Central, stopping if nothing matches. It reads open invoices, internal notes and open opportunities, then searches TickTick for open tasks by name and number and for tasks completed recently. You get one briefing with account, notes, pipeline, open tasks and recent completions, up to three suggested next actions, and empty sections shown as none found. It says task matching is by text and may be incomplete. Nothing is written to either system.

Business outcome

---

You start the call knowing the balance, notes, pipeline and open tasks for the customer, from one read-only briefing.

scenario

Finding out how much effort went into a customer means searching Capsule CRM for the history, then searching TickTick for tasks, completed tasks and focus sessions that mention them. The pieces live in two tools, so the real effort rarely gets added up.

What popdock provides

Name a customer and a lookback window, and it finds the party in Capsule CRM, stopping and listing the options if several match. It summarizes recent CRM activity by type and lists the latest ten entries, then finds matching TickTick tasks, completed tasks and focus sessions tied to those tasks. You get open and completed task counts and total focus minutes, with a flag when focus time is high but the last contact is older than the window. It says TickTick matching is by name only. Nothing is changed.

Business outcome

---

You see how much effort a customer is getting against how recently you spoke to them, from both tools at once.

scenario

Release dates in GitHub drift away from the deadlines in personal task lists, and nobody notices until the date passes. Checking means opening the milestone, listing its open issues and searching the task app for each one by hand.

What popdock provides

Give a milestone title, and it reads that GitHub milestone with its due date and open and closed counts, stopping if it matches none or several. It lists the open issues, then looks in TickTick for a task that carries the issue number or title. You get a table of issues with the matching task and due date, flagged when the task is due after the milestone or has no due date, with untracked issues last. Weak text matches are marked as possible. It only reads, and every write on both servers is ruled out.

Business outcome

---

You find tasks that are late against a milestone and issues with no task before the release date passes.

scenario

Collection tasks get ticked off in the task app before the payment actually lands in NetSuite, and nobody rechecks. Finding the mistakes means taking each completed task, reading the invoice number from its title and looking up the open balance by hand.

What popdock provides

Name a lookback window and a keyword, and it reads completed TickTick tasks that match and pulls the document number from each title. It then checks NetSuite for each number and keeps those that still show a balance after payments applied. For every hit you see the task, completion time, document number, customer, open balance and due date, and it says which tasks look closed in error and which are fine. Titles with no document number are listed as unchecked. Nothing is written to either system.

Business outcome

---

You catch collection tasks marked done while the NetSuite receivable is still open, before the money goes uncollected.

scenario

Someone compares the sent email campaigns in Constant Contact against a to-do list by hand to see which have a follow-up. With a month of sends that is a lot of name searching, and campaigns slip through while tasks for old campaigns stay open.

What popdock provides

Name a lookback window and optionally a TickTick project, and it lists the Constant Contact campaigns sent in that time with sends, opens and clicks. It searches TickTick for a task naming each campaign and for open tasks that mention campaign. You get campaigns with an open task, campaigns with only completed tasks, and campaigns with no task, then tasks that match no campaign. It says matching is by campaign name only, and marks duplicate names as ambiguous. It only reports, and writes are ruled out on both servers.

Business outcome

---

You see which campaigns have no follow-up task and which tasks point at no campaign, with no manual cross-check.

scenario

Service contracts expire unnoticed because renewal reminders are not tracked against the contract list. Someone has to list the contracts ending soon in Dynamics SL and then search the task app for a renewal reminder on each one.

What popdock provides

Name a window in days, and optionally a company, and it lists active Dynamics SL service contracts expiring in that period. For each contract it searches open TickTick tasks by contract ID, then by customer name, and counts a task as a renewal when its title mentions renew or the contract ID. You get a table sorted by expiration date with the amount and the renewal task and due date, or None, ending with the count of contracts with no renewal task. If nothing expires it says so and stops. No TickTick write is made.

Business outcome

---

You see which expiring contracts have no renewal task, in time to act before they lapse.

scenario

After a meeting, someone rereads the notes and scans the task list by hand to see whether each action item was ever captured. The task app is rarely checked item by item, so commitments slip through and are only noticed when someone chases them.

What popdock provides

Name a Granola meeting and optionally a TickTick project, and it finds the note, stopping if several or none match. It pulls the action items from the summary, and from the transcript when the summary has none, with an owner and due date where one was said. It then looks for open TickTick tasks that clearly cover each item. You get a covered table and a missing table with suggested owner and due date, and counts. Doubtful matches are listed as missing with the near match noted. Nothing is written.

Business outcome

---

You know which meeting commitments have a task and which are still missing, so none depend on memory.

scenario

Upcoming HubSpot meetings get checked against the task app by hand, so some meetings arrive with no prep task. It means listing the next week of meetings, finding each company, and searching for a task that mentions either one.

What popdock provides

Give a number of days, and optionally an owner, and it reads the HubSpot meetings starting in that window and looks up each company name. It searches open TickTick tasks by meeting name, then by company name, and prefers tasks due on or before the start. You get a table in start order with the prep task and due date or NONE, with meetings that have no prep task listed at the top. A meeting with no company is matched by meeting name only, and it says so. No tasks are created or changed on either system.

Business outcome

---

You see which upcoming meetings have no prep task, with enough time to prepare for them.

scenario

Leads due to close soon slip because nobody checked whether a follow-up task exists. Finding the gaps means listing a rep's open leads in Nutshell, finding each company, and searching the task app for a task that mentions the lead.

What popdock provides

Give an owner name and a number of days, and it finds the owner in Nutshell, reads their open leads anticipated to close in that window and gets the company name for each. It searches open TickTick tasks by lead or company name, then by lead number. You get a table by close date with value, confidence and the follow-up tasks found or NONE, ending with a count of leads with none. It says a NONE result only means no task mentions the name. It only reports, and writes are ruled out.

Business outcome

---

You see which leads about to close have no follow-up task, so none are left unattended.

scenario

Overdue HubSpot tasks get compared with the task app by hand, so work that is untracked or already finished elsewhere goes unnoticed. Each overdue task has to be searched by title in two places before you know where it stands.

What popdock provides

Name a person, and it reads their overdue HubSpot tasks with due date, priority and contact. For each one it searches open TickTick tasks by title and, if none is found, checks tasks completed in a lookback window. You get three groups: tracked and open, completed in TickTick but still overdue in HubSpot, and not in TickTick at all, each with title, due date and priority. Partial title matches are flagged as uncertain. Nothing is created, updated or completed on either system.

Business outcome

---

You see which overdue HubSpot tasks are untracked or already done elsewhere, so nothing falls through between the two.

scenario

Change windows in ServiceNow are planned without looking at personal deadlines and countdowns in the task app, so clashes show up late. Checking means listing each change window and comparing every task and countdown date by hand.

What popdock provides

Give an assignee and a date range, and it reads their planned ServiceNow changes, skipping closed and canceled ones. It reads TickTick tasks that are not completed and countdowns over the same range. For each change it lists tasks due inside the window or within 24 hours before it and countdowns dated inside it, and lists changes with no clash. You get a table per change with risk, due date and priority, highest risk first. It states the time zone assumed and marks clashes near a boundary as uncertain. Nothing is changed.

Business outcome

---

You spot clashes between change windows and your deadlines before the change goes ahead, not after.

scenario

Due dates and status are kept in two places by hand, so they drift apart. The task list ends up showing work that Jira says is done or has moved, and comparing them means opening each Jira issue from the key in the task title.

What popdock provides

Name a number of days, and it reads open TickTick tasks due in that window whose title contains a Jira key. It reads each issue in Jira for its due date and status, then compares them. You get only the rows that disagree, with a verdict such as due dates differ, Jira Done but task open, or Jira issue not found, then the count of matches. Tasks with no Jira key are skipped, and it says how many. A missing Jira due date is reported, not treated as a mismatch. Nothing is changed on either side.

Business outcome

---

You see where TickTick and Jira disagree on dates or status, so stale tasks and missed changes surface early.

scenario

A rep checking whether a Capsule CRM deal has follow-up work has to open the opportunity, then search TickTick by deal name and again by customer, and compare due dates by eye. Deals with no next step go unnoticed until the customer goes quiet.

What popdock provides

Name a Capsule CRM opportunity and it finds the deal, listing the candidates for you to pick from if more than one matches. It then searches TickTick tasks by the opportunity name, the party name and, if those find nothing, the party as a tag. You get the deal details, the matching tasks and a verdict of Covered, Overdue or Uncovered. It says the match is by name only, treats an empty TickTick search as Uncovered, and changes nothing in either tool.

Business outcome

---

Deals with no scheduled next step show up in a single check, and nothing is edited in Capsule CRM or TickTick.

scenario

Buyers can see which purchase orders are late in Dynamics GP, but nothing shows whether anyone is chasing them in TickTick. Checking each PO number and vendor against the task list by hand is slow, so the orders nobody owns slip further.

What popdock provides

Optionally give a vendor ID, and it finds open Dynamics GP purchase orders with a balance remaining and a promised or required date in the past. For each one it searches open TickTick tasks by PO number, then by vendor name. A task only counts when it names the PO, vendor-only matches are marked possible, and a completed task does not count as coverage. Both systems are read only.

Business outcome

---

Late purchase orders with nobody chasing them are listed with days late and value, so buyers can pick them up before they slip further.

scenario

Preparing for an account meeting means opening Chorus for recent calls and emails, then separately opening the task list to see what is still outstanding. Overdue commitments are easy to miss when the two views never meet.

What popdock provides

Name an account and a lookback period, and it reads the recent Chorus conversations, the participants of the latest call and the emails sent. It then searches TickTick for open tasks that mention the account. The brief lists conversations, email activity and open tasks by due date with overdue ones flagged, plus talking points drawn only from that data. It states that matching is by account name, reports an empty side as empty, and changes nothing.

Business outcome

---

You walk into the meeting knowing what was said recently and which commitments are still open or overdue.

scenario

Call load lives in Chorus and deep-work time lives in TickTick, so a rep buried in calls can look fine in both tools on their own. Nobody sees the weeks where meetings crowded out focused work.

What popdock provides

Give a Chorus user email and a date range, and it totals recorded conversation count and hours per week from Chorus. It then totals TickTick focus hours and completed tasks for the same weeks. You get a weekly table and two or three plain observations, such as heavy call weeks with little focus time. It states that the TickTick account may not belong to the same person, reports an empty side as empty rather than zero, and changes nothing.

Business outcome

---

Managers see which weeks calls crowded out focus time, without exporting from two systems.

scenario

The same to-dos end up in both Dynamics 365 Sales and TickTick, and the two lists drift apart. Without a side by side view, a task can be missing from one system or carry a different due date or priority in the other.

What popdock provides

Give an optional owner and a number of days ahead, and it reads open Dynamics 365 Sales tasks due in that window and open TickTick tasks due by the same date. It matches them by equal subject and title, or by one containing the other with due dates within a day. You get three lists: in both, only in Dynamics 365 Sales, and only in TickTick, with counts. Priority differences are shown as text, and nothing is changed in either system.

Business outcome

---

Gaps between your CRM tasks and your personal task list become visible in one report, with nothing edited.

scenario

Project managers compare booked timesheet hours in Dynamics GP with what the team actually worked on in TickTick, and the two rarely line up cleanly. Pulling the numbers from both and matching them to the project takes time and invites guesswork.

What popdock provides

Give a Dynamics GP project number and a lookback period, and it reads the project status and costs and sums booked timesheet hours and cost per employee. It then totals TickTick focus time for the project number and project name and lists open and recently completed TickTick tasks that mention it. You get the difference and a one-line read. It explains that focus time covers only timed work, shows uncertain matches separately, and is read only on both systems.

Business outcome

---

Project managers see booked hours beside tracked focus time in one view, with gaps explained as indicative rather than errors.

scenario

Nobody can say how much of the week went to meetings versus focused work, because meetings are recorded in Granola and focus time is logged in TickTick. Adding it up by hand means opening both and doing the sums day by day.

What popdock provides

Give a lookback period and, optionally, a meeting title keyword, and it totals meeting hours and counts per day from Granola notes using their scheduled start and end. It then totals TickTick focus hours and sessions per day. You get a daily table, the focus to meeting ratio, the three heaviest meeting days and the days with no focus logged. Meetings with no end time are listed as unknown, not zero, and nothing is changed.

Business outcome

---

You see the real balance of meetings and focus time for the week, including days with no focus at all.

scenario

A project plan in Intacct and the team task list in TickTick drift apart, and the difference is only noticed when a deadline is missed. Comparing task names, statuses and dates across the two by eye is slow and unreliable.

What popdock provides

Give an Intacct project ID and, optionally, a TickTick project name, and it reads the Intacct project and its tasks, then finds the matching TickTick project. If more than one TickTick project matches, it lists them and stops. You get four lists: in Intacct only, in TickTick only, matched with a different state, and matched with different dates, plus percent complete against the share of TickTick tasks completed. Near matches are labelled possible, and both systems are read only.

Business outcome

---

Plan and task list differences appear before a deadline slips, with no records changed in Intacct or TickTick.

scenario

Booked timesheet hours in Intacct and the time someone actually spent focusing are never compared, so gaps in either go unseen. Lining the two up day by day takes exports from both systems.

What popdock provides

Give an employee ID and a date range, and it totals booked and billable hours per day and per project from Intacct timesheet entries. It then totals TickTick focus hours for the same days and, where useful, names the work from the linked tasks. You get a day by day table with the difference, flags for days with booked hours but no focus and days with focus but nothing booked, and range totals. It says focus time is only a rough signal and changes nothing in either system.

Business outcome

---

Days where booked hours and focus time disagree stand out, so timesheet questions can be asked early.

scenario

Project managers keep a plan in NetSuite and a separate task list in TickTick, then compare them by eye. Status and date drift goes unnoticed until someone asks why a task marked done in one place is still open in the other.

What popdock provides

Give a NetSuite project name, and it reads the project tasks with their status, end date, percent complete and owner. It then reads the TickTick tasks for the same project, open and completed, and matches them by task title. You get three lists: in NetSuite only, in TickTick only, and matched but disagreeing on status, percent complete or dates. If the project name finds nothing in NetSuite it reports the nearest names, and nothing is changed in either system.

Business outcome

---

Status and date drift between the NetSuite plan and the TickTick list is caught in one report.

scenario

Comparing logged hours with real focused work means exporting from two systems and lining up days by hand. Unlogged or over-logged time is easy to miss in the process.

What popdock provides

Give a Business Central company, a resource number and a date range, and it reads the timesheet rows for that resource, noting that none exist if nothing comes back. It then totals TickTick focus hours per day and notes the tasks that took the most time. You get a day by day table of focus hours, timesheet hours and difference, the days with only one side, and the timesheet status. It asks you to confirm the TickTick account is the same person, treats differences as prompts for review, and writes nothing.

Business outcome

---

Unlogged or over-logged days stand out in one table, without exporting from two systems.

scenario

Nobody can see whether the time spent on a campaign paid off, because focus time sits in TickTick and results sit in Constant Contact. Putting the two together means finding each campaign task and adding up sessions by hand.

What popdock provides

Give a lookback period, and it lists recent Constant Contact campaigns with sends, opens, clicks and opt-outs. It finds the TickTick tasks named after each campaign, open and completed, and adds up their focus time. You get one row per campaign with focus hours and open and click rates, ranked by effort, with campaigns that took effort for weak results and results with no tracked effort noted. Matching is by campaign name only, rates show as not available when nothing was sent, no cause is claimed, and nothing is changed.

Business outcome

---

You see effort and results side by side for each campaign, without claiming one caused the other.

scenario

A day's meetings and to-dos are split between Dynamics 365 Sales and TickTick, so clashes and duplicate items are easy to miss. Building one view means checking the calendar, the CRM task list and the personal task list in turn.

What popdock provides

Give a date, which defaults to today, and optionally an owner, and it reads Dynamics 365 Sales appointments and open tasks along with open TickTick tasks due by the end of that day. You get one agenda with meetings in time order, due or overdue CRM tasks and due or overdue TickTick tasks. Overlapping appointments are flagged, items that look like the same task are listed once as duplicated, and it suggests the top three things to do first. It only reads and changes nothing.

Business outcome

---

You start the day with one agenda that shows clashes and duplicates instead of two lists to reconcile.

scenario

Preparing for a customer call means checking opportunities, cases and contacts in Dynamics 365 Sales, then searching TickTick separately for anything planned or recently done. It is easy to leave a source out.

What popdock provides

Name an account and it finds it in Dynamics 365 Sales, stopping if more than one account matches or none do. It then reads the account's open opportunities, active cases and contacts, and finds open TickTick tasks that mention the account plus recently completed ones. You get an account summary, each section with None found where empty, and a one-line view of what needs attention. TickTick matches are by name only and loose ones are flagged. It only reads and changes nothing.

Business outcome

---

You prepare for a customer call from one view of CRM context and related TickTick work.

scenario

Someone compares the BugHerd bug list with their TickTick task list by eye, and bugs slip through without a task. The bigger the project, the easier it is to assume a bug is planned when it is not.

What popdock provides

Name a BugHerd project and, optionally, a TickTick project, and it finds the BugHerd project, listing the candidates and stopping if more than one matches. It reads the open bugs and looks in open TickTick tasks for a match on the bug number in the form #123, or an equal title, preferring the number. You get a table of unmatched bugs with number, title, severity, assignee and due date, then a count of matched against unmatched. It is read only on both systems and changes nothing.

Business outcome

---

Open bugs with no TickTick task are listed in one pass, so none slip through unplanned.

scenario

Engineers eyeball the Bugsnag error list against their TickTick tasks, and high-volume errors slip through untracked. Matching error IDs to task titles by hand gets harder as the list grows.

What popdock provides

Name a Bugsnag project and, optionally, a minimum event count, and it reads open errors with their class, message, events and severity. For each one it looks in open TickTick tasks for the error ID or link in the title, and retries with the start of the error class. You get a table of errors with no matching task and a short list of those that are tracked. It stops if Bugsnag returns nothing, treats a TickTick search with no results as untracked, and never changes errors or tasks.

Business outcome

---

High-volume Bugsnag errors with no TickTick task are listed, so they can be planned rather than missed.

scenario

Job task lists in the ERP and the team task project in TickTick drift apart, leaving job tasks that nobody is tracking. Comparing task numbers and descriptions across the two by hand is slow.

What popdock provides

Give a Business Central company, a job number and, optionally, a TickTick project name, and it reads the job and its tasks. It then finds the TickTick project, listing the candidates and stopping if more than one matches, and reads its tasks. You get a table of job tasks with the matching TickTick task and status, gaps listed first, and any TickTick tasks that match no job task. Matches on description alone are marked possible, and nothing is changed in either system.

Business outcome

---

Job tasks with nobody tracking them are listed first, so gaps can be closed before work is missed.

scenario

Open opportunities sit in Dynamics 365 Business Central while follow-up reminders live in TickTick, and nothing links the two. A rep has to read the pipeline, then search the task list deal by deal, and the quiet deals are the ones nobody notices going cold.

What popdock provides

Give a company, and optionally a salesperson code, and it reads the open Business Central opportunities, then searches TickTick for an open task that mentions each opportunity number. If the number finds nothing it tries the company name, and marks that as a weaker, possible match. You get a table of value, closing date and nearest task due date, the deals with no task largest first, and the ones past their closing date. Nothing is changed in either system.

Business outcome

---

You see which open deals have no follow-up task, biggest first, without touching Business Central or TickTick.

scenario

After a sales call recorded in Chorus, the follow-up is meant to become a task in TickTick. Managers compare the call list against the task list by hand, the two systems share no id, and calls slip through with no follow-up at all.

What popdock provides

Name an account and a lookback, 14 days by default, and it lists the Chorus calls for that account. It then searches open and completed TickTick tasks by account name and subject text, counting a task only if it was created on or after the call date. Ambiguous matches are shown as possible. You get one row per call and a count of calls without a task. It only reads, and nothing is created or changed in Chorus or TickTick.

Business outcome

---

You can see which recent calls for an account still have no follow-up task, without comparing two lists by hand.

scenario

Staff finish donor work in TickTick, such as a thank-you call or a note sent, and forget to log it in DonorPerfect. The donor record then understates the relationship, and nobody can tell which finished tasks were never recorded.

What popdock provides

Give a number of days, 14 by default, and optionally a TickTick project. It reads the tasks completed in that window and takes the donor name from each title, then looks the donor up in DonorPerfect. A task counts as logged if a contact exists within 2 days of its completion. Several matching donors are kept in an ambiguous list, and titles with no donor are set aside. It only reads, and nothing is written to either system.

Business outcome

---

You get a list of finished donor work that never reached DonorPerfect, with doubtful matches kept apart rather than guessed.

scenario

Donor follow-ups are recorded in DonorPerfect, but the people doing the work run their day from TickTick. Someone compares the two lists by eye, and a follow-up with no task is easy to overlook until the date has passed.

What popdock provides

Give a number of days, 14 by default, and optionally an owner. It reads the DonorPerfect follow-ups due in that window, skips completed ones, and looks up each donor by name. It then searches open TickTick tasks by donor name and donor id, counting a task as covering the follow-up when its due date is within 3 days. A name match with a different date is shown as a possible match. It only reads, and nothing is created or changed.

Business outcome

---

You see which upcoming donor follow-ups have no task behind them, so none is dropped.

scenario

Reps scan their Dynamics 365 Sales opportunities in one screen and their TickTick list in another to see which closing deals have a follow-up. The check is manual, TickTick has no customer field, and some deals are missed.

What popdock provides

Name an owner and a window, 30 days by default, and it lists the open Dynamics 365 Sales opportunities closing in that time. For each one it searches open TickTick tasks by customer name, then by opportunity topic, and counts a task only when its title names one of them. You get covered and uncovered tables with counts. Because matching is by name text, it says so and flags ambiguous matches. It only reads, and no task or record is created or changed.

Business outcome

---

You see which closing opportunities have no follow-up task, so no deal near its close date goes unchased.

scenario

A person's open Jira issues are meant to appear on their personal TickTick list, but nothing keeps them in step. Issues quietly never reach the task list, and nobody notices until one slips past its due date.

What popdock provides

Name an assignee, and optionally a Jira project, and it lists their open issues in To Do and In Progress. It then reads the open TickTick tasks once and looks for a task whose title contains each issue key. You get a table of issues with no task, sorted by due date with undated ones last, plus a count of issues that do have one. If the name matches more than one person it asks which is meant. Nothing is written to either system.

Business outcome

---

You can see which open issues never reached the task list and fix them before they slip.

scenario

Reps keep customer follow-ups as tasks in Nutshell and their personal to-dos in TickTick, then compare the two by eye. Titles rarely match word for word, so commitments made in the CRM get missed in the daily list.

What popdock provides

Name a Nutshell user and a window, 7 days by default. It finds the user, stopping to ask if several people match, and lists their open Nutshell tasks due in that time. For each one it searches open TickTick tasks by the key words of the title, counting a match when the title clearly refers to the same job and the date is within 2 days. Fuzzy matches come with the reasoning. Nothing is created or changed in either system.

Business outcome

---

You see which Nutshell commitments are missing from TickTick, with the reasoning behind each match.

scenario

OnePageCRM keeps a next action for every contact, while many reps work from a TickTick to-do list. They compare the two by eye, the systems share no id, and follow-ups quietly fall through.

What popdock provides

Give a window, 7 days by default, and optionally an owner. It reads the open OnePageCRM actions due in that time, then names each contact and company. For each action it searches open TickTick tasks by the contact's last name, and calls it a match when the title also shares the action text or full name and the date is within 2 days. Partial matches are labelled possible with the reason. It only reads, and nothing is changed in either system.

Business outcome

---

You can see which due actions have no task in TickTick, with partial matches labelled possible rather than confirmed.

scenario

Open GitHub issues are tracked by eye against a TickTick task list. The two share no id, so issues that never became a task are easy to miss, and they slip until someone asks about them.

What popdock provides

Optionally give a label, and name a TickTick project. It lists the open GitHub issues, then reads that project's open tasks and looks for one whose title contains the issue number or the issue title. Matches by title alone are marked possible. You get a table with the matching task or no task and a count of untracked issues. If the project name matches nothing it lists candidates and stops. It only reads, and no issue or task is created or edited.

Business outcome

---

You see which open issues nobody is tracking as a task, and can act on them before they slip.

scenario

When a bug is closed or archived in BugHerd, the TickTick task that tracked it often stays open. The stale tasks clutter the plan, and finding them means checking bug numbers against the task list one at a time.

What popdock provides

Name a BugHerd project. It resolves the project, stopping if several match, then reads the archived and closed bugs. It reads the open TickTick tasks and matches them to bugs by the number written as #123 in the title or content, or by an identical title, preferring the number. You get a table of the stale tasks. A bug that matches several tasks is listed with all of them and flagged. Nothing is changed in BugHerd or TickTick.

Business outcome

---

You get a list of open tasks whose bug is already finished, ready for you to tidy up, with nothing changed on your behalf.

scenario

Collections staff read the NetSuite aging report, then check their TickTick task list by hand to see who is chasing what. Overdue invoices slip through with no one assigned, and the balance stays unpaid longer than it should.

What popdock provides

Give an as-of date, today by default, and optionally a customer. It reads the open receivables past due, keeps only those with a balance remaining, and searches open TickTick tasks by document number, then by customer name. You get a table with days overdue and the matching task or NONE, then the unchased items with their total balance. It stops if nothing is overdue and never picks between several matching tasks. It only reads, and nothing is changed in NetSuite or TickTick.

Business outcome

---

You see which overdue invoices have no one chasing them, with their total balance, so collections can act on them.

scenario

Finance staff keep payment reminders in a task list that is separate from the ledger. When a Rillet bill falls due with no reminder in TickTick, nothing prompts anyone to pay it, and the miss shows up as a late payment.

What popdock provides

Give a window, 14 days by default, and optionally a TickTick project. It reads the Rillet bills due in that time, ignoring paid and void ones, and names each vendor. It then searches open TickTick tasks for the bill's expense number or vendor name. Unmatched bills are listed first, soonest due first, and tasks due after the bill are flagged. It stops if no bills are due and lists candidates when matching is unclear. Nothing is changed.

Business outcome

---

You see which bills falling due have no reminder task, soonest first, so no payment is missed.

scenario

Reps eyeball the Salesforce pipeline against their TickTick list to see which deals closing soon have a follow-up. The check is manual and the systems share no id, so a deal can reach its close date with no task behind it.

What popdock provides

Give a window, 14 days by default, and optionally an owner and a minimum amount. It reads the open Salesforce opportunities closing in that time, then searches TickTick for an open task by opportunity name, retrying with the account name. You get covered and uncovered tables, uncovered by close date. Every match is labelled a name match, not a certain link, and very short names are marked uncertain. It only reads, and nothing is changed.

Business outcome

---

You see which deals closing soon have no follow-up task, with name-only matches kept honest as uncertain.

scenario

Support agents track ticket follow-ups as TickTick tasks, with the ticket number written into the title. When the ticket is solved, the task often stays open, and the list fills with work that is already done.

What popdock provides

Give a lookback, 14 days by default, and optionally a task prefix such as ZD. It lists the Zendesk tickets solved in that window, then reads the open TickTick tasks with that prefix and pulls the ticket number from each title to match them. You get a table of stale tasks with project and due date, plus how many open tasks were scanned and how many had no recognizable ticket number. It never infers status from a title and completes nothing.

Business outcome

---

You get a list of open tasks whose ticket is already solved, ready to close, and nothing is closed on your behalf.

scenario

A fundraiser looks up a donor's history in DonorPerfect, then searches TickTick by hand for the follow-up tasks. TickTick has no donor field, so tasks filed under a nickname or a different spelling are missed.

What popdock provides

Give a donor name or donor id. It finds the donor in DonorPerfect and, if several match, lists them with id, city and email and stops. It then searches open TickTick tasks due within a window, 30 days by default, by last name and by donor id, and drops tasks that clearly name a different person. You get a donor header, the tasks with any overdue ones flagged, and the last 3 contacts and gifts. It only reads, and nothing is changed.

Business outcome

---

You see a donor's open tasks beside their giving history in one answer, with name collisions flagged rather than guessed.

scenario

Agents track ticket follow-ups in TickTick and look them up by hand across two apps. The ticket id lives only as text in a task title, so tasks and ticket status drift apart, and a solved ticket keeps an open task or an urgent one has none.

What popdock provides

Give a Zendesk ticket id. It reads the ticket, stopping if it is not found, then searches open and completed TickTick tasks for that id, counting it only as a whole number and never as part of a longer one. You get the ticket line, a table of matching tasks, and the mismatches: ticket solved but a task open, ticket open or urgent but no task, or a task overdue while the ticket is open. All matches are listed, none chosen. It only reads.

Business outcome

---

You see a ticket and its tasks side by side, with the disagreements called out, without searching two apps.

scenario

An agent's open Zendesk tickets are checked one at a time against a personal TickTick list. With dozens open, the check is slow, and the urgent tickets are the ones most likely to go untracked.

What popdock provides

Name an agent, and optionally a priority. It lists their open Zendesk tickets, taking the 25 most urgent and saying how many were left out. For each ticket it searches TickTick for an open task whose title contains the ticket id as a whole number. You get covered and uncovered lists, urgent uncovered first. A ticket whose TickTick lookup fails is listed as unchecked, not as uncovered. It only reads, and nothing is created or changed.

Business outcome

---

You see which open tickets have no task, urgent ones first, and failed checks are never passed off as gaps.

scenario

Knowing how much focused time goes into each customer means reading timer history in TickTick and matching task titles to account names in Salesforce by hand. Nobody does it often, so effort per account is guessed, and time spent on small accounts or on no account at all goes unseen.

What popdock provides

Give a start date, and optionally an account owner and a minimum number of hours, and it reads your TickTick focus sessions and the Salesforce accounts. It matches each session to an account by looking for the account name in the task title, and a session that fits more than one name goes to the longest name. Names under 4 characters are skipped. You get a table of focus hours, session count and annual revenue per account, plus the unmatched hours. Nothing is changed in either system, and it tells you matching is by name text.

Business outcome

---

You see where focused time really goes by account, with unmatched time shown openly, so effort can be compared with revenue.

scenario

A weekly activity summary means scrolling through GitHub commit logs, then opening TickTick for timer history and finished tasks, then lining the days up yourself. It is slow, and a day with commits but no recorded focus, or the reverse, is easy to miss.

What popdock provides

Name an author and how many days to look back, and it reads that author's GitHub commits and the TickTick focus time and completed tasks over the same days. You get a day by day table of commits, focus hours and tasks completed, then totals and any day that has commits without focus or focus without commits. It reports counts only and does not score productivity. It also notes that TickTick data belongs to the connected TickTick account, and it changes nothing in GitHub or TickTick.

Business outcome

---

A week of GitHub and TickTick activity lines up in one table, with counts only and no guessed scores.

scenario

Preparing a follow-up for an account means opening HubSpot for the company, its deals and its tickets, then searching TickTick for the tasks already planned or done. Open deals or high priority tickets with no task behind them are easy to miss.

What popdock provides

Give a HubSpot company name and it finds the company, stopping and listing the options if more than one matches. It then reads the open deals and open tickets, and the TickTick tasks planned or recently completed for that company. You get one brief with the company, open deals, open tickets, planned tasks, recently completed work and a list of gaps, meaning deals or high priority tickets with no TickTick task. Nothing is written to HubSpot or TickTick.

Business outcome

---

One follow-up brief shows the CRM status and the planned work together, with gaps called out before the conversation.

scenario

Reps compare the HubSpot deals closing soon against their TickTick to-do list by hand. A deal with a close date next week and no follow-up task is easy to overlook, and it often only shows up when the deal slips.

What popdock provides

Give a number of days ahead, 14 if you do not say, and optionally a deal owner, and it reads the HubSpot deals closing in that window. For each deal it looks for an open TickTick task by deal name, and retries once with the company name. Matching is by name only, so loose matches are marked as possible. You get a table sorted by close date with deals that have no task listed first. Nothing is changed in HubSpot or TickTick.

Business outcome

---

You see which closing deals have no follow-up task before they slip, with uncertain matches marked rather than assumed.

scenario

Before a collections call, you piece a customer's balance, open invoices and recent payments together from Intacct, then search TickTick for the follow-up notes. An overdue account that nobody is chasing is easy to miss.

What popdock provides

Give a customer name and it finds the customer in Intacct, stopping and listing the options if several match. It reads the open invoices and recent payments, 90 days back unless you say otherwise, then looks for open TickTick tasks that mention the customer and reads their comments. You get a one page brief with the account snapshot, open invoices, recent payments, open tasks with the latest comment and a suggested next step. Nothing is changed in either system, and it says TickTick matches are by name text and may be incomplete.

Business outcome

---

Collectors get the money picture and the follow-up history on one page, and a customer with no tracked follow-up stands out.

scenario

Judging how far the month-end close has got means comparing a checklist in a task app against journal entries, bills and invoices in the ledger, by eye. Tasks get ticked without the ledger activity behind them, or the work is done and never marked.

What popdock provides

Give the period start and end and the name of your TickTick close project, and it reads the checklist and the Rillet journal entries, bills and invoices for that period. It reports done, open and overdue checklist counts, ledger counts by status, and which checklist steps such as accruals, bills or invoicing look supported by Rillet activity. Conclusions are marked as inference. If Rillet has no records it says so instead of calling the checklist complete, and it never completes tasks or posts entries.

Business outcome

---

You see which close steps look done, open or at risk against real ledger activity, with inference clearly labelled.

scenario

Before a customer call, reps open NetSuite for the balance, invoices, opportunities and cases, then look through their task app for related work. Stitching it together by hand usually means something is missed, such as an unpaid invoice with no one assigned.

What popdock provides

Give a customer name, and optionally how many days to look back, and it finds the NetSuite customer, stopping and listing the options if several match. It reads their invoices, opportunities and cases, then the open and recently completed TickTick tasks and the comments on open ones. You get a one page brief with profile and balance, open invoices, opportunities, cases, tasks and gaps such as an unpaid invoice or open case with no task. Empty sections are shown as empty, and nothing is changed in either system.

Business outcome

---

Reps walk into a customer call with the NetSuite picture and the internal work together, and with gaps spelled out.

scenario

Prepping for a call means opening Nutshell for the account's people, leads and notes, then searching TickTick for related tasks. Piecing the history together takes time, and the open work is easy to overlook.

What popdock provides

Give a Nutshell account name and it finds the account, stopping and listing the options if more than one matches. It then reads the people, leads and notes, and the open and recently completed TickTick tasks for that account, 90 days back unless you say otherwise, with comments where they are worth reading. You get a brief with an account snapshot, people, open leads, latest notes, tasks and suggested talking points. Nothing is changed in either system, and if TickTick has nothing it says so rather than inventing tasks.

Business outcome

---

You start the call knowing the account history and the open work, without inventing tasks that do not exist.

scenario

Preparing for a customer touch means opening the OnePageCRM history of calls, meetings, notes, deals and actions, then going through the TickTick list for related work. The two never line up on their own, so a next action with no task goes unnoticed.

What popdock provides

Give a contact name, and optionally how many days to look back, 30 by default, and it finds the contact in OnePageCRM, stopping and listing the options if more than one matches. It reads their calls, meetings, notes, deals and next actions, then the open and recently completed TickTick tasks that mention them. You get one brief that says which system each item came from, flags possible namesakes and lists gaps. Nothing is changed in either system, and it stops if either connection is unavailable.

Business outcome

---

You see a contact's CRM history and task list together, with the source of each item clear and possible namesakes flagged.

scenario

Deals near their close date can have no scheduled follow-up, because the CRM and the personal task list are separate. Nobody compares them, so a deal worth real money has no next step until it slips.

What popdock provides

Give a number of days ahead, 14 by default, and optionally a minimum amount, and it reads the pending OnePageCRM deals expected to close in that window. For each one it looks for an open TickTick task by the contact's last name, then by company name. Matching is by name only, so matches are labelled likely, and overdue tasks are flagged rather than counted as coverage. You get a table by close date and the total pending amount of deals with no task. Nothing is changed in either system.

Business outcome

---

You see which closing deals have no live follow-up and how much money is exposed, with weak matches labelled honestly.

scenario

Overdue work is split between Capsule CRM tasks and a TickTick to-do list, so nobody sees the full backlog for a person. Working out which customer each late item belongs to, and who owns that customer, is more manual lookups.

What popdock provides

Give an owner name and it reads that person's overdue Capsule CRM tasks and the overdue TickTick tasks. For TickTick tasks that name a Capsule CRM customer, it looks up the customer and adds the owner and last contacted date, skipping any match that is ambiguous. You get one table sorted by days overdue with the source, item, customer and due date, plus a one line summary per source. Items are merged only when title and due date are the same, and nothing is changed in either system.

Business outcome

---

One overdue list covers Capsule CRM and TickTick with customer context, and nothing is merged unless it really matches.

scenario

Overdue work is split across Nutshell tasks and activities and a TickTick to-do list, so nobody sees one person's full backlog. The same job can also sit in both places and be counted twice.

What popdock provides

Give a person's name and it finds that user in Nutshell, stopping if there is not exactly one match. It reads their overdue Nutshell tasks and activities and the overdue TickTick tasks. You get one table sorted by days overdue with source, title, due date and related record or project, with items that appear in both systems flagged. It ends with totals per source and the three oldest items. If one side is empty it shows the other, and nothing is completed, updated or added.

Business outcome

---

One person's overdue backlog is visible across both systems, with duplicates flagged and the oldest items first.

scenario

Overdue work is split between Pipedrive activities and a personal TickTick list, so there is no single view of what has slipped. The same follow-up can sit in both places, which makes the backlog look bigger or hides what is oldest.

What popdock provides

Give an owner name and how many days to look back, 30 by default, and it finds the Pipedrive user, stopping and listing the options if more than one matches. It reads that user's overdue Pipedrive activities and the overdue TickTick tasks in the same window, and says the TickTick side covers the connected TickTick account. You get one table with the oldest first, possible duplicates marked with reasoning, and counts per source. Nothing is changed in either system.

Business outcome

---

Everything that has slipped sits in one list ordered by how late it is, with possible duplicates explained.

scenario

Reps keep follow-ups in both Pipedrive and TickTick, and nobody notices which calls and meetings never made it onto the personal task list. A commitment that exists in only one place is easy to forget.

What popdock provides

Give an owner name and how many days ahead, 7 by default, and it finds the Pipedrive user, stopping and listing the options if more than one matches. It reads their open Pipedrive activities and looks in TickTick for a task whose title refers to the same job and whose due date is within 2 days. You get two tables, matched activities and those missing from TickTick with type, due date, contact and deal. Fuzzy matches show the reasoning, it never guesses a match, and nothing is changed in either system.

Business outcome

---

Reps see which Pipedrive commitments are not on their TickTick list, with every match explained rather than assumed.

scenario

Before a meeting, a rep opens Pipedrive for deals, notes and calls, then hunts through a task app for loose commitments made to that person. One of those commitments usually gets missed.

What popdock provides

Give a contact name or email, and optionally how many days to look back, 30 by default, and it finds the person in Pipedrive, stopping and listing the options if more than one matches. It reads open deals for their organization, planned activities, recent notes and call logs, then open and recently completed TickTick tasks that name the organization or the person. You get a one page brief with three suggested talking points. If a side has no data it says so rather than inventing any, and nothing is changed in either system.

Business outcome

---

Reps arrive at a meeting with deals, history and personal commitments in one page, with empty sides stated honestly.

scenario

Open deals go quiet when no activity is scheduled in Pipedrive and nothing sits on the rep's task list. It only shows up when the deal slips, because checking each deal in both places by hand rarely happens.

What popdock provides

Give an owner name, and optionally a minimum deal value, and it finds the Pipedrive user, stopping and listing the options if more than one matches. It reads their open deals, checks each for an open Pipedrive activity and the nearest due date, then looks for an open TickTick task that clearly names the deal or its organization. You get a table sorted by value, then the deals with no follow-up anywhere. Unmatched deals are reported as none rather than guessed, and nothing is changed in either system.

Business outcome

---

Deals with no follow-up in either system are surfaced by value, before they go quiet and slip.

scenario

Every morning means opening several lists and sorting overdue and due tasks by hand to decide what comes first. Priorities get missed, and tasks already under way are treated like fresh ones.

What popdock provides

Give a date, and optionally a TickTick project, and it reads your open overdue tasks and the tasks due on that day. It ranks them by priority, then how overdue they are, then due time, flags tasks that already have progress recorded as in progress, and groups sub-tasks under their parent. You get a numbered plan with a one line reason for each position and a short list of tasks to consider deferring. If nothing is due it says so and stops. It only reads and never changes a task.

Business outcome

---

You start the day with a ranked plan and reasons, built from overdue and due tasks without opening each list.

scenario

Your personal to-dos sit in TickTick while the incidents assigned to you sit in ServiceNow, so the day gets planned from one list and the other is ignored. An incident with an SLA about to breach can sit unseen behind a routine task, and nobody notices until the breach has already happened.

What popdock provides

Give a name and how many days ahead to plan, and it reads your open TickTick tasks, including overdue ones, and the open ServiceNow incidents assigned to that person with their SLA breach times. It merges them into one ordered plan with breached or breaching SLAs first, then critical and high priority incidents, then overdue tasks, then the rest by due date. A task that cites an incident number is shown as one line. Nothing is changed in either system, and if the name matches no ServiceNow user exactly, that side is skipped rather than guessed.

Business outcome

---

One ordered daily plan across TickTick and ServiceNow, so SLA risks are seen before the routine tasks, with nothing changed in either system.

scenario

Past-due receivables are reviewed in Dynamics GP, but follow-up work is tracked somewhere else, so nobody checks that each large overdue customer actually has someone chasing it. The account with the biggest balance can go weeks without an owner because the two lists are never compared.

What popdock provides

Give a minimum number of days past due, and optionally a company and how many customers to keep, and it reads the past-due receivables in PowerGP Online and totals the amount per customer. For each of the largest customers it looks in TickTick for an open task that names the customer or customer number. You get a table sorted by amount showing the oldest days past due and the matching task, or NONE, with a total for the uncovered customers. Partial name matches are flagged as possible, not covered. It only reads, and stops if nothing meets the threshold.

Business outcome

---

Large overdue customers with no follow-up task are found in one pass, so collections work is not missed, and nothing is changed.

scenario

Before a collections call, someone pulls a customer's balance and open receivables from Dynamics GP, then searches TickTick for the follow-up notes, and pieces the two together by hand. The overdue account that nobody is chasing is easy to miss, because the gap only shows when both sources are read together.

What popdock provides

Give a customer name or number and optionally a company, and it finds the customer in PowerGP Online, stopping to list the matches if there is more than one. It reads their open receivables and any sales holds, then looks in TickTick for tasks that name the customer and reads the latest comments on each. The brief shows balance, hold status, open receivables, the TickTick tasks, and gaps such as 60 days past due with no open task. TickTick is matched only on the name or number in the task title, and nothing is changed.

Business outcome

---

One page shows a customer's balance, holds and follow-up work together, so unchased overdue accounts stand out, with nothing changed.

scenario

Purchase orders waiting for approval in Dynamics GP can sit for weeks because nobody is tracking them. The first sign is often a vendor calling about an unpaid or unconfirmed order, since the approval queue and the task list are never checked against each other.

What popdock provides

Give an age threshold in days, and optionally a company, and it reads the purchase orders in PowerGP Online that are still pending approval and older than that. For each order it looks in TickTick for a task naming the purchase order number, falling back to the vendor name only to mark a possible match. You get a table with PO number, vendor, date, remaining subtotal, approver and task, sorted by largest subtotal. It states which pending status value it used, only reads, and stops if nothing is pending.

Business outcome

---

Aged purchase orders with no tracking task are visible before a vendor chases them, with the largest exposure first.

scenario

What you owe a vendor lives in Dynamics GP, while the tasks and notes about that vendor live in TickTick. Without checking both, due invoices are missed, or two people chase the same one, and nobody sees that an invoice due this week has no task against it.

What popdock provides

Give a vendor name or ID and optionally a company, and it finds the vendor in PowerGP Online, stopping to list the matches if several fit. It reads their balance, hold status, open payables ordered by due date and open purchase orders. It then looks in TickTick for tasks that name the vendor and reads the latest comment on each. Invoices due within 7 days with no task are called out. If TickTick finds nothing it says no tracked work instead of inferring any, and it never changes data.

Business outcome

---

Vendor payables and follow-up work appear side by side, so invoices due soon without a task are caught and nothing is chased twice.

scenario

Before a meeting, someone opens the Granola notes, then the TickTick task list, and then guesses who owes what. Overdue items and recent comments are easy to forget, so the meeting starts without the actions that most need discussing.

What popdock provides

Give a meeting title and optionally a TickTick project, and it finds the matching Granola meeting, stopping to list the options if several match. It reads the time, organiser, summary and attendees, then finds the project in TickTick and its open tasks, matching each attendee to assignees by name or email prefix. Overdue tasks are flagged and comments from the last 14 days are read. The briefing lists open tasks by attendee, recent discussion and suggested topics. Attendee matches are labelled probable, and nothing is changed.

Business outcome

---

You walk into the meeting knowing who owns which open and overdue tasks, with matches labelled probable where they are uncertain.

scenario

Before donor calls, staff read each task in TickTick, then look up every donor in the CRM one at a time to find their gifts, contacts and notes. Prep is slow and uneven, and a call can go ahead without knowing the donor's last gift or the last conversation.

What popdock provides

Give how many days ahead to look, and optionally a TickTick project, and it reads open tasks due in that window and keeps the ones that name a person. For each name it looks for a single matching constituent in Bloomerang and reads the latest gifts, contacts and notes. If a donor is not found or has several matches it lists the task as not found and never guesses. The agenda is in due date order with last gift, last contact, key notes and a suggested talking point. Nothing is changed in either system.

Business outcome

---

Each donor call starts with giving and contact history ready, so prep is quicker and consistent, with nothing changed in either system.

scenario

Overdue donor tasks pile up in TickTick with nothing to show which donors matter most. A follow-up with a major donor can wait behind a small one, because working out the giving behind each name means searching DonorPerfect one donor at a time.

What popdock provides

Optionally give a TickTick project, and it reads the overdue open tasks, takes the person or organization name from each title and looks for a single matching donor in DonorPerfect. Matched donors are ranked by year to date giving, then total giving, using the figures on the donor record and checking gifts over the last 12 months only when totals are missing. Several matches are shown as ambiguous rather than guessed, and tasks with no donor name are listed apart. Task priorities are only suggested, never changed.

Business outcome

---

Overdue donor follow-ups are ordered by giving, so the most important donors are contacted first, with nothing changed.

scenario

Donor follow-ups are logged as tasks in the CRM, while personal to-dos are kept in TickTick, and nobody checks that each follow-up has a matching task. Some get dropped, and some TickTick tasks look like donor follow-ups that never made it into Bloomerang.

What popdock provides

Give how many days ahead to check, and optionally a constituent name, and it reads open Bloomerang tasks due in that window and the open TickTick tasks due by the same date. It pairs them when the TickTick title contains the Bloomerang subject or the constituent name and the due dates are within 2 days. The report has three tables: matched, in Bloomerang only and in TickTick only, with counts. Uncertain pairs are labelled possible matches, an ambiguous constituent name stops the check, and nothing is changed.

Business outcome

---

Donor follow-ups missing from either list are found in one pass, so fewer are dropped, and nothing is changed in either system.

scenario

Tasks are kept in both Capsule CRM and TickTick, and over time the two drift apart. A follow-up exists on one side only, or the due dates differ, so work is missed or tracked twice, and finding the gaps means comparing two lists by eye.

What popdock provides

Give an owner and how many days ahead to check, and it reads that owner's open Capsule CRM tasks due in the window and the open TickTick tasks due in the same window. A pair is made only when the TickTick title contains the Capsule description or party name and the due dates are within one day. The report lists Capsule tasks with no TickTick counterpart, TickTick tasks that mention a Capsule party but have no Capsule task, and matched pairs with different dates, with counts. Undated tasks are listed separately, and nothing is changed.

Business outcome

---

Tasks missing or mismatched between Capsule CRM and TickTick are found quickly, so follow-ups are neither missed nor doubled, and nothing is changed.

scenario

TickTick tasks that cite ServiceNow tickets drift out of step with the tickets. A task stays open after its incident is closed, or its priority is lower than the record's, and checking each one by hand is slow enough that it gets skipped.

What popdock provides

Name a TickTick project, and it reads the open tasks and finds the INC, CHG and PRB numbers in each title or content. It then looks each number up in ServiceNow and flags tasks whose record is resolved, closed or canceled while the task is open, whose priority is higher than the task, or whose assignee differs. The report is a table with counts of tasks checked, clean and citing a number not found. Unknown or ambiguous numbers are reported instead of guessed, and nothing is changed in either system.

Business outcome

---

Out of step tasks and ServiceNow records are found in one pass, so stale and under-prioritised work is corrected, and nothing is changed.

scenario

Bad satisfaction ratings are reviewed in Zendesk, but there is no easy way to see whether anyone followed up. If the follow-up task lives in TickTick, someone has to search for each ticket by hand, and an unhappy customer can be left without a reply.

What popdock provides

Give a score, bad by default, and how many days to look back, 30 by default, and it reads the matching Zendesk satisfaction ratings. For each ticket it searches TickTick open and completed tasks for the ticket ID in the title. You get a table of ticket, subject, assignee, the customer comment quoted as written, and follow-up state of open task, completed task or none, with the ratings that have no follow-up first. The match is on title text only, never assumed, and nothing is changed in either system.

Business outcome

---

Unhappy customers with no follow-up are listed first, so gaps are closed sooner, and nothing is changed.

scenario

Planning a finance team's week means eyeballing bill and invoice due dates in the ledger against a task list, then guessing at capacity. A day with many payments due and few tasks planned, or too many tasks for the time available, only shows up once it has gone wrong.

What popdock provides

Give how many days ahead to plan, and optionally an assignee, and it counts unpaid Rillet bills and open invoices by due date across the window. It reads open TickTick tasks due in the same window and the focus sessions from the last 14 days to estimate typical focus minutes per day. The report shows, per day, bills due, invoices due, tasks due and focus minutes, flagging heavy ledger days with few tasks and task counts beyond typical focus capacity. It notes that task counts ignore task size, skips the capacity check when there is no focus data, and changes nothing.

Business outcome

---

You see which days the finance workload outgrows planned tasks and focus time, so the week can be rebalanced before it slips.

scenario

Preparing for an account means searching Salesforce for opportunities, tasks and cases, then searching TickTick for related work, and stitching the results together. Something is usually missed, such as an open case that nobody has a task for.

What popdock provides

Give an account name and optionally how many days to look back, 30 by default, and it finds the account in Salesforce, stopping to list the options if several match. It reads the open opportunities, tasks and cases for that account, then looks in TickTick for open tasks and recently completed tasks that name the account. The view has an account summary, the Salesforce items, the TickTick items and up to three gaps. TickTick has no account field, so it says those results are matched on name text only, and nothing is changed.

Business outcome

---

One view of an account's Salesforce activity and TickTick work shows the gaps before the meeting, and nothing is changed.

scenario

Someone working a TickTick task about a customer has to leave it and search Shopify for the customer's profile, orders and refunds. The email on the task may differ slightly from the one in the store, so the lookup is slow and easy to get wrong.

What popdock provides

Give the task title, and optionally the customer email, and it finds the TickTick task and its comments, stopping to list the options if several tasks match. It takes the email or name from the input, task or comments, then finds the customer in Shopify, again stopping if several match. It pulls their orders and refunds and summarises the task, profile, last 5 orders, refunds and what the owner should know. Emails are matched ignoring case and spacing, an absent customer is reported rather than guessed, and nothing is changed.

Business outcome

---

The task owner sees the customer's Shopify profile, orders and refunds without leaving the task, with nothing changed.

scenario

A TickTick task mentions a contact, and the person has to open the email platform separately to check their lists, recent activity and whether they agreed to receive email. A step is easily skipped, and a message goes to someone who has not given permission.

What popdock provides

Give the task title and optionally a contact email, and it finds the TickTick task, stopping to list the options if several match. It takes the email from the task title or your input, and asks for one if neither has it. It then looks the contact up in Constant Contact and reads list memberships, the last 10 activities and notes. The report shows task, contact details, lists, activity and notes, then says plainly whether permission to email is a clear yes. A missing contact is reported, not guessed, and nothing is changed.

Business outcome

---

You know who the contact is, what they have done and whether you may email them, without leaving the task.

scenario

Support staff look at a customer's survey feedback in Simplesat and their open work in TickTick separately. An unhappy customer with no one assigned to them is easy to miss, because the two places are never read side by side.

What popdock provides

Give a customer email and optionally how many days to look back, 90 by default, and it finds the customer in Simplesat and stops if there is no match. It reads their survey responses and answers, then looks in TickTick for open and completed tasks that name the customer or their company. The report has a customer header, a feedback table with sentiment and choice, a task table, and a line on whether any negative feedback has no matching open task. Name matches are labelled likely, and nothing is changed in either system.

Business outcome

---

Customers with negative feedback and no one working on it are spotted quickly, and nothing is changed.

scenario

Marketing picks happy customers for testimonials from survey scores, but the outreach lives as tasks in a separate task manager. Without checking both, the same customer gets asked twice, or a glowing answer already published as a testimonial gets chased again.

What popdock provides

Name how many days to look back (30 by default) and it lists the positive Simplesat answers from that window, skipping any already published as a testimonial. For each answer it finds the customer name, email and company, then searches TickTick, open and completed, for a task naming that customer. You get one table with customers who have no outreach task listed first, and a name-only match is flagged as possible. Nothing is changed in Simplesat or TickTick.

Business outcome

---

Marketing sees which happy customers still need a testimonial request and which are already being contacted, so nobody is asked twice.

scenario

Working out where a long task stands means opening it, reading every sub-task and scrolling through the whole comment thread to find what was decided and what is still open. Anyone picking it up cold has to rebuild that picture by hand.

What popdock provides

Give the task title, and optionally the project, and it finds the matching TickTick task, checking completed tasks too if nothing open matches. It reads the sub-tasks and the comments in time order, then reports status, due date, priority, assignee and tags, sub-task progress, a short summary of the discussion with decisions and open questions, and a suggested next action. If more than one task matches it lists them and stops. It only reads, and never posts a comment or edits a task.

Business outcome

---

You pick up any TickTick task knowing its status, decisions and open questions without reading the whole thread.

scenario

Focus time is logged against tasks in TickTick, while the priority of the incidents behind that work sits in ServiceNow. Nobody can easily tell whether hours are going to the critical incidents or to low priority ones, because the two never meet in one view.

What popdock provides

Give a start date, and optionally a TickTick project, and it reads the focus sessions since then and finds the ServiceNow incident numbers cited in the task titles. It totals the time per incident, looks each incident up in ServiceNow for priority and state, and reports hours and minutes with sessions on tasks that cite no incident counted as other work. It names any critical or high priority incident with no focus time and any low priority one taking over 25 percent of the total. It only reads and never invents an incident for a task that cites none.

Business outcome

---

You see whether focus time follows incident priority, and which urgent incidents are getting none.

scenario

Focus sessions are recorded in one place and the tasks and projects they belong to in another, so the hours spent per task or project are never worked out. Adding it up by hand from the app means a lot of cross-checking, and sessions without a task muddy the totals.

What popdock provides

Give a date range, and optionally a minimum session length, and it reads the TickTick focus sessions in that period. It looks up the task and project behind each session, including completed tasks, then reports total focus time and session count, time per project and per task with the largest first, and time by day to show the pattern. Sessions with no task and sessions added manually are counted separately, and it never guesses a project. Nothing is changed.

Business outcome

---

You know where focus time actually went, by project, task and day, without adding sessions up by hand.

scenario

Habit streaks are checked one habit at a time in the app, so a habit that is slowly slipping goes unnoticed until it has already lapsed. Comparing check-ins with how often each habit is meant to happen takes a lot of counting.

What popdock provides

Give a date range, and optionally a habit name, and it reads your TickTick habits and their check-ins for the period. It compares completed check-ins with the days each habit's repeat rule expects, and whether the value met the goal. You get a ranked table with expected, done, rate and trend, plus the two weakest habits with a realistic change for each. If a habit has no repeat detail it says the expectation is unknown rather than assuming daily. Habits and check-ins are never changed.

Business outcome

---

You see which habits are holding and which are slipping, ranked by consistency, without counting check-ins yourself.

scenario

Overdue tasks pile up across projects and nobody decides what to do with them. Some are a small slip, some are stale and some were abandoned long ago, but without sorting them by age and project they all sit in the same long list.

What popdock provides

Give an as-of date, and optionally a project and a minimum number of days overdue, and it reads the open TickTick tasks that are past due. It sorts them into recent slips, stale and likely abandoned, notes recurring tasks separately, and suggests one action for each: do now, reschedule, split, delegate or delete, based on priority, age and progress. You get a table by age band and counts per project. It only recommends, and carries out nothing unless you ask separately.

Business outcome

---

Every overdue task gets a clear do, reschedule or drop decision, and nothing is changed until you say so.

scenario

Writing a project update means opening the board, counting tasks in each column, checking which are overdue and what is due soon, and then turning that into a paragraph a stakeholder can read. It is slow, and the counts are easy to get wrong.

What popdock provides

Give a project name and an as-of date and it finds the TickTick project, stopping to ask if the name matches more than one. It reads the board columns, the open tasks and recent completions, then reports tasks per column, open against completed counts, overdue tasks, tasks due in the next 7 days, unassigned tasks and tasks per assignee. It ends with risks and a one-paragraph summary a stakeholder could read. It only reads and changes nothing.

Business outcome

---

You get an accurate project status, with counts, risks and a ready summary, in a minute rather than a manual board review.

scenario

Tag lists grow messy over time, with near-duplicates like Urgent and urgent, tags nobody uses any more and child tags under parents that are rarely used. Cleaning up means counting how often each tag appears across every task by hand.

What popdock provides

Give a look-back period, 365 days by default, and it reads your TickTick tags and counts how they are used on open and completed tasks in that period. You get the tags never used, near-duplicates differing by case, plural or spacing, the most used tags and their share, and child tags whose parent is rarely used. It ends with a suggested merge or removal list. It only reads, and leaves any tag changes to you.

Business outcome

---

You get an evidence-based list of tags to merge or remove, and keep full control of the actual clean-up.

scenario

In a shared TickTick project, uneven workloads are usually spotted only when someone is already overloaded. Counting open, overdue and high priority tasks for each person by hand is tedious, and unassigned work slips through.

What popdock provides

Give a project name and an as-of date and it finds the TickTick project, asking you to choose if several match. It reads the project members and the open tasks, then reports per member the open, overdue, high priority and due in 7 days counts, plus unassigned open tasks. It names members with no work and those carrying well above the average, and suggests rebalancing with specific tasks. It never reassigns anything itself.

Business outcome

---

You see who is overloaded and who has capacity before it becomes a problem, and decide the moves yourself.

scenario

Deadlines are scattered between task due dates and separate countdown dates, so no single view shows what is coming. Days where several high priority tasks land together are only noticed once they arrive.

What popdock provides

Give a start and end date and it reads the open TickTick tasks due in that window and the countdowns that fall in it. It merges them into one chronological list, marks each as a task or countdown with the days remaining, flags days with several high priority tasks as crunch points, and marks recurring countdowns. If the dates are the wrong way round it asks, and if both are empty it says the window is clear. No tasks or countdowns are changed.

Business outcome

---

One timeline shows every deadline and crunch day in the window, so you can plan before the pressure lands.

scenario

A weekly review means reconstructing the week from memory and from several lists: what got finished, what slipped past its due date and how much focused work really happened. Without the facts, wins and slippage are guessed.

What popdock provides

Give a date range, and optionally a project, and it reads the TickTick tasks completed in that period, the open tasks that were due and are still not done, and the focus sessions with their total time. You get the completed count grouped by project with notable titles, slipped tasks oldest first, total focus hours and the tasks that got the most focus, then three observations and one suggestion for next week. If nothing was completed it says so rather than inferring. It never edits tasks.

Business outcome

---

You get a factual weekly review, with wins, slippage and focus time, in place of a review written from memory.

scenario

Account managers check a customer's balance and open items in Dynamics GP, then hunt through TickTick by hand for the tasks tied to that customer. Because TickTick has no customer ID, work that is not named consistently is easily missed.

What popdock provides

Give a Dynamics GP customer ID, and optionally how many days to look back for completed work, and it reads the customer's balance, credit limit, hold flag, last 10 documents and open service calls from Dynamics GP. It then searches TickTick by customer name and ID for matching tasks, their comments and completed work, and lists the match basis for each. Uncertain matches are flagged instead of attributed, and gaps such as an overdue document with no task are called out. It only reads, and stops if the customer is not in Dynamics GP.

Business outcome

---

You see a customer's account position and all related TickTick work in one view, with weak matches flagged.

scenario

Checking whether a Jira issue is tracked in TickTick means searching both tools by hand. Stale tasks left open after the issue is Done, duplicate tasks and mismatched due dates are easy to miss.

What popdock provides

Give a Jira issue key and it reads the issue's summary, status, assignee and due date from Jira. It then finds every TickTick task, open or completed, whose title carries that key, matching on the key only and not on summary text. You get the issue beside a table of those tasks, with differences flagged, such as a task still open while the issue is Done or a due date that does not match. If the issue is not found it stops, and nothing is written in either system.

Business outcome

---

You know in one check whether a Jira issue is properly tracked in TickTick, and where the two disagree.

scenario

Finding out what happened to an order means checking Shopify for fulfillment and refunds, then searching TickTick for any tasks or comments about it. The pieces are in two tools and in no particular order, so the story takes a while to piece together.

What popdock provides

Give a Shopify order number and it finds the order, stopping if it matches none or more than one. It reads the order's fulfillment orders, fulfillments and refunds from Shopify, then searches open and completed TickTick tasks for the order name and number and reads their comments. You get one dated timeline marked Shopify or TickTick, ending with the current state and any gap, such as an unfulfilled order with no task. Matching to tasks is by title text only, and it says so. It never creates a task.

Business outcome

---

You get one dated timeline of an order across Shopify and TickTick, with gaps visible, instead of two searches.

scenario

After a customer answers a survey, working out what was done about it means digging through the ticket, then through tasks, comments and time spent in a separate task manager. Without that trail it is hard to say whether the feedback was actually addressed.

What popdock provides

Give a support ticket ID and it finds the Simplesat response and reads its answer, sentiment and choice, plus the customer name and ticket subject. It then searches TickTick for tasks naming the ticket, retrying with the subject or customer, reads each task's comments and totals the focus time spent. You get a timeline from survey answer to task creation, comments and completion, with focus minutes and a one-line status. It stops if the response is ambiguous or missing, and it changes nothing in either system.

Business outcome

---

You can tell whether a customer's survey feedback was acted on, with the trail of work and time behind it.

scenario

Staff compare the list of unfulfilled Shopify orders with their TickTick to-do list by eye. Orders with no follow-up task go unnoticed, and tasks for orders that have since shipped stay open and clutter the list.

What popdock provides

Name how many days to look back (14 by default) and optionally a TickTick project. It reads the unfulfilled Shopify orders in that window and the open TickTick tasks, then matches them by order name or number in the task title. You get three tables: orders with a task, orders with none, and open tasks naming an order that is no longer unfulfilled. Ambiguous matches are flagged and matching by text is stated. Nothing is changed in Shopify or TickTick.

Business outcome

---

You see which unfulfilled orders have no follow-up and which tasks are stale, so no order falls through.

scenario

Meetings sit in one tool and deadlines in another, so an overloaded day is only discovered when it arrives. Adding up meeting hours against tasks due, overdue work and countdowns across a week is easy to skip.

What popdock provides

Name how many days ahead to look (7 by default) and optionally a TickTick project. It reads your scheduled Granola meetings, then the TickTick tasks due, countdowns and overdue open tasks for the same window. You get a day-by-day view of meetings, tasks due and countdowns, with days flagged where meetings run over 4 hours and tasks are due, the overdue tasks with days late, and the three hardest days. A meeting with no end time is treated as one hour and marked as an estimate. It reschedules nothing.

Business outcome

---

You spot the hardest days of the week ahead before they arrive, with meetings and deadlines in one view.

scenario

Next steps for a deal live in two places: the deal and its tasks in the CRM, and your own task list in TickTick. Nobody lines them up, so a deal can sit with no open task anywhere and stall without anyone noticing.

What popdock provides

Name a company and it finds it in Attio, then shows its deals and open tasks. It also searches TickTick for tasks that mention the company or each deal and lists them with project, due date and status. Because the two systems share no id, TickTick results are labelled as name matches, and the report ends with the deals that have no open task in either system. It stops if the company is ambiguous, and nothing is changed.

Business outcome

---

Stalled deals show up because every next step from both systems sits in one place, with name matches labelled and nothing changed.

scenario

Judging someone's workload from the CRM alone hides the personal tasks they also carry in TickTick. A person who looks free in Attio can have a packed week, so overload goes unnoticed until something slips.

What popdock provides

Name an owner and how many days ahead to look, and it reads their open Attio deals and tasks and their TickTick tasks. It merges them into a day by day list with the source marked on each line, then shows open deals, overdue items and anything undated. Days with more than 5 items are flagged. If TickTick has no tasks under that name, it says which TickTick account the result came from. Nothing is changed.

Business outcome

---

Leaders see real workload across both systems and spot overloaded days before work slips, with nothing changed.

scenario

Reps compare CRM follow up tasks against their personal task list by eye. A commitment logged in Attio that never made it into TickTick drops through the gap, and nobody sees it until the customer chases.

What popdock provides

Say whose tasks to check, if you want to narrow it, and how many days ahead to look. It reads the open Attio tasks due in that window and searches TickTick for each one by its wording. You get two lists: tasks missing in TickTick and tasks already there, with counts. When several TickTick tasks could match, it marks the Attio task as ambiguous instead of guessing. Nothing is changed in either system.

Business outcome

---

CRM follow ups no longer slip through the gap, because every missing or doubtful match is listed for you to handle.

No items found.

ready, go

Tools for TickTick

Start with ready-made MCP tools for the TickTick. Each one gives your AI client a single, clearly defined job: get invoices or journal entries, pull a file, or create and update records. Add a tool to your PopdockAI MCP server, choose the fields it returns and who can use it, and it's ready in Claude, ChatGPT or Microsoft Copilot. Nothing is exposed that you haven't switched on.

Name of tool

Description

get-data

ticktick-get-tasks

Returns open TickTick tasks with their project, due date, priority, status, assignee and tags. Filter by project, due date range or status.

get-data

ticktick-get-task-comments

Returns the comments on a TickTick task with author and time.

get-data

ticktick-get-tags

Returns the tags defined in TickTick with their colour and parent tag.

get-data

ticktick-get-subtasks

Returns the sub-tasks (checklist items) of a TickTick task with their completion status.

get-data

ticktick-get-projects

Returns TickTick projects (lists) with their name, group, view mode and archived status.

get-data

ticktick-get-project-members

Returns the people a TickTick project is shared with, for assignee and workload questions.

get-data

ticktick-get-project-groups

Returns the folders (project groups) that organise TickTick projects.

get-data

ticktick-get-habits

Returns TickTick habits with their goal, repeat rule, streak and status.

Ready to unlock your data?

‍

Start building tools that turn your business systems into AI superpowers

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Capabilities that matter most for TickTick

Example AI Use Cases for TickTick

Audit unactioned negative Simplesat feedback in TickTickCustomer Support

BigCommerce customer brief with TickTick tasksSales

BigCommerce order coverage by TickTick tasksOperations

BugHerd bug workload against TickTick scheduleOperations

Bugsnag release risk against TickTick planProject Management

Business Central customer brief with TickTick tasksSales

Capsule CRM customer activity and TickTick focus timeSales

Check a GitHub milestone against TickTick tasksProject Management

Check completed TickTick tasks against NetSuite receivablesFinance

Check Constant Contact campaigns for TickTick follow-up tasksMarketing

Check Dynamics SL contract renewals in TickTickSales

Check Granola meeting action items against TickTick tasksProject Management

Check HubSpot meetings for TickTick prep tasksOperations

Check Nutshell lead follow-up coverage in TickTickSales

Check overdue HubSpot tasks against TickTickSales

Check ServiceNow change windows against TickTickProject Management

Check TickTick and Jira date driftProject Management

Check TickTick coverage of Capsule CRM opportunitiesSales

Check TickTick task coverage for late Dynamics GP purchase ordersOperations

Chorus account meeting brief with open TickTick tasksSales

Compare Chorus call time with TickTick focus timeLeadership

Compare Dynamics 365 Sales tasks with TickTickOperations

Compare Dynamics GP project hours with TickTick focus timeProject Management

Compare Granola meeting time with TickTick focus timeLeadership

Compare Intacct project tasks with TickTickProject Management

Compare Intacct timesheets with TickTick focus timeOperations

Compare NetSuite project tasks with TickTickProject Management

Compare TickTick focus time with Business Central timesheetsOperations

Compare TickTick focus time with Constant Contact campaign resultsLeadership

Dynamics 365 Sales and TickTick daily agendaLeadership

Dynamics 365 Sales customer 360 with TickTick workSales

Find BugHerd bugs missing in TickTickProject Management

Find Bugsnag errors without TickTick tasksDevelopers

Find Business Central job tasks missing from TickTickProject Management

Find Business Central opportunities without a TickTick follow-upSales

Find Chorus calls with no TickTick follow-up taskSales

Find completed TickTick donor tasks not logged in DonorPerfectData and Analytics

Find DonorPerfect follow-ups with no TickTick taskOperations

Find Dynamics 365 Sales opportunities without a TickTick follow-upSales

Find Jira issues without a TickTick taskProject Management

Find Nutshell tasks missing in TickTickSales

Find OnePageCRM actions missing from TickTickSales

Find open GitHub issues without a TickTick taskDevelopers

Find open TickTick tasks for closed BugHerd bugsProject Management

Find overdue NetSuite receivables without TickTick tasksFinance

Find Rillet bills due with no TickTick taskFinance

Find Salesforce opportunities without a TickTick follow-upSales

Find stale TickTick tasks for solved Zendesk ticketsCustomer Support

Find TickTick tasks for a DonorPerfect donorOperations

Find TickTick tasks for a Zendesk ticketCustomer Support

Find Zendesk tickets missing a TickTick taskCustomer Support

Focus time by Salesforce accountLeadership

GitHub commits and TickTick focus time reportLeadership

HubSpot account follow-up brief with TickTick tasksSales

HubSpot deals closing with no TickTick taskSales

Intacct customer brief with TickTick tasksFinance

Month-end close progress from TickTick and RilletFinance

NetSuite customer brief with TickTick tasksSales

Nutshell account prep brief with TickTick tasksSales

OnePageCRM contact brief with TickTick tasksSales

OnePageCRM deals closing with no TickTick follow-upSales

Overdue Capsule CRM and TickTick workLeadership

Overdue Nutshell and TickTick work for one personOperations

Overdue Pipedrive and TickTick workOperations

Pipedrive activities missing in TickTickSales

Pipedrive contact meeting brief with TickTick tasksSales

Pipedrive deal follow-up coverage in TickTickSales

Plan my day in TickTickOperations

Plan my day with the ServiceNow queueIT and Integration

PowerGP Online collections coverage audit against TickTickFinance

PowerGP Online customer account brief with TickTick tasksFinance

PowerGP Online purchase approvals tracking check in TickTickOperations

PowerGP Online vendor payables with TickTick follow-upOperations

Prepare a Granola meeting with TickTick task contextProject Management

Prepare TickTick donor call agenda with Bloomerang historySales

Rank overdue TickTick donor tasks by DonorPerfect givingLeadership

Reconcile Bloomerang tasks with TickTickOperations

Reconcile Capsule CRM and TickTick tasksOperations