DemandFlow Support Centre

POST: Social post

ReferenceEntity Reference16/04/2026Updated 16/04/2026
The POST entity represents a social media post with content editor, scheduling, channel selection, status tracking, and image editor.

POST: Social post

The POST entity represents a social media post with content editor, scheduling, channel selection, status tracking, and image editor.

Default definition. This article describes the default POST definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches POST.

Entity properties

PropertyValue
Entity codePOST
Display nameSocial post
PluralSocial posts
Level800

Use cases

Social media management entity for scheduled posts. Two-column layout: left (25%) has post content using termeditor field type (with banned terms, substitution terms, grammar checking), status (scheduled/processing/posted/failed), creator (singleuser readonly), channel (objectLookup to SOCIALCHANNEL), and schedule time (datetime); right (75%) has imagesEditor row type for visual content. Uses comboKeyFilter SUB|USER for user-scoped data, combo2 for STATUS filtering, comboFilterAdd for combined filtering, and forceNew flag. Provides a social media scheduling and content management workflow.

Fields

General

FieldTypeRequiredNotes
nametermeditorYesContent .
statusenumStatus. Valid ids: scheduled (Scheduled), processing (Processing), posted (Posted), failed (Failed).
ownerIdreference → userCreator. Read-only.
socialChannelreference → SOCIALCHANNELYesChannel.
posttimedatetimeYesSchedule time.
languageenumLanguage. Valid ids: en_GB (English (UK)), en_US (English (US)), de_DE (German (Germany)), de_AT (German (Austria)), de_CH (German (Switzerland)), fr_FR (French (France)), fr_BE (French (Belgium)), fr_CH (French (Switzerland)), fr_CA (French (Canada)), es_ES (Spanish (Spain)), es_MX (Spanish (Mexico)), es_AR (Spanish (Argentina)), it_IT (Italian (Italy)), pt_PT (Portuguese (Portugal)), pt_BR (Portuguese (Brazil)), nl_NL (Dutch (Netherlands)), nl_BE (Dutch (Belgium)), pl_PL (Polish), cs_CZ (Czech), sk_SK (Slovak), hu_HU (Hungarian), ro_RO (Romanian), bg_BG (Bulgarian), hr_HR (Croatian), sl_SI (Slovenian), sr_RS (Serbian), uk_UA (Ukrainian), ru_RU (Russian), el_GR (Greek), tr_TR (Turkish), da_DK (Danish), sv_SE (Swedish), nb_NO (Norwegian (Bokmal)), fi_FI (Finnish), zh_CN (Chinese (Simplified)), zh_TW (Chinese (Traditional)), ja_JP (Japanese), ko_KR (Korean), ar_SA (Arabic (Saudi Arabia)), hi_IN (Hindi), th_TH (Thai), vi_VN (Vietnamese), id_ID (Indonesian).
viewCountnumberViews. Read-only.
likeCountnumberLikes. Read-only.
commentCountnumberComments. Read-only.
shareCountnumberShares. Read-only.

Additional panels

  • imagesEditor panel.

Relationships

  • Lookups: socialChannel points at SOCIALCHANNEL record.

Creating a Social post via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "POST",
  "level":    800,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "",
  "socialChannel": "",
  "posttime": "2026-01-01T12:00:00Z"
}

Listing POST records

# All social posts in your tenant
GET /v1/entities/POST/SUB

See also

postsocial postsocial postssocial

Was this article helpful?

← Back to Knowledge Base