Resources · Make integration

Android Make integrationAutomate Android with Make.

What if your phone could start your automations on its own? The Android Make integration gives you 39 modules, including 17 instant triggers and 22 actions. This guide is for people who carry the phone all day, and it walks you from the connection to your first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Android Make integration do for you?

The Android Make integration links your phone to Make, so what happens on the device (a call, a text, a photo, a WiFi change) can start a scenario, and a scenario can act on the phone in return. A scenario is the automation you build in Make: a chain of modules, each one a single brick such as a trigger or an action.

Missed-call follow-up. When Watch completed incoming calls reports a finished call, the next modules can log it in your CRM, and Send a push notification reminds you to call back. Sales reps on the road get a clean call history without typing anything.

Photo proof from the field. New photo fires the moment the phone takes a picture. Pair it with a storage app and every site photo lands in the right client folder. The reverse works too: Save a photo pushes an image from a scenario onto the device.

Location-aware reminders. Watch entrances to/exits from a geofence area tells Make when the phone enters or leaves a circle you defined, which suits delivery drivers and technicians who need a checklist on arrival.

Some limits come from Google, not Make. Since 2019, apps on Google Play cannot read SMS or call logs, so the SMS functions need the unrestricted Make app for Android downloaded from the website. The page on n8n vs Make helps if you are still choosing a tool, and the Make pricing guide explains what each plan allows. For a guided start, see our Make training.

Connect

How do you connect your Android phone to Make?

  1. 01

    Install the Make app on the phone

    Your device needs Android 7.0 or later and the Make app for Android installed. If you plan to read or send text messages, take the unrestricted version from the Make website rather than Google Play.

  2. 02

    Add an Android module in the editor

    In a scenario, click the + and search for Android, then pick any module. Click Create a connection, which links your device to Make once and reuses it in every Android module. You can give the connection a name if you run several phones.

  3. 03

    Authorize and save

    Follow the authorization Make shows you for the device, then click Save. The connection now appears in the module, and the other Android modules can pick it from the same list.

First scenario

Your first scenario: forward incoming texts as push alerts

GoalWhen your Android phone receives a text message, Make sends a push notification to a second device you choose.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. Click the big + to place the first module, the one that starts everything.

  2. 02

    Pick the Watch text messages trigger

    Search for Android, choose Watch text messages, then click Create a connection to link your phone. Remember that SMS needs the unrestricted Make app with SMS enabled in its settings.

  3. 03

    Add Send a push notification

    Click the + on the right of the trigger and add Send a push notification. Pick the device that should get the alert, then map the sender and the text from the previous module into the message.

  4. 04

    Test with Run once

    Click Run once, then send a text to the phone. Each module shows the bundle it received, so you can check the sender and message before going live.

  5. 05

    Switch the scenario on

    Turn the scenario on with the toggle. Because this trigger is instant, the phone calls Make as soon as a text arrives instead of waiting for a schedule.

Triggers

Which Android events can start a scenario?

17 modules start a scenario when something happens in Android. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Android as soon as it happens.

Android1New photo

New photo

Instant trigger

In MakeTriggers when a device takes a photo.

Snap a picture and your scenario starts with that photo as its first bundle, the single item passed from one module to the next. It turns the phone camera into an upload button for any app Make can reach.

How it fires
instant: the app calls Make through a webhook as soon as it happens, so there is no schedule to wait for.
When to use it
a technician photographs a finished job and the picture should reach the client file without a manual upload.
Watch out
every photo the device takes starts a run and counts operations on your plan, so personal pictures trigger it too.
Android2Watch barcode / QR code

Watch barcode / QR code

Instant trigger

In MakeTriggers when you scan a barcode / QR code.

Scanning a barcode or a QR code with the phone hands the result to Make and starts your scenario. Your Android device becomes a pocket scanner feeding a spreadsheet, a stock tool or an order system.

How it fires
instant: the app calls Make through a webhook as soon as it happens, one run per scan.
When to use it
a warehouse team checks parcels in on receipt and wants each scanned code written to a tracking sheet right away.
Watch out
the scan happens in the Make app for Android, so the person scanning needs it installed and connected to the same account.
Android3Watch Bluetooth activations

Watch Bluetooth activations

Instant trigger

In MakeTriggers when you enable Bluetooth on a device.

Turning Bluetooth on is a small gesture, and this trigger lets it mean something: the scenario starts the moment the phone's Bluetooth switches on. Use it as a manual on switch that needs no extra app.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a driver enables Bluetooth when starting a shift, and Make logs the start in a timesheet.
Watch out
it reacts to the switch, not to a paired device; for a specific headset or car kit, Watch connections to Bluetooth devices is the closer fit.
Android4Watch Bluetooth deactivations

Watch Bluetooth deactivations

Instant trigger

In MakeTriggers when you disable Bluetooth on a device.

The mirror of the activation trigger: when Bluetooth goes off on the device, Make starts your scenario. Paired with the previous one, it gives you a simple start and stop signal from the phone.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
closing a work session in a time tracker when the field worker switches Bluetooth off at the end of a visit.
Watch out
it reacts to the switch itself, so if something other than a person turns Bluetooth off, expect a run all the same; do not read every run as a deliberate gesture.
Android5Watch Button

Watch Button

Instant trigger

In MakeTrigger when you push a button.

This gives you a button that starts a scenario when you push it. No event to wait for, no condition to meet: you decide when the automation runs, straight from the phone.

How it fires
instant: the app calls Make through a webhook as soon as it happens, once per press.
When to use it
a store manager taps the button to send the closing report or to alert the team that a delivery has arrived.
Watch out
each press is a new run, so a nervous double tap sends the same message twice; keep the following modules safe to repeat.
Android6Watch completed incoming calls

Watch completed incoming calls

Instant trigger

In MakeTriggers when a device registers a completed incoming call.

Once a call you received ends, this trigger passes it to Make, which is the right moment to log it, since the conversation is over. It feeds call history into tools that never see your phone.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a consultant wants each client call recorded as an activity in the CRM without typing it in.
Watch out
Google restricts call log access for apps from Google Play, so check that your Make app version can read calls before building on it.
Android7Watch completed outgoing calls

Watch completed outgoing calls

Instant trigger

In MakeTriggers when a device registers a completed outgoing call.

After you hang up on a call you placed, Make receives it and the scenario runs. It is the outgoing twin of the completed incoming trigger and closes the loop on prospecting calls.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a sales rep calls leads from the phone and each finished call should move the lead to the next stage.
Watch out
call logs fall under the Google Play restrictions, so the unrestricted Make app for Android from the website is the safer install.
Android8Watch connections to Bluetooth devices

Watch connections to Bluetooth devices

Instant trigger

In MakeTriggers when a device connects to another Bluetooth device.

When the phone pairs with another Bluetooth device, a car kit, a headset or a scanner, your scenario starts. That connection is often a reliable sign of where you are and what you are doing.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
the van's hands-free kit connects and Make marks the driver as on the road in the dispatch board.
Watch out
any Bluetooth device fires it, so a wireless earbud counts the same as the van; plan how your next modules tell them apart.
Android9Watch disconnections from Bluetooth devices

Watch disconnections from Bluetooth devices

Instant trigger

In MakeTriggers when a device disconnects from another Bluetooth device.

The phone losing its link with another Bluetooth device starts the scenario. Leaving the car, putting the headset away or walking out of range are all events you can now act on.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a technician parks, the car kit drops, and Make opens the visit report for the job.
Watch out
a device that goes out of range for a moment also disconnects, so one real departure may show up as several runs.
Android10Watch entrances to/exits from a geofence area

Watch entrances to/exits from a geofence area

Instant trigger

In MakeTriggers when a device enters or leaves a predefined circle.

Draw a circle around a place, and Make hears about it whenever the phone crosses the edge, going in or coming out. Arrival and departure become events your tools can react to.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a cleaning company wants the client notified when the team reaches the site and a record kept when it leaves.
Watch out
the circle is defined in advance; if the people who carry the phone work at many addresses, Watch location changes may suit you better.
Android11Watch incoming calls

Watch incoming calls

Instant trigger

In MakeTriggers when a device registers an incoming call.

This reacts while the phone is ringing, not after the call. Make gets the incoming call right away, so the scenario can look up the caller before you pick up.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a support line on a shared phone should post each incoming call in the team chat so nobody answers blind.
Watch out
it fires for every call, answered or not; if you only care about finished conversations, Watch completed incoming calls avoids the noise.
Android12Watch location changes

Watch location changes

Instant trigger

In MakeTriggers when a device changes its location.

The phone moves and Make receives its new position, which lets a scenario follow a person on the move without a dedicated tracking tool. Good for anything that depends on where the device is.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a courier's position should update the customer delivery page as the van gets closer.
Watch out
a phone on the move changes location a lot, and each change is a run that consumes operations; a geofence is lighter when only arrival matters.
Android13Watch outgoing calls

Watch outgoing calls

Instant trigger

In MakeTriggers when a device makes an outgoing call.

Dial a number and the scenario starts at once, without waiting for the call to end. It captures the intent to call rather than the result of it.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a recruiter wants the candidate record opened on the laptop as soon as the call starts from the phone.
Watch out
a call that never connects still fires; for a log of real conversations, Watch completed outgoing calls is the better source.
Android14Watch sent SMS

Watch sent SMS

Instant trigger

In MakeTriggers when a device sends a text message.

Every text message your phone sends becomes a bundle in Make. It keeps a copy of what you promised a client by text in a place your team can read.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a property manager confirms visits by text and wants each confirmation added to the tenant's file.
Watch out
SMS functions only work with the unrestricted Make app for Android from the website, with SMS enabled in its mobile settings; the Google Play version stays silent.
Android15Watch text messages

Watch text messages

Instant trigger

In MakeTriggers when a device receives a text message.

A text lands on the phone and the scenario starts with the message in hand. Codes, confirmations and customer replies can flow into your other tools without anyone copying them.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a small shop receives orders by text and wants each one created in the order sheet as it arrives.
Watch out
like every SMS function, it needs the unrestricted Make app from the website and SMS turned on in that app's mobile settings.
Android16WiFi connection

WiFi connection

Instant trigger

In MakeTriggers when a device connects to a WiFi network.

Joining a WiFi network is a quiet signal that you have reached a known place, and this trigger turns it into the start of a scenario. The office network, the store, the workshop: each can mean something.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
an employee reaches the office, the phone joins the office network, and Make checks them in for the day.
Watch out
the trigger fires for any network, so your home WiFi starts the same scenario unless the next modules look at which network it was.
Android17WiFi disconnection

WiFi disconnection

Instant trigger

In MakeTriggers when a device disconnects from a WiFi network.

When the phone drops a WiFi network, Make starts your scenario. Paired with the connection trigger, it brackets the time spent in one place.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
leaving the workshop network closes the open job in the time tracker and sends a summary to the manager.
Watch out
a weak signal can drop and reconnect in a short span, so one exit may produce a disconnection followed by a new connection.
Modules

What can Make do on your Android phone?

Android gives you 22 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Set Up the Make for Android App

9 modules

To use the SMS functions, you must install the unrestricted Make app for Android. 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.

Android1

General Settings

ActionIn the docs only

This entry belongs to the setup group of the Make for Android app in the Make documentation, the part that prepares the phone before any module can use it. The documentation lists it without a description.

When to use it
before your first Android scenario, when you install the app on a device with Android 7.0 or later.
Watch out
for text messages, the unrestricted app also needs SMS switched on in its mobile settings, a step people often skip.
Android2

QR / Barcode Scanner

ActionIn the docs only

Part of the setup group of the Make for Android app, this entry relates to scanning, which is what Watch barcode / QR code sends to Make. The documentation gives no description of it.

When to use it
when you plan to use the phone as a scanner and want the app side ready before building the scenario.
Watch out
scanning happens inside the Make app, so the person scanning needs it installed and connected.
Android3

Photos

ActionIn the docs only

Listed in the setup group of the Make for Android app, this entry concerns the photo side of the integration: New photo, Take a photo and Save a photo. The documentation offers no description of it.

When to use it
when a scenario will read pictures from the camera or push images onto the device.
Watch out
without the app ready on the phone, the photo modules have no device to talk to.
Android4

GPS

ActionIn the docs only

In the setup group of the Make for Android app, this entry covers location, the source behind Watch location changes and Watch entrances to/exits from a geofence area. The documentation lists it without a description.

When to use it
when your scenario depends on where the phone is, for arrivals, departures or a moving courier.
Watch out
location triggers can run often on a phone that moves, and every run uses operations on your plan.
Android5

WiFi

ActionIn the docs only

This setup entry of the Make for Android app concerns WiFi: the two WiFi triggers and the Enable WiFi and Disable WiFi actions. The documentation names it and gives no further description.

When to use it
when joining or leaving a network should start a scenario, or when a scenario should switch WiFi for you.
Watch out
turning WiFi off from a scenario can also cut the phone's own link if it has no mobile data.
Android6

Bluetooth

ActionIn the docs only

The Bluetooth entry of the setup group relates to the four Bluetooth triggers and to the Enable Bluetooth and Disable Bluetooth actions. The Make documentation lists it without describing it.

When to use it
when a car kit, headset or other paired device should drive your scenarios.
Watch out
any paired device counts, so decide early how your scenario tells the van kit from a pair of earbuds.
Android7

Calls

ActionIn the docs only

Call handling in the Make for Android app sits under this setup entry, behind the four call triggers and the Make a call and Prepare a phone call actions. No description is given in the documentation.

When to use it
before any scenario that logs calls or dials numbers from the phone.
Watch out
since 2019, Google Play apps cannot read call logs, so the version of the Make app you install matters here.
Android8

SMS

ActionIn the docs only

This is the setup entry that unlocks text messages: without it, Watch text messages, Watch sent SMS and Send text message do nothing. It is the one setup step the documentation spells out.

When to use it
as soon as a scenario reads or sends SMS.
Watch out
install the unrestricted Make app for Android from the website, not Google Play, then enable SMS in its mobile settings.
Android9

Web

ActionIn the docs only

The last setup entry concerns the browser side of the Make for Android app, used by Open a web browser and Close a web browser. The documentation lists it but adds no description.

When to use it
when a scenario should put a page in front of the person holding the phone.
Watch out
a page opened from a scenario interrupts whatever the user is doing, so keep it for moments that call for it.

Other modules

13 modules
Android10

Change a ring mode

Action

In MakeChanges the active ring mode on a device.

Silence the phone, or bring the ringer back, from a scenario. The module switches the active ring mode on the device so nobody has to remember to do it by hand.

When to use it
a geofence around the meeting room puts the phone in silent mode on arrival and restores the ringer on exit.
Watch out
plan the way back; a scenario that silences the phone without a matching one to undo it leaves calls unheard.
Android11

Close a web browser

Action

In MakeCloses a browser window on the target device.

Shut the browser window on the target device once its job is done. It is the natural second half of Open a web browser, keeping a shared phone tidy between uses.

When to use it
a kiosk tablet shows a form to a customer and the scenario closes it after the answer arrives.
Watch out
the module closes a browser window, so anything the person was reading in it disappears too.
Android12

Disable Bluetooth

Action

In MakeTurns off Bluetooth on a device.

Turn Bluetooth off on the device from any scenario. Useful for saving battery or for making sure a company phone does not stay paired where it should not.

When to use it
the phone leaves the depot geofence and Make switches Bluetooth off until the next shift starts.
Watch out
if Watch Bluetooth deactivations runs in another scenario, this action will start that one too.
Android13

Disable WiFi

Action

In MakeTurns off WiFi on a target device.

Switch WiFi off on the target device without touching it. The phone falls back to mobile data, which can matter for security or for a shared device in public places.

When to use it
a field phone leaves the office network area and should stop joining open networks on the way.
Watch out
with no mobile data, the phone loses its link to Make as well, so it cannot receive the order to turn WiFi back on.
Android14

Enable Bluetooth

Action

In MakeTurns on Bluetooth on a device.

Bring Bluetooth back on the device from a scenario, so a car kit or scanner can pair without the user digging through settings.

When to use it
the driver presses the Watch Button trigger at the start of a route and Make turns Bluetooth on for the hands-free kit.
Watch out
this action starts any scenario that listens to Watch Bluetooth activations, so check you are not building a loop between two scenarios.
Android15

Enable WiFi

Action

In MakeTurns on WiFi on a target device.

Turn WiFi on at the target device from Make. The phone can then join known networks again, which saves mobile data at the office or the warehouse.

When to use it
entering the warehouse geofence switches WiFi on so the scanner uploads run over the local network.
Watch out
enabling WiFi can fire WiFi connection once the phone joins a network, so mind scenarios that listen to it.
Android16

Make a call

Action

In MakeDials a specified number on a device.

This action dials a number on the phone for you, straight from a scenario. The call starts on the device, so the person holding it only has to talk.

When to use it
a high-priority ticket lands in the help desk and the on-call phone rings the customer back at once.
Watch out
the call starts without asking; if the user should decide, Prepare a phone call only fills the number in.
Android17

Open a web browser

Action

In MakeOpens a browser window on the target device showing a pre-entered URL.

Put a web page in front of the person holding the phone: the module opens a browser window on the device at a URL you set in the scenario. Links from other apps can land there too.

When to use it
a technician enters a client site and the phone opens that client's checklist form.
Watch out
it takes over the screen, so avoid it on a phone someone may be using to drive.
Android18

Prepare a phone call

Action

In MakeOpens the phone app on a device and pre-fills a phone number.

The gentler version of Make a call: it opens the phone app with the number already filled in and leaves the dial button to the user. Nothing happens until someone chooses to call.

When to use it
a new lead comes in from a web form and the sales rep finds the number ready on the phone.
Watch out
the call only happens if someone is holding the phone; for an unattended device, the number just waits on screen.
Android19

Save a photo

Action

In MakeUploads a photo to a device.

Send an image from a scenario onto the phone. A plan, a label or a signed document produced elsewhere ends up on the device where the person on site can open it.

When to use it
a delivery driver receives the photo of the parcel label generated by the shipping tool before reaching the door.
Watch out
this pushes to the device; to capture a new picture on the phone, the module you want is Take a photo.
Android20

Send a push notification

Action

In MakeSends a push notification to a selected device.

Alert a phone with a notification written by your scenario. It is the lightest way to tell someone on the move that something needs their attention, without email or chat.

When to use it
a big order lands in the online store and the owner's phone shows the amount and customer name.
Watch out
you pick the target device in the module, so a scenario built for one colleague will not reach another's phone by itself.
Android21

Send text message

Action

In MakeSends a text message.

Send an SMS from the phone's own number, triggered by anything Make can see. Customers get a text from a number they recognize, not from an unknown service.

When to use it
an appointment is booked in the calendar and the client receives a confirmation text from the business phone.
Watch out
it requires the unrestricted Make app for Android from the website, with SMS enabled in its mobile settings.
Android22

Take a photo

Action

In MakeTakes a photo on a device.

Tell the phone to take a picture from a scenario, with no one pressing the shutter. The photo can then flow to the next module like any other bundle.

When to use it
a tablet mounted at a loading dock takes a picture each time a delivery is scanned in, for proof of condition.
Watch out
the camera fires whatever it is pointed at, so this suits fixed devices better than a phone in a pocket.
Need help

Need help automating Android with Make?

A person reads every message.

FAQ

Android Make integration: common questions

01Is the Android Make integration free?
Yes. Android is a standard app, so it works on the Free plan of Make. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Each module run counts as an operation, one step of one module on one bundle, and your plan counts those operations. Scheduled scenarios on Free wait at least 15 minutes between runs, but that matters little here because every Android trigger is instant. Paid plans lift the active scenario limit and allow runs of up to 40 minutes.
02What do you need to connect Android to Make?
An Android device running 7.0 or later, with the Make app for Android installed, and a Make account. In the editor you add any Android module, click Create a connection, authorize the device and save. For text messages, the Google Play version is not enough: Google has restricted SMS and call log access for Play apps since 2019. Install the unrestricted Make app from the website and enable SMS in its mobile settings. Your settings and scenarios from the Play version keep working after the switch.
03Does the Android Make integration react in real time?
Yes. All 17 Android triggers are instant: the phone calls Make through a webhook as soon as the event happens, whether that is a call, a text, a photo, a scan or a WiFi change. There is no polling interval to set and no 15 minute wait from the Free plan. A scheduled trigger would check at regular intervals, marked by a clock badge in the editor; the Android triggers carry the lightning badge instead. Just keep the phone connected, since the event has to reach Make.
04What if an Android module you need is missing in Make?
The Android app has 39 modules, but no Make an API Call module, so you cannot reach phone features beyond those listed. Start by combining what exists: a trigger such as Watch text messages with an action from another app often covers the need. The main limit comes from Google, which blocks SMS and call log access for Play apps, and the unrestricted Make app from the website removes it. If the gap remains, our Make agency can review your case and suggest another app.
05Should you pick Make or n8n for Android automations?
It depends on what you already run. In Make, Android comes with 39 ready modules, including 17 instant triggers, and a free plan that covers this app. The same app often has an n8n node, so check the n8n side before deciding if your team already works there. Compare on the modules you need, how your team likes to build, and where your other scenarios live. The n8n vs Make comparison on this site lays out those criteria without picking a winner for you.