In basic settings, there are two templates you can configure for each public post type that has an enabled user interface. Each post type is enabled individually for each template.

The basic templates are for publishing a new post, and for updating an edited post. By default, update when a Post is enabled only for the ‘post’ post type.

Screenshot of the basic status update settings fields.

These templates are only the defaults – this is what will be used to structure an update if no other customizations are made, such as a user or term template or a custom format inserted in the editor.

If this value is blank, then no status update will be sent unless a custom text is provided.

Template Tags

The template tags available are documented at the bottom of the Basic settings screen.

Screenshot of the list of template tags.
  • #title#: The title of the post.
  • #blog#: The name of your website.
  • #post#: An excerpt of your post content.
  • #category#: The name of the first selected category for the post.
  • #cat_desc#: The description field from the first selected category.
  • #date#: The post date.
  • #modified#: The modified date.
  • #url#: The shortened post URL. (Or full post URL, if there is no shortener used.)
  • #longurl#: The full post URL.
  • #author#: The author. @referenced account if available, otherwise, display name.
  • #displayname#: The author’s display name.
  • #account#: An X.com @ reference for the main site account or author, depending on user settings.
  • #@#: An X.com @ reference for the current author or blank.
  • #tags#: The post tags as hashtags.
  • #reference#: Used only in paired posting; @reference to the other account simultaneously posting.

Custom Template Tags

You can create on-the-fly custom template tags for post meta fields or user meta fields.

A pattern with double square brackets, e.g. [[custom_field]] will pull the stored value of a custom meta field from the post.

A pattern with double curly braces, e.g. {{user_meta}} will pull the stored value of a user meta custom field.

Many meta fields are not stored as strings, and can’t be sent directly to a service. In this case, you may need custom handling to format a custom template tag.