---
title: "Connect Pipefy and Timing - APIANT.ai"
description: "When \"Done Card\" fires in Pipefy, your agent runs \"Create Project\" in Timing, or \"New Project\" in Timing to \"Create Record\" in Pipefy."
canonical: "https://apiant.ai/connect/pipefy-to-timing"
---

# Connect Pipefy and Timing

When **Done Card** fires in [Pipefy](https://apiant.ai/connections/pipefy), your agent runs **Create Project** in [Timing](https://apiant.ai/connections/timing), or **New Project** in Timing to **Create Record** in Pipefy. Describe the whole flow and it is built, tested on every scenario and kept running.

Pipefy **6** triggers Pipefy **11** actions Timing **4** triggers Timing **21** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Pipefy and Timing to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Timing records where your hours actually go, while Pipefy runs the work itself in pipes and tables. Connecting them means a card moving in Pipefy can start or stop a Timing timer, and finished Timing entries can land on the card or table record they belong to, so billing status and hours sit next to the work.

Example flows

## What Pipefy and Timing can do together

### From Pipefy to Timing

- When **Done Card** in Pipefy then **Create Project** in Timing
- When **Moved Card** in Pipefy then **Update Project** in Timing

### From Timing to Pipefy

- When **New Project** in Timing then **Create Record** in Pipefy
- When **New Time Entry** in Timing then **Update Database Record** in Pipefy

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 Pipefy and Timing

## Triggers and actions 10 triggers · 32 actions

- Trigger

**Done Card**

Triggers when a card is done.

- Trigger

**Moved Card**

Triggers when a card is moved.

- Trigger

**New Card**

Triggers when a new card is created.

- Trigger

**New Database Record**

Triggers when a new record is created.

- Trigger

**Updated Card Field**

Triggers when a card field is updated.

- Trigger

**Updated Record Field**

Triggers when a record field is updated.

- Action

**Create Card**

Creates a card in a Pipefy pipe, filling in its start form fields.

- Action

**Create Record**

Creates a new table record.

- Action

**Delete Card**

Permanently deletes a card from its pipe.

- Action

**Delete Database Record**

Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.

- Action

**Find Card**

Returns the cards in a pipe whose chosen field matches the specified value.

- Action

**Find Database Records**

Find a database records by title.

- Action

**Get Card**

Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.

- Action

**Get Database Record**

Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.

- Action

**Move Card**

Moves a Pipefy card to another phase of its pipe.

- Action

**Update Card Field**

Sets a new value on one field of an existing Pipefy card.

- Action

**Update Database Record**

Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.

- Trigger

**New Project**

Triggered when a new project is created in Timing.

- Trigger

**New Team**

Triggered when you are added to a new team in Timing.

- Trigger

**New Time Entry**

Triggered when a new time entry is logged in Timing.

- Trigger

**New Timer Started and Running**

Triggered when a new timer is started and is still running in Timing.

- Action

**Batch Update Time Entries**

Updates several Timing time entries at once — moves them to a project, retitles them, sets notes, billing status or custom fields. Anything left blank is left untouched on the entries.

- Action

**Create Project**

Creates a new project in Timing, optionally under a parent project, and returns the created project.

- Action

**Create Time Entry**

Logs a finished block of work in Timing between a start and end time, optionally against a project, and returns the created time entry.

- Action

**Delete Project**

Deletes a project in Timing, along with all of its child projects.

- Action

**Delete Time Entry**

Deletes a time entry in Timing.

- Action

**Find Project**

Searches your Timing projects by title and returns the first match, plus the full list of matches.

- Action

**Find Team**

Finds a team you belong to in Timing by its name and returns the first match, plus every team whose name matched.

- Action

**Generate Report**

Builds a time report in Timing over a date range, broken down by the columns you choose, and returns the report rows with their durations.

- Action

**Get Activity Hierarchy**

Returns a readable breakdown of what you worked on in Timing over a date range, as tab-indented text grouped by project and app with durations.

- Action

**List Projects**

Returns the projects you can see in Timing, optionally filtered by title, team, or hiding archived ones.

- Action

**List Team Members**

Returns the active members of a Timing team. People with a pending invitation are not included.

- Action

**List Teams**

Returns all the Timing teams you are a member of.

- Action

**List Time Entries**

Returns your Timing time entries, optionally narrowed by date range, project, team member, search text or billing status.

- Action

**Show Latest Time Entry**

Returns your most recent time entry in Timing.

- Action

**Show Project**

Returns a single Timing project with its colour, notes, billing default, parent and child projects.

- Action

**Show Running Timer**

Returns the timer that is currently running in Timing. Errors with a not-found if no timer is running.

- Action

**Show Time Entry**

Returns a single Timing time entry with its times, duration, project, notes and billing status.

- Action

**Start Timer**

Starts a running timer in Timing, stopping any timer that is already running, and returns the new entry.

- Action

**Stop Timer**

Stops the timer that is currently running in Timing and returns the finished time entry.

- Action

**Update Project**

Updates a Timing project's name, colour, notes, archive state or billing default. Anything left blank keeps its current value.

- Action

**Update Time Entry**

Updates a Timing time entry — its times, project, title, notes or billing status. Anything left blank keeps its current value.

## Each app on its own

- [ **Pipefy** The easy button for processes and workflows Easily organize and run all your processes in one place, leaving...](https://apiant.ai/connections/pipefy)
- [ **Timing** Timing is an automatic time tracking app for macOS.](https://apiant.ai/connections/timing)

Reviews

## What our customers say

## More from Pipefy

- [ **Pipefy to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/pipefy-to-trello)
- [ **Pipefy to Hyrule Compendium** Hyrule Compendium is an open-source REST service exposing data on every interactive item in The Legend of...](https://apiant.ai/connect/pipefy-to-hyrule-compendium)
- [ **Pipefy to Spaceflight News** Spaceflight News API aggregates news coverage of spaceflight and the space industry from many publishers.](https://apiant.ai/connect/pipefy-to-spaceflight-news)
- [ **Pipefy to SparrowDesk** SparrowDesk is an AI-first helpdesk that unifies customer support across email & chat while automating...](https://apiant.ai/connect/pipefy-to-sparrowdesk)
- [ **Pipefy to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pipefy-to-salesforce)
- [ **Pipefy to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/pipefy-to-slack)

## More into Timing

- [ **Favro to Timing** Plan a wedding, build an award winning video game or even send a rocket into space.](https://apiant.ai/connect/favro-to-timing)
- [ **HubSpot to Timing** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-timing)
- [ **Salesforce to Timing** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-timing)
- [ **Slack to Timing** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-timing)
- [ **Gmail to Timing** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-timing)
- [ **Google Calendar to Timing** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-timing)

Questions

## Pipefy and Timing, answered

###

### Can a Pipefy card start tracking time in Timing on its own?

Yes. The Moved Card and New Card triggers in Pipefy can run Start Timer in Timing, and you can use Find Project first so the timer is logged against the right Timing project. The agent tests every scenario before it goes live.

###

### What happens to a Timing entry once the work is billed?

A new time entry in Timing can create or update a card in Pipefy with the duration and notes, and Update Time Entry can set the billing status back in Timing. Both directions rest on listed triggers and actions only.

###

### What can start an automation from Pipefy?

Any of Pipefy's 6 triggers in the catalog, including Done Card, Moved Card, New Database Record and New Card. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Timing when something happens in Pipefy?

Any of Timing's 21 actions, including Create Project, Stop Timer, Create Time Entry and Update Project. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Timing to Pipefy?

Yes. When something happens in Timing, your agent can act in Pipefy too. This page covers both directions: Timing's triggers and Pipefy's actions are listed here as well.

###

### Do I have to build a connector for Pipefy or Timing?

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 Pipefy and Timing 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.
