SmsNotification
SMS template (app/smses): a text message sent with the sms_send mutation
type SmsNotification implements AdminSharedAttributesInterface {
content: String
created_at: JSONDate!
delay_by: String
form_configurations: [FormConfiguration!]
forms: [Form!]
id: ID!
manually_managed: Boolean
metadata: HashObject
name: String!
physical_file_path: String
to: String!
trigger_condition: String
updated_at: JSONDate!
}
Fields
content (String)
Liquid that evaluates to the text of the message. The data argument of sms_send is available in the data variable
created_at (JSONDate)
Timestamp of when the object was created, set automatically by the system
delay_by (String)
Number of minutes sms_send waits before sending the SMS, given as a plain number, for example 60. Defaults to 0
form_configurations (FormConfiguration)
Deprecated, legacy forms that send this SMS
forms (Form)
Deprecated, legacy forms that send this SMS
id (ID)
Unique identifier of the object
manually_managed (Boolean)
When true, the resource is managed outside of files: pos-cli deploy and sync never overwrite or delete it
metadata (HashObject)
Free-form data attached to the resource with the metadata key of its file (or the metadata argument of an admin mutation)
name (String)
Name of the SMS, used to send it with the sms_send mutation
physical_file_path (String)
Path of the file the resource comes from, relative to the app directory, for
example views/pages/index.liquid or
modules/my_module/public/views/partials/header.liquid. Identifies the resource
in deploy, sync and admin mutations
to (String)
Liquid that evaluates to the recipient mobile number with the country code,
for example +1 541 754 3010. The to_mobile_number filter helps to build it
trigger_condition (String)
Liquid that evaluates to true (or t) when the SMS should be sent; any other result skips it. Defaults to true
updated_at (JSONDate)
Timestamp of when the object was last updated, set automatically by the system
Interfaces
AdminSharedAttributesInterface
Attributes shared by resources that can be deployed from files with pos-cli
(pages, partials, layouts, notifications, authorization policies, schemas, assets etc.)