FlowRunner
PricingContact
Theme
Start Free

TimeCamp Planner

Project Management

TimeCamp Planner, formerly HeySpace, pairs kanban boards with team chat in one workspace. Agents create and move cards, manage lists, checklists, estimates and tags, post chat messages and handle people and groups across spaces.

Verified 106 actions API key available
TimeCamp Planner website Platform Documentation Capability data verified 2026-08-18
A client request arrives by email or form and needs to become tracked work
Agent reads the request and resolves the space and list it belongs in
List Cards looks for an existing card covering the same request before creating another
Create Card opens the card, and Assign Person To Card puts an owner on it
Create Checklist Item adds the steps this kind of request always needs
Send Message posts the request's own words into the card's conversation
A person confirms before any space is deleted rather than archived

What This Integration Enables

TimeCamp Planner, the product formerly sold as HeySpace, puts kanban boards and team chat in the same workspace. That is the whole argument for it: the card and the conversation about the card are not in two systems that need to be reconciled, because a message can be posted into a space's chat or onto the card itself. FlowRunner agents work with that grain. They create spaces, lists and cards, assign people and set their card roles, manage checklists, estimates and tags, and post the context that would otherwise live in somebody's inbox directly onto the work it describes.

Two of the platform's conventions are worth knowing before building here. Records are created at an identifier the caller chooses rather than one the server hands back, so every create operation mints one for you and returns it, which means a flow always knows the identifier of what it just made. And the vocabulary is layered: workspace roles, space roles and card roles are three separate sets of words that do not overlap, so an agent resolving who may do what reads the right one rather than assuming. Time tracking itself lives in TimeCamp rather than in Planner, which is why a card's time entries are empty until that connection exists.

What an agent should not do here is tidy. Archiving and deleting are the same call with a different status, so the destructive option is no harder to reach than the safe one, which is exactly the situation FlowRunner's human-in-the-loop discipline exists for: the agent does the reading, the counting and the archiving, and a person decides when something stops existing.

Without FlowRunner

Two places per topic The card lives in one tool and the conversation about it in another, and they drift apart
Guest access unaudited Nobody is quite sure which outside people can still see which spaces
Cleanup by deletion A finished project gets deleted because archiving it was one more click

With FlowRunner

Card and conversation together The request, its checklist and the discussion that resolved it sit on one object
Access answerable on demand Space memberships and guest placements are read on a schedule and reported
Archive as the default Finished spaces are archived and restorable, and deletion is a decision somebody makes

Use Case Scenarios

  • Requests arrive as cards with the conversation attached

    An inbound request reaches the team through Gmail or a form in Typeform. The agent resolves the destination with Get Workspace Overview, checks List Cards so a repeat request does not become a second card, and calls Create Card in the intake list. Assign Person To Card puts an owner on it with the right card role, Create Checklist Item adds the standard steps for this request type, and Send Message posts the requester's own words into the card so the owner reads the original rather than a summary of it. Attach Tag To Card marks the client, and the card is ready before anybody opens the tool.

  • An access review that runs itself

    Guests in TimeCamp Planner see only the spaces they are placed in, which makes outside access easy to grant and easy to forget. On a schedule, the agent reads List Guests In Spaces alongside List Space Memberships and compares the result against the client list in the CRM. Guests attached to engagements that closed months ago get collected into a report for the workspace owner, along with the spaces each one can still see. Where the owner confirms, Remove Guest From All Spaces ends the access in one call. The review happens because it is scheduled, not because somebody remembered.

  • Closing a project without losing it

    When an engagement ends, the agent walks the space: Complete Card on the work that finished, Archive List for the columns that are done, and a summary posted into the space chat naming what shipped and what moved elsewhere. Then Archive Space puts the whole space away, out of the sidebar with everything inside it intact and restorable. Nothing is deleted, because the account team will ask about this engagement again in six months and the answer should still exist.

Human-in-Loop Highlight

Delete Space is the operation that deserves a person, and the reason is that it does not look dangerous from the outside. In TimeCamp Planner there is no separate delete route for a space: archiving, restoring and deleting are the same call with a different status. So deletion succeeds as quietly as archiving does, with no confirmation step, no different response shape and nothing to distinguish the two in a log except the value that was sent. Everything inside the space goes with it: lists, cards, checklists, estimates and the entire chat history of the project. So a cleanup agent never issues that call on its own. It posts to the workspace owner: "The Brightline Rebrand space has had no activity for 94 days. It holds 61 cards, 3 lists and 480 chat messages, and 2 guests from the client still have access. Archive it, which keeps everything and is reversible, or delete it, which is not?" The owner picks. Archiving is the answer the agent proposes; deleting is an answer only a person can give.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

106 actions

Workspace

4
  • List Workspaces Returns the workspaces the token's owner belongs to. Every other operation is scoped to one, so this is where a flow finds its identifier.
  • Get Current User Returns the person the API token belongs to.
  • Get Workspace Overview Returns the workspace's spaces, lists and people in one answer. The same load the app itself performs on start, and the cheapest way to see everything at once.
  • Update Workspace Changes the workspace's own record, such as its name.

People and Access

13
  • List People Returns everyone in the workspace with the role each one holds.
  • List Space Memberships Returns who belongs to which space across the whole workspace, which answers what a person can see without asking space by space.
  • List Guests In Spaces Returns the guests placed in each space. The list to read when auditing outside access.
  • Invite Person Invites somebody to the workspace by email address.
  • Invite Guests Invites one or more people as guests and places them in the spaces you name. A guest sees nothing outside those spaces.
  • Resend Invitation Sends the workspace invitation again to somebody who has not accepted it.
  • Generate Invitation Link Returns a link that lets somebody join without waiting for an email to arrive.
  • Set Person Role Changes what somebody may do across the whole workspace.
  • Deactivate Person Suspends access without deleting the person, so their work stays attributed to them. The reversible way to offboard.
  • Reactivate Person Restores access for somebody who was suspended.
  • Remove Guest From All Spaces Takes a guest out of every space at once, which is the quickest way to end outside access.
  • List Integrations Returns the integrations enabled on the workspace.
  • Get Schedule Returns the workspace's schedule view: who is working on what over time.

Groups

7
  • List Groups Returns the workspace's groups, the named sets of people a space can be shared with in one step.
  • List Group Members Returns who belongs to which group across the workspace.
  • Create Group Creates a group of people that can then be added to spaces as a unit.
  • Update Group Renames a group.
  • Delete Group Deletes a group. The people in it keep their own access.
  • Add Person To Group Puts somebody into a group.
  • Remove Person From Group Takes somebody out of a group.

Spaces

17
  • Get Space Returns one space with its people, followers and settings. A space is what the API itself calls a project.
  • Create Space Creates the container that holds lists, cards and a chat, at an identifier minted for you and returned with the result.
  • Update Space Changes a space. Only the fields filled in are sent, so anything left empty keeps its current value.
  • Archive Space Archives a space. It leaves the sidebar and keeps everything inside it, and restoring brings it back.
  • Restore Space Brings an archived space back into the sidebar.
  • Delete Space Deletes a space and everything in it. The same call as archiving with a different status, so it succeeds quietly. The operation this page's human gate exists for.
  • Copy Space Copies a space with its lists and cards under a new name. The fast path for a repeatable engagement shape.
  • List Archived Spaces Returns the spaces no longer in the sidebar.
  • Add Person To Space Adds somebody to a space and says what they may do in it.
  • Remove Person From Space Takes somebody out of a space. Their cards stay where they are.
  • Add Space Follower Makes somebody follow a space, so they are notified about it without being a member.
  • Remove Space Follower Stops somebody following a space.
  • List Space Files Returns the files attached anywhere inside a space.
  • Attach File To Space Attaches a file that already exists in the workspace to a space.
  • Get Space Settings Returns the token owner's own settings for a space, such as how they are notified about it.
  • Set Space Settings Replaces the token owner's own settings for a space.
  • Mark Space Visited Records that the token owner has looked at a space, which clears its unread badge.

Lists

10
  • List Space Lists Returns a space's lists, which are the columns cards sit in.
  • List Space Card Order Returns the order cards sit in within each list. Read it before a move, to work out the position to give a card.
  • Create List Creates a list inside a space, at an identifier minted for you.
  • Update List Changes a list. Filling in the space moves it to another one.
  • Archive List Archives a list or brings it back. The cards go with it, so this is how a finished column is put away.
  • Copy List Copies a list together with its cards.
  • Move All Cards Moves every card out of one list into another, leaving the first empty. A wide write worth reviewing before it runs on a shared board.
  • List Cards Returns the cards in a list. The duplicate check before anything is created.
  • Add List Follower Makes somebody follow a list, so they hear about every card added to it.
  • Remove List Follower Stops somebody following a list.

Cards

20
  • Get Card Returns one card with its people, tags, followers and checklist. A card is what the API itself calls a task.
  • Create Card Creates a card in a list, at an identifier minted for you and returned with the result.
  • Update Card Changes a card. Only the fields filled in are sent.
  • Complete Card Marks a card finished and moves its progress to full at the same time, because a card left part way still reads as part done.
  • Reopen Card Marks a finished card active again and puts its progress back to the start.
  • Archive Card Archives a card or brings it back. An archived card leaves the board without being deleted.
  • Move Card Moves a card to another list and optionally to a position within it.
  • Copy Card Copies a card under a new name.
  • Ping Card Nudges everyone on a card, which is how the product asks for an update without writing a message.
  • Assign Person To Card Puts somebody on a card. Card roles are their own vocabulary and are not the space roles of the same name.
  • Set Card Person Role Changes what part somebody already on a card plays.
  • Remove Person From Card Takes somebody off a card.
  • Add Card Follower Makes somebody follow a card without giving them work on it.
  • Remove Card Follower Stops somebody following a card.
  • Attach Tag To Card Puts an existing tag on a card.
  • Detach Tag From Card Takes a tag off a card. The tag itself stays in the workspace.
  • Attach File To Card Attaches a file that already exists in the workspace to a card.
  • Remove File From Card Takes a file off a card.
  • List Recent Cards Returns the cards somebody visited most recently, newest first.
  • Mark Card Visited Records that somebody has looked at a card, which clears its unread badge for them.

Checklists

6
  • Get Card Checklist Returns a card's checklist items.
  • Create Checklist Item Adds an item to a card's checklist, at an identifier minted for you.
  • Update Checklist Item Changes a checklist item, including ticking it off.
  • Delete Checklist Item Removes an item from a card's checklist.
  • Assign Checklist Item Gives a checklist item to somebody. This route is addressed by the item rather than the card.
  • Unassign Checklist Item Takes a checklist item away from somebody.

Estimates and Time

6
  • Get Card Estimate Returns how long a card is estimated to take.
  • Create Card Estimate Estimates a card in minutes.
  • Update Card Estimate Changes a card's estimate as the work becomes clearer.
  • Delete Card Estimate Removes a card's estimate.
  • List Card Time Entries Returns the time already tracked against a card. Tracking lives in TimeCamp rather than Planner, so this is empty until that connection exists.
  • Add Time Entry Records time worked on a card, given either as a duration or as a start and an end.

Tags

4
  • List Tags Returns the workspace's tags, the labels that can be put on cards.
  • Create Tag Creates a tag in the workspace, at an identifier minted for you.
  • Update Tag Renames or recolors a tag. Every card carrying it changes with it.
  • Delete Tag Deletes a tag and takes it off every card carrying it.

Messages

6
  • Send Message Posts a message into a space's chat or onto a card. The operation that puts context where the work is rather than in an inbox.
  • Update Message Edits a message that has already been posted.
  • Delete Message Deletes a message.
  • Add Message Reaction Puts an emoji reaction on a message.
  • Remove Message Reaction Takes a reaction off a message.
  • Get Messages Metadata Returns how many messages a container holds and which are unread.

Notifications

5
  • List Unread Notifications Returns what the token owner has not read yet, across one workspace or all of them.
  • Mark Notification Read Marks one notification as read.
  • Mark All Notifications Read Clears the unread badge for a whole workspace, or only for the kinds named.
  • Archive Notifications Files away whole kinds of notification so they stop appearing in the notification center.
  • Update Notification Marks one notification read or archived by its own identifier.

Files

3
  • Authorize File Upload Asks TimeCamp Planner where to put a file and returns a signed upload address for whatever holds the bytes.
  • Register File Records a file that already sits at an address so it can be attached to a card or a space.
  • Delete File Deletes a file from the workspace, taking it off everything it was attached to.

Custom Fields

2
  • Get Custom Fields Returns the custom field values held against a space, a card, a person or the workspace.
  • Update Custom Fields Sets custom field values on any of those. Only the keys sent are touched.

User Status

3
  • List User Statuses Returns what everyone in the workspace has set as their status, such as away or in a meeting.
  • Set User Status Sets the token owner's own status in a workspace.
  • Clear User Status Removes the token owner's status in a workspace.

Frequently Asked Questions

What can FlowRunner do with TimeCamp Planner?

FlowRunner agents can run List Workspaces, Get Current User, and Get Workspace Overview in TimeCamp Planner, plus 103 more actions.

Does connecting TimeCamp Planner to FlowRunner require OAuth?

No. TimeCamp Planner connects to FlowRunner with an API key, no OAuth flow required.

Can TimeCamp Planner trigger a FlowRunner workflow automatically?

TimeCamp Planner doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with TimeCamp Planner

Free plan, no card required. Connect in minutes.