Everything in the box

One plan, no per-feature upsells. Here’s the full surface, grouped by what you’re trying to do.

Model the work

Pipes & phases

Every process is a pipe: an ordered set of phases a card moves through. Admins control which phase a card can transition to next, so the workflow can’t skip steps.

17 field types

Text, long text, email, phone, URL, number, currency, date, date and time, select, multi-select, checkbox, assignee, attachment, record reference, repeatable group and formula.

Conditional fields

show-if rules hide or reveal fields based on other field values, so a card only ever asks for what’s relevant.

Formula fields

Template-driven computed fields with built-in functions and field references. Circular dependencies are detected and rejected at definition time.

Keep it correct & on time

SLA tracking

Per-phase time limits plus a pipe-level expiry. Choose wall-clock, weekdays-only or business-hours calendars, with holiday support. Cards display how late they are.

Validation rules

Field-level constraints (length, range, date bounds, file size/MIME) and cross-field rules: require-one-of, exactly-one-of, date comparison, conditional-required, composite uniqueness.

Attachments

Upload files to object storage with min/max count, size limits and MIME-type filtering enforced on the card.

See & share

Saved views

Filters, sorted columns, grouping and aggregations (sum, average, count, percent-filled). Relative-date filters such as overdue, last 30 days, next 7 days.

CSV export

Export any view to CSV. Included, like everything else.

Comments

Threaded discussion on each card, with edit and delete.

Roles & access

Team roles (owner, admin, member, guest) cascade into pipes, with per-pipe admin / member / viewer overrides. Visibility and editability are role-aware.

Connect & automate

Webhooks

Signed deliveries for card.created/updated/moved/deleted, card.late, card.expired, comment events and pipe lifecycle. Six retry attempts with exponential backoff; endpoints flagged broken after repeated failures.

Zapier and Make

Connect your workspace to Zapier or Make and a card moving between phases can drive thousands of other apps, with no code and no API keys to copy around. Cards arrive with their real labels rather than internal ids, so a step reads "Phase = Awaiting approval" and not an opaque reference.

Action buttons

Put a button on any card and point it at your own systems. Sending the confirmation, raising the invoice, scheduling the follow-up: one press each, with a short undo window before anything leaves. Deliveries are signed, and failures retry.

Generous API

Full read and write access to your data, with thousands of calls per editor included every month. Build your own tooling on top of your pipes.

Read the docs →

Pipefy importer

Bring existing pipes across. Imports run in the background and are owner-only, so a large migration never blocks the team.

Start running your work through Track40

30 days free, no card required. After that, one plan with everything included, at US$12 per editor per month. Your data stays put.