Integration
Connect ProcessPlan and TimeKeeper
When Field Updated fires in ProcessPlan, your agent runs Add activity in TimeKeeper, or Employee Clock In in TimeKeeper to Complete a Task in ProcessPlan. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want ProcessPlan and TimeKeeper to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What ProcessPlan and TimeKeeper can do together
From ProcessPlan to TimeKeeper
When Field Updated in ProcessPlan
then Add activity in TimeKeeper
From TimeKeeper to ProcessPlan
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with ProcessPlan and TimeKeeper
Triggers and actions 14 triggers · 20 actions
- Field Updated
Triggers when a field value on a running process is changed.
- Process Instance Completed
Triggers when a process is completed.
- Process Instance Started
Triggers when a new process is started.
- Task Assigned
Triggers when a task is assigned to someone.
- Task Canceled
Triggers when a task is canceled.
- Task Completed
Triggers when a task is completed.
- Task Due Date Changed
Triggers when a pending task's due date is set or changed.
- Task Notes Updated
Triggers when the notes on a pending task are updated.
- Task Past Due
Triggers when a pending task becomes past due.
- Task Start Date Changed
Triggers when a pending task's start date is set or changed.
- Cancel a Process
Cancels a running process.
- Cancel a Process Task
Cancels a pending task in a running process.
- Complete a Task
Completes a pending task by submitting one of its responses.
- Find a Process Instance
Finds process instances whose properties match a filter, such as the instance description.
- Start a New Process
Starts a new process from a process template and fills in its starting fields.
- Start a Process Task
Starts a task in a running process out of its normal order. Use with caution.
- Update Process Fields
Saves new values into one or more fields of a running process.
- Employee Clock In
Triggers when an employee clocks in, returning the new time entry with its employee, job, activity and start time.
- Employee Clock Out
Triggers when an employee clocks out, delivering the completed time entry with its start and end times, duration, job and activity.
- Leave Request Approved
Triggers when a leave request is approved in TimeKeeper, for leave falling between 30 days ago and 59 days ahead.
- Who's In
Triggers when an employee appears on the Who's In list, i.e. each time someone clocks in, with their location, last job and clock-in time.
- Add activity
Creates a new activity in TimeKeeper that employees can log time against.
- Add a Job
Creates a new job in TimeKeeper with a name and optional job number and address.
- Get employee timesheet
Returns an employee's timesheet for a date range, including total regular, overtime and leave hours plus each day's time entries and leave.
- Get job breakdown report
Generates a breakdown report for one TimeKeeper job over a date range of up to 60 days.
- List activities
Returns every activity set up in your TimeKeeper account, with each activity's name and number.
- List employees
Returns the employees in your TimeKeeper account, including archived ones, with their contact details, job title, teams and working locations.
- List jobs
Returns every job in your TimeKeeper account, with each job's name, job number, completion status and id.
- List leave entries
Returns employee leave entries (annual leave and other leave types) within a date range of up to 30 days, optionally for one employee or one leave type. Public holidays are not included.
- List leave requests
Returns the leave requests in your TimeKeeper account for a date range of up to 90 days, optionally filtered by status, leave type or employee. Returns open requests unless another status is chosen.
- List shifts
Returns the draft, open and published shifts scheduled in a date range of up to 90 days, optionally for one employee. Shift times are in UTC.
- List time entries
Returns the time entries recorded in your TimeKeeper account for a date range of up to 90 days, optionally narrowed to one employee, job or activity.
- Update activity
Updates the name and activity number of an existing activity in TimeKeeper.
- Update a Job
Updates an existing job in TimeKeeper, changing its name, job number, address or address coordinates.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from ProcessPlan
ProcessPlan to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ProcessPlan to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ProcessPlan to StripeStripe is a payment processing platform for online businesses.
ProcessPlan to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
ProcessPlan to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
ProcessPlan to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into TimeKeeper
HubSpot to TimeKeeperHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to TimeKeeperGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TimeKeeperGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TimeKeeperGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ProcessPlan and TimeKeeper, answered
What can start an automation from ProcessPlan?
Any of ProcessPlan's 10 triggers in the catalog, including Field Updated, Process Instance Completed, Task Completed and Task Due Date Changed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TimeKeeper when something happens in ProcessPlan?
Any of TimeKeeper's 13 actions, including Update activity, Update a Job, Add activity and Add a Job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TimeKeeper to ProcessPlan?
Yes. When something happens in TimeKeeper, your agent can act in ProcessPlan too. This page covers both directions: TimeKeeper's triggers and ProcessPlan's actions are listed here as well.
Do I have to build a connector for ProcessPlan or TimeKeeper?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use ProcessPlan and TimeKeeper without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.