Card


A card is a visual, detailed representation of an activity included on your pipe.

In order to illustrate how a card represents an activity in your processes, here are a few examples:

  • In a sales pipeline, each card represents a new potential customer moving through all the phases of your sales process. From prospecting to closing the sale, all the information you gather throughout the process is stored within the card.

  • In a purchase process, each card represents a request for an item to be purchased or a service to be hired.

Even though cards represent different things in different pipes, they're essentially pieces of information gathered to guide an activity.

Cards move laterally from left to right through the phases of your pipe. Your pipe will probably have a few phases for your cards to go through, therefore it’s normal to see different cards in different phases of your process simultaneously.

Object most used fields

View all object's fields

field : objectdescription
assignees: [User]Information about the assigned users
attachments: [Attachment]Information about the attached files
current_phase: PhaseInformation about the card current phase
done: BooleanWhether the card is done
id: IDThe card ID
pipe: PipeInformation about the pipe
title: StringThe card title
updated_at: DateTimeWhen the card was last updated

Boolean

Represents `true` or `false` values.

ID

Represents a unique identifier that is Base64 obfuscated. It is often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"VXNlci0xMA=="`) or integer (such as `4`) input value will be accepted as an ID.

String

Represents textual data as UTF-8 character sequences. This type is most often used by GraphQL to represent free-form human-readable text.

DateTime

An ISO‐8601 encoded UTC date time string (YYYY-MM-DD HH:MM:SS).