--- title: Android slug: android image: https://make-cxp-documentation.ams3.cdn.digitaloceanspaces.com/apps-center-icons/PREVIEW_DEFAULT.png docTags: createdAt: 2025-02-03T13:28:22.759Z --- With the Android app in Make, you can manage events performed by your Android phone. # Requirements To use the Android app in Make, you must have an Android device (7.0 and higher) and the Make app for Android installed on your phone. :::hint{type="info"} As of the beginning of 2019, Google has [restricted applications](https://play.google.com/about/privacy-security-deception/permissions/) published on Google Play that gives access to: - SMS permissions - Call logs This app is also subject to these restrictions. To use the SMS module, [download and install the unrestricted version from the website](docId\:PxWbOaLdt85zNNxPAexuc) (not Google Play). ::: # Installation of the unrestricted Make app for Android To install the Android app with **no restrictions**: :::::WorkflowBlock :::WorkflowBlockItem Tap on the following download link, and download the APK file. **[Make app for Android](https://android.integromat.com/integromat.apk) (8.5 MB)** ::: ::::WorkflowBlockItem Open the downloaded `make.apk` file. :::hint{type="warning"} Some phones (typically Huawei devices) may detect a possible virus in the APK file. There might be various reasons for this to happen. Our investigation determined that we are most likely blacklisted by Huawei's antivirus system. Huawei devices, unlike other OEMs, pre-installed an antivirus into their system and uses [Virustotal API ](https://developers.virustotal.com/v3.0/reference)which may falsely detect Integromat's APK file as malware. All other OEMs use Google Play Protect anti-malware service where the Integromat app is verified. If you are in doubt whether the file contains suspicious software, scan your device using Google Play Protect: 1. Open the Google Play Store app. 2. At the top right, tap the profile icon. 3. Click **Play Protect**. 4. Click the **Scan** button to scan your device for malware and/or viruses. ::: :::: :::WorkflowBlockItem Switch the button to allow the Make app installation. ::: :::WorkflowBlockItem Install the application. ::: :::WorkflowBlockItem Open the installed application. ::: :::WorkflowBlockItem Scan the QR code and proceed to the application. ::: ::::: The application is now ready to use. :::hint{type="info"} All of your settings and scenarios made using the previously installed Make app from Google Play will remain untouched and functional in the new **non-restricted Make app for Android**. ::: # Installation of the restricted Make app for Android on Google Play You can still install the Make app for Android on [Google Play](https://play.google.com/store/apps/details?id=com.integromat.android\&raii=com.integromat.android\&pli=1). # Use the App The app is designed to run in the background and perform selected functions. On the main screen, you can switch between the following options: - **Events**: Contains a list of captured events that have not yet been sent to the server. The app synchronizes events automatically. The synchronization is performed in the shortest possible time interval supported by the operating system. While for Android devices, events are sent immediately, for iOS devices, it can take several hours to send events. The automatic synchronization also occurs every time you open the app. To start the synchronization manually, drag the list of events down. - **History**: Contains all events that have already been sent to the server and those that generated an error when being sent. By clicking on an event, you can view its details, including any errors that have possibly occurred. - **Buttons**: Buttons allow you to run a scenario by tapping the associated button on your Android device. - **Scanner**: Use the barcode or QR code scanner to scan respective codes and trigger the scenario. - **Settings**: Settings of the Make for Android app features. Modules are divided into two categories: **triggers** and **actions**. Triggers have the ability to listen to the connected device and start the scenario whenever the device generates a new event. Actions, on the other hand, create new items in the device. Select the desired trigger or action, and add it to your scenario. In the configuration window of the module, select the desired module and, where appropriate, set up other parameters. # Set Up the Make for Android App Before you start building a scenario using the Android app modules, you need to set up your Make for the Android app to allow the app access to your phone's corresponding functions. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/sDhYyM6MOyrVGRqrzTboi_image.png" size="58" width="912" height="1382" position="flex-start" alt="Make app settings screen" showCaption="false"} ## General Settings | **Field** | **Description** | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Synchronize events in the order they were created** | This option allows you to keep the synchronization order even if the scenario is not available. No new events are processed until the first event in the queue is processed. | | **Send photos only over WiFi** | When enabled, photos will be sent only when your device is connected to the Internet via WiFi. It prevents high data consumption when connected via the mobile data network. | | **Dark Mode** | You can switch the Make app for Android to Dark Mode or Light Mode.
Select one of the options:
- **Always light**: Switches the app to the Light Mode.
- **Always dark**: Switches the app to the Dark Mode.
- **Follow system**: The mode is selected according to your system settings. | ## QR / Barcode Scanner | **Field** | **Description** | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- | | **Same code scan delay** | Set the period when the same code is scanned again. | | **Default description** | Enter the description to be added to all scanned codes.

You must have descriptions enabled to use a default description. | ## Photos **Triggers** | **Field** | **Description** | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | **Send new photos to Make** | When enabled, every time a photo is taken, the app sends the photo to Make and then triggers the **New Photo** module. | **Actions** | **Field** | **Description** | | --------------------------------------------- | ------------------------------------------------------------------- | | **Allow Make to import photos to the device** | Enable this option to allow the use of the **Save a Photo** module. | | **Take photo** | Allows you to use the **Take a Photo** module. | ## GPS **Triggers** | **Field** | **Description** | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Track GPS location** | Allows you to use the **Watch location changes** module that triggers when the device changes location. Use the **Change** button to define the distance that has to be changed to trigger the event. | | **Entered/left area** | Activate this function to send information when the device enters and/or leaves the specified area to the **Watch entrances to/exits from a geofence area **module.

Please note that you must spend a couple of minutes outside/inside the geofence area to trigger this function. | ## WiFi **Triggers** | **Field** | **Description** | | --------------------------- | ------------------------------------------------------------------------------------------------------ | | **Wifi connected event** | Triggers the **WiFi connection** module in your scenario when the device connects to the WiFi network. | | **Wifi disconnected event** | Triggers the **WiFi disconnection** module when the device disconnects from the WiFi network. | **Actions** | **Field** | **Description** | | ---------------- | --------------------------------------------------------------- | | **Enable WiFi** | Allows you to use the **Enable Wifi** module in your scenario. | | **Disable WiFi** | Allows you to use the **Disable Wifi** module in your scenario. | ## Bluetooth **Triggers** | **Field** | **Description** | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Bluetooth enabled** | Triggers the **Watch Bluetooth activations** module in your scenario when Bluetooth is enabled on your device. | | **Bluetooth disabled** | Triggers the **Watch Bluetooth Deactivations** module in your scenario when Bluetooth is disabled on your device. | | **Device connected** | Triggers the **Watch connections from Bluetooth Devices** module in your scenario when your Bluetooth device connects to another device. | | **Device disconnected** | Triggers the **Watch Disconnections from Bluetooth Devices** module in your scenario when your Bluetooth device disconnects from another device. | **Actions** | **Field** | **Description** | | --------------------- | ------------------------------------------------------------------------------------------------------------------- | | **Enable bluetooth** | Allows you to use the **Enable Bluetooth **module in your scenario to turn on Bluetooth on your device. | | **Disable bluetooth** | Allows you to use the **Disable Bluetooth **module in your scenario to turn off Bluetooth on your device. | ## Calls Call functions (except **Change a Ring Mode**) are available for the [non-restricted Make for Android](docId\:PxWbOaLdt85zNNxPAexuc) app only. **Triggers** | **Field** | **Description** | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Incoming call** | Triggers the **Watch Incoming Calls** module in your scenario when your device registers an incoming call.

There is no phone number in the module output due to the changes in the Android policy starting from Android 11.0. | | **Incoming call ended** | Triggers the **Watch Completed Incoming Calls** module in your scenario when an incoming call is finished. | | **Outgoing call** | Triggers the **Watch Incoming Calls** module in your scenario when your device registers an incoming call.

There is no phone number in the module output due to the changes in the Android policy starting from Android 11.0. | | **Outgoing call ended** | Triggers the **Watch Completed Outgoing Calls** module in your scenario when an outgoing call is finished. | **Actions** | **Field** | **Description** | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Prepare phone call** | Allows you to use the **Prepare a phone call** module in your scenario to display the pre-defined phone number in the phone's dialer app. | | **Make Call** | This function allows you to use the **Make a Call **module in your scenario to dial the phone number specified in the **Make a Call** module. | | **Change ringmode** | This function allows you to use the **Change a Ring Mode **module in your scenario to switch the ring mode between **silent**, **vibration**, and **loud **ring modes. | ## SMS :::hint{type="warning"} To use the SMS functions, you must install the [unrestricted Make app for Android.](docId\:PxWbOaLdt85zNNxPAexuc) These functions **will not work** if you are using the app downloaded from Google Play. Additionally, you must enable SMS in the mobile settings of the [unrestricted app](docId\:PxWbOaLdt85zNNxPAexuc). ::: **Triggers** | **Field** | **Description** | | -------------------- | ---------------------------------------------------------------------------------------------- | | **New SMS received** | Triggers the **Watch Text Messages** module in your scenario when your device receives an SMS. | | **New SMS sent** | Triggers the **Sent SMS** module in your scenario when your device sends an SMS. | **Actions** | **Field** | **Description** | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Send SMS ** | Allows you to use the **Send Text Message **module in your scenario to send a text message. The recipient number and the text message content must be entered into the respective fields of the **Send Text Message** module | ## Web **Actions** | **Field** | **Description** | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Open websites** | This function allows you to use the **Open a Web Browser **module in your scenario to open a specified URL address in a web browser on your device. | | **Close websites** | This function allows you to use the **Close a Web Browser **module in your scenario to close a web browser on your device. | # Run a scenario using the Make for Android App You can run the scenario by tapping the button created in the Android app. The button can be placed as a widget on your Android screen. ## Create the button in the Android App ::::WorkflowBlock :::WorkflowBlockItem Open the Make for Android app. ::: :::WorkflowBlockItem Tap **Buttons**. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/2SAM2hI_FFTKGbKGkXoTa_image.png" size="76" width="880" height="100" position="flex-start" showCaption="false"} ::: :::WorkflowBlockItem Tap **My first button**. ::: :::WorkflowBlockItem Enter the name for your button and ID (you will need this for your scenario module), and customize the button color and icon. ::: :::WorkflowBlockItem Save the button by tapping **Done**. ::: :::WorkflowBlockItem Create or go to a scenario and add the **Android > Watch Button** module to the first position in your scenario. ::: :::WorkflowBlockItem Select the device where you created the button, and enter the ID of the button. ::: :::: You can test the button by right-clicking on the **Android > Watch Button** module and clicking **Run this module only**. Then tap the button on your Android device. The **Watch Button** module in your scenario is triggered. Now, you can use this function to trigger your scenario via your mobile device. ## Place the button on your Android screen ::::WorkflowBlock :::WorkflowBlockItem Tap and hold anywhere on your Android screen to open the Manage Home menu. ::: :::WorkflowBlockItem Tap **Widgets**. ::: :::WorkflowBlockItem Find and tap the Make app. ::: :::WorkflowBlockItem Select the widget you want to add to your screen. ::: :::: The button now appears on your screen. You can move it by touching and holding the button and then dragging it. # Scanner **Barcode and QR code scanner** You can access the QR/barcode scanner by tapping the **Scanner** button in your app. The Scanner allows you to send barcode/QR code information to the module, and trigger the scenario (using the Watch Barcode/QR Code module) by scanning a barcode or QR code. The scanner features three buttons: 1. **Front/back** to switch between your device's cameras. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/kYDt_5ItWtZKQYBI-pq-5_uuid-12527196-79e7-039b-2fd1-6d17c5acaf37.png" size="20" width="108" height="90" position="flex-start" showCaption="false"} 2. **Flashlight** to turn on your device's flashlight as needed. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/UbGnuodrrzjufT82cQISm_uuid-927fb0b2-f5d9-1324-2535-510bf8c22f57.png" size="20" width="46" height="60" position="flex-start" showCaption="false"} 3. **Tag** to add descriptions to your scans. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/aEA9du9074BbtsLm8AX2X_uuid-98b06fdb-1c20-1e27-d58b-30774add458b.png" size="20" width="74" height="72" position="flex-start" showCaption="false"} The Barcode and QR code reader supports the following code formats: ```none Code 128 (FORMAT_CODE_128) Code 39 (FORMAT_CODE_39) Code 93 (FORMAT_CODE_93) Codabar (FORMAT_CODABAR) EAN-13 (FORMAT_EAN_13) EAN-8 (FORMAT_EAN_8) ITF (FORMAT_ITF) UPC-A (FORMAT_UPC_A) UPC-E (FORMAT_UPC_E) QR Code (FORMAT_QR_CODE) PDF417 (FORMAT_PDF417) Aztec (FORMAT_AZTEC) Data Matrix (FORMAT_DATA_MATRIX) ``` # Security The traffic between the mobile device and \{\{}} is secured by the Transport Layer Secure (TLS) encryption protocol. The authorization is based on a client certificate that is generated automatically when you log on. The certificate’s private key is generated on the device and securely stored in the System Keychain.