> ## Documentation Index
> Fetch the complete documentation index at: https://fliqr.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# System fields in Flows
> Reference of Fliqr AI system fields you can use as {{placeholders}} in Flows — contact, account, ads, commerce, and channel-specific values.
System fields are values Fliqr AI fills automatically. Use them as `{{field_name}}` in messages, conditions, External Requests, and integrations.
Not every system field appears in the Flow Builder suggestions list. You can still type `{{field_name}}` manually — if the field exists, it resolves at runtime.
## Contacts
| Field | Description |
| -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| `{{first_name}}` / `{{last_name}}` / `{{full_name}}` | Name from the channel profile when available |
| `{{email}}` / `{{phone}}` | Contact email and phone |
| `{{user_country}}` / `{{user_state}}` / `{{user_city}}` | Location fields when known |
| `{{gender}}` | Gender when provided by the channel |
| `{{locale}}` | Language locale (for example `en_US`) |
| `{{locale2}}` | Short language code (for example `en`) |
| `{{profile_pic}}` | Profile image URL |
| `{{timezone}}` | Offset (for example `+2`) |
| `{{timezone_name}}` | IANA name (for example `America/New_York`) |
| `{{user_id}}` | Fliqr contact ID (use with the API) |
| `{{subscribed_date}}` | When the contact was created |
| `{{inbox_link}}` | Link to this contact in the Fliqr Inbox |
| `{{fb_chat_link}}` | Direct link to the contact in Facebook Inbox |
| `{{me}}` | Link for the contact to view/delete their data (GDPR helper) |
| `{{user_code}}` | Contact code |
| `{{ig_user_name}}` | Instagram username |
| `{{ig_followers}}` | Instagram follower count |
| `{{ig_verified}}` | Instagram verification status |
| `{{ig_follow_business}}` | Whether the user follows the business |
| `{{ig_business_follow_user}}` | Whether the business follows the user |
| `{{last_btt_title}}` | Title of the last button the contact tapped |
| `{{last_interaction}}` | Last interaction timestamp |
| `{{last_order}}` | Last order reference when available |
| `{{last_seen}}` | Last time the contact read a message |
| `{{last_outbound_message_at}}` | Last time the business messaged the contact |
| `{{last_input}}` | Last text, image, video, audio, file, or voice message from the user |
| `{{last_input_type}}` | `text`, `image`, `video`, `audio`, `file`, or `reel` |
| `{{consecutive_failed_reply}}` | Count of consecutive failed replies |
| `{{last_ref}}` | Last entry-point / ref link the user clicked |
| `{{user_channel}}` | Primary channel for the contact |
| `{{user_hash}}` | Contact hash |
| `{{user_tags}}` | Names of all tags on the contact |
| `{{user_external_id}}` | External channel ID (for example Viber user id) |
| `{{user_source}}` | How the contact arrived (`Ads`, comment, Direct, Imported, API, Inbound Message, …) |
| `{{assigned_admin_name}}` / `{{assigned_admin_email}}` / `{{assigned_admin_id}}` | Assigned Inbox admin |
| `{{current_user_time}}` | Current time in the contact’s timezone context |
| `{{chat_history}}` | Last 50 messages |
| `{{chat_history_large}}` | Last 200 messages |
| `{{chat_history_details}}` | Last 50 messages including who sent each one |
| `{{chat_history_details_large}}` | Last 200 messages including who sent each one |
| `{{user_notes}}` / `{{last_user_note}}` | Inbox notes |
| `{{webchat}}` | Link to continue the conversation in website chat |
| `{{webchat_parent_url}}` | Page URL where the webchat widget is loaded |
## Account
| Field | Description |
| ----------------------------------------------------------- | ------------------------- |
| `{{account_id}}` / `{{account_name}}` / `{{account_image}}` | Workspace account details |
| `{{api_key}}` | Account API key |
Do not put `{{api_key}}` in messages contacts can see. Prefer server-side auth on [External Request](/docs/core-concepts/flows/external-requests).
## Ads and Lead Ads
| Field | Description |
| ------------------------------------------------- | ----------------------------------------- |
| `{{last_ad}}` | Last Facebook/Meta ad ID the user clicked |
| `{{last_ctwa}}` | Last Click-to-WhatsApp action ID |
| `{{last_ad_source_url}}` | Link to the ad |
| `{{last_ad_source_platform}}` | `Facebook` or `Instagram` |
| `{{last_lead_id}}` | Lead ID |
| `{{last_form_name}}` / `{{last_form_id}}` | Lead form name and ID |
| `{{last_ad_name}}` | Ad name |
| `{{last_campaign_name}}` / `{{last_campaign_id}}` | Campaign |
| `{{last_adset_name}}` / `{{last_adset_id}}` | Ad set |
| `{{last_adgroup_id}}` | Ad group ID |
## Facebook / Instagram comments and stories
| Field | Description |
| ------------------------------------------- | ---------------------------------------------------------------- |
| `{{last_commented_post_text}}` | Text of the post the contact commented on (useful in AI prompts) |
| `{{last_fb_comment}}` | Text of the last comment |
| `{{total_new_tagged}}` / `{{total_tagged}}` | Tag counts in the comment (Facebook) |
| `{{last_post_id}}` / `{{last_comment_id}}` | Post and comment IDs |
| `{{last_story_id}}` | Instagram story ID for story replies |
## Channel-specific
| Field | Channel | Description |
| ------------------------------------------ | --------- | ----------------------------------- |
| `{{page_user_name}}` | Messenger | Page username |
| `{{viber_bot_username}}` | Viber | Bot username |
| `{{last_call_recorded}}` | Voice | URL of the last recorded call |
| `{{last_latitude}}` / `{{last_longitude}}` | Location | Set when the user shares a location |
## Pipelines, booking, questionnaire
| Field | Description |
| ----------------------------------------------------------------------------------- | ------------------------------------------------- |
| `{{last_opportunity_id}}` | Last pipeline card/opportunity created or updated |
| `{{booking_date}}` / `{{booking_link}}` / `{{booking_id}}` / `{{booking_calendar}}` | Appointment booking values |
| `{{last_points}}` | Total points from the last questionnaire |
## E-commerce
| Field | Description |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| `{{cart_checkout_link}}` / `{{shop_link}}` | Cart and shop URLs |
| `{{cart_last_item_name}}` / `{{cart_last_item_quantity}}` / `{{cart_num_items}}` | Cart line summary |
| `{{cart_other_fees}}` / `{{cart_shipping_cost}}` / `{{cart_subtotal}}` / `{{cart_total}}` | Cart money fields |
| `{{cart_products}}` | Products currently in the cart |
| `{{money_symbol}}` | Currency symbol |
| `{{order_*}}` | Order totals, shipping, status, coupon, and IDs (`order_total`, `order_total_formatted`, …) |
| `{{product_name}}` / `{{product_quantity}}` / `{{product_id}}` | Product context for product triggers |
## Flow runtime and Inbox
| Field | Description |
| ---------------------------------------- | -------------------------------------------------------------------------------- |
| `{{last_step}}` / `{{current_step}}` | Step IDs (published Flows only) |
| `{{admin_name}}` / `{{admin_team_name}}` | Admin who sent a message/Flow from the Inbox |
| `{{last_error_log}}` | Details about the last error log entry |
| `{{last_input_failure}}` | Why Get User Data failed: `timeout`, `user_skipped`, or `invalid_input_attempts` |
## Field not in the picker?
If an integration UI (for example Google Sheets) does not list a system field:
1. Create a custom field.
2. Use **Set Custom Field** and set its value to `{{system_field}}`.
3. Map the custom field in the integration.
## Next
Custom fields, tags, and user input.
Pull values from JSON into custom fields.