Facebook Messenger
With Facebook Messenger apps in Make, you can watch and send messages, send an action, upload an attachment, or get a sender in your Facebook Messenger account.
To use the Facebook Messenger modules, you must have a Facebook Developer account. You can create an account at https://developers.facebook.com/.
Refer to the Facebook API documentation for a list of available endpoints.
To establish the connection with a Trigger module, you must create a webhook with a Verify Token and add this information into your app in the Facebook Developer Portal.
To establish the connection with an Action module, you must generate an Access Token in your app in the Facebook Developer Portal.
The following example, How to create a bot and connect it to Facebook Messenger and Make, describes both processes in a possible scenario.
The Facebook Messenger app supports a bot's connection that can then be used to receive and send messages on behalf of a designated page that belongs to the bot.

- Choose Other as the use case for your app and click Next.
- Add your App name and Contact email, then click Create app.
- Once you create the app, you will be shown the Product Setup page. Select Messenger and click Set up.
- Scroll down until you see the Configure webhooks section and click Configure. Click the Add Callback URL button. You will be prompted to fill in the Edit Callback URL and Verify Token fields. The required values can be generated through Make.
Open a new tab and log into your Make account, and create a new Make.
- Clicking the save button will generate a URL for your webhook. Copy this URL to your clipboard.
Go back to the Edit Callback URL dialog in your Facebook Developer account. In the Callback URL field, enter the URL from your clipboard, and in the Verify token field, enter the same token that you entered in step 6. Click Verify and Saveto save the dialog.
- Under Generate Access Tokens, click Connect. In the dialog box that opens, choose the pages you want your app to access and click Continue and Save.
- Click Got it. You will return to the Generate access tokens section.
For your chosen page, click Generate.
In the Token Generated dialog box, confirm that you understand and then copy the token to your clipboard.
- To create a connection between Make and Facebook messenger, add a Send a Message module and click Create a connection. Enter the access token from the previous step into the Access Token field and click Save.
- Map the Sender ID to the Page Scoped User ID field and specify the Message Text in the Send a Message module.
- Set up the Send a Message module and run the Make to test your bot.

To test the bot application, you need to:
- Send a test message to the test page (created by the app administrator) when logged in as a test developer to trigger the Watch messages module in your Make.
To test your application before publishing it, you need to set up roles for developers who will test it. For non-developer accounts, the app does not respond until it is officially released.
You need two Facebook accounts to test the app:
- The first account that creates the app (bot) is the Facebook page owner.
- The second account that is set up as a verified Facebook developer account (How do I verify my developer account on Facebook?) and sends the test message to the Facebook page.
Log in with your second developer (test) account and confirm the request on the https://developers.facebook.com/requests page.
After the test developer account is set, run your Make Make, log in to Facebook (with your test developer account credentials), and open the public page you want to test the bot with.
Send the message to the page to test your bot.

Conditions that have to be met while testing:
- The Facebook account you write a message to the Facebook page must be set as the developer of the app.
- The bot cannot send the message first (anti-spam policy). The app test user must initiate the conversation with the developer role, your second account.
For more information on how to set up the roles, see the official Facebook documentation.