Skip to main content

Get Message Template

Get Message Template gets one WhatsApp message template by id, including its components, status and rejected_reason (why Meta rejected it).

It calls GET https://graph.facebook.com/v23.0/{templateId}.

The activity has four tabs: Configuration, Auth, Input and Output.

Configuration​

FieldRequiredDescription
NameOptionalName of the step, should be unique within this workflow.
DescriptionOptionalDescribe the purpose or function of this step.
Template IDOptionalTemplate id from List or Create Message Template. Globally unique, so no WABA ID is needed. Sent as the templateId path parameter; Meta needs it.
FieldsOptionalComma-separated template fields. Keep rejected_reason. Defaults to id,name,status,language,category,parameter_format,components,rejected_reason,quality_score. Sent as the fields query parameter.

Auth​

FieldRequiredDescription
Auth TypeOptionalOAuth 2, the only option. WhatsApp uses the Meta OAuth connection.
WhatsApp ConnectionOptionalThe WhatsApp resource, which needs the whatsapp_business_management scope.

Input​

This activity is built on the REST Client. It sends no request body. You can map pathParams.templateId from an earlier step here.

FieldRequiredData TypeDescription
TargetRequiredObjectThe HTTP request.

Output​

The activity returns an httpResponse object (status.code, status.message, headers, body). The response body carries:

FieldData TypeDescription
idStringTemplate id.
nameStringTemplate name.
statusStringAPPROVED, IN_APPEAL, PENDING, REJECTED, PENDING_DELETION, DELETED, DISABLED, PAUSED, LIMIT_EXCEEDED or ARCHIVED.
languageStringLanguage code, for example en_US.
categoryStringUTILITY, MARKETING or AUTHENTICATION.
parameter_formatStringNAMED or POSITIONAL.
components[]ArrayEach with type, format, text, buttons (type, text, url, phone_number) and example.
rejected_reasonStringNONE, ABUSIVE_CONTENT, CATEGORY_NOT_AVAILABLE, INCORRECT_CATEGORY, INVALID_FORMAT, PROMOTIONAL, SCAM or TAG_CONTENT_MISMATCH.
quality_scoreObjectscore and date.