Actions72
- Pages Actions
- Posts Actions
- Groups Actions
- Events Actions
- Insights Actions
- Marketing/Ads Actions
- Videos Actions
- Messaging Actions
- Shop/Catalog Actions
- Lead Ads Actions
- Webhooks Actions
Messaging → Set Persistent Menu
AI-generatedOverview
The node provides an enhanced integration with the Facebook Graph API, enabling a wide range of operations across multiple Facebook resources. Specifically for the Messaging resource and the Set Persistent Menu operation, the node allows users to configure the persistent menu of a Facebook Page's Messenger experience. This menu is a customizable set of options that appear in the chat interface, helping users navigate or interact with the page more easily.
This operation is beneficial for businesses or developers who want to improve user engagement on their Facebook Pages by providing quick access to important actions or information directly within Messenger. For example, a business could set up a persistent menu with options like "View Products," "Contact Support," or "FAQs" to streamline customer interactions.
Properties
| Name | Meaning |
|---|---|
| Page ID | The unique identifier of the Facebook Page for which the persistent menu will be set. |
Output
The output of this operation is a JSON object representing the response from the Facebook API after attempting to set the persistent menu. It typically contains confirmation details or error messages related to the update of the Messenger persistent menu configuration.
The node does not output binary data for this operation.
Dependencies
- Requires a valid API key credential for the external N8N Tools API service used for validation.
- Requires Facebook API credentials (OAuth2 or API token) to authenticate requests to the Facebook Graph API.
- The node internally uses a helper class to interact with Facebook's API endpoints.
- Proper permissions/scopes must be granted to the Facebook app to modify Messenger settings on the specified Page.
Troubleshooting
- Invalid subscription or API key: If the node throws an error about invalid subscription or API key, verify that the API key credential for the external validation service is correct and active.
- Facebook permission errors: Errors related to insufficient permissions usually mean the Facebook access token lacks required scopes or the Page role is insufficient. Ensure the token has
pages_messagingor equivalent permissions. - Incorrect Page ID: Providing an invalid or unauthorized Page ID will cause failures. Double-check the Page ID and ensure the authenticated user has admin rights on that Page.
- Network or API errors: Temporary network issues or Facebook API rate limits can cause failures. Retry after some time or check Facebook's API status.