Troubleshooting

Webhook delivery & HTTP errors

Symptoms that show up before you know which trigger type or platform is at fault. Start here. Every execution is logged in the trigger’s Activity tab with the full request URL, request body, headers, status code, and response body — open that first when debugging.

Webhook not received

If your FlowTrigger webhook is not reaching your automation platform, check the following in order: verify the webhook URL is correct with no typos and that it includes https://. Confirm your automation workflow is active and published. Ensure your phone has internet connectivity. Finally, check the Activity tab in FlowTrigger for the HTTP status code — a 4xx code means a client-side error like a wrong URL or missing authentication, while a 5xx code means the server encountered an error. Check the Advanced tab on your trigger for HTTP configuration options.

401 Unauthorized

A 401 Unauthorized error means your webhook endpoint requires authentication credentials that are either not configured or are incorrect in FlowTrigger. Open your trigger’s settings and check the authentication configuration. FlowTrigger supports two authentication methods: Basic Auth (username and password) and Header Auth (custom header with an API key or token). Verify that your credentials match exactly what the endpoint expects — pay attention to capitalization, spaces, and prefixes like “Bearer” for token-based auth. You can configure authentication in the Advanced tab when editing any trigger.

404 Not Found

A 404 Not Found error means the webhook URL does not exist or is incorrect. Double-check the URL in FlowTrigger for any typos, missing path segments, or extra characters. If you recently recreated the webhook node in your automation platform, the URL may have changed — copy the new URL and update it in FlowTrigger. For platform-specific 404 causes, see the n8n-specific issues and Make-specific issues sections below.

500 Internal Server Error

A 500 Internal Server Error occurs on the server or workflow side, not in FlowTrigger. The request was delivered successfully, but the receiving workflow failed during processing. Check your automation platform’s execution logs for detailed error information. Common causes include: the workflow has a bug in a downstream node, required fields are missing from the incoming data, or the workflow cannot connect to a third-party service (e.g., database timeout, API rate limit). Fix the issue in your workflow and resend the trigger from FlowTrigger.

Pending status

A pending status in FlowTrigger usually means the HTTP request was sent but the app has not yet received a response from the webhook endpoint. This can happen when the endpoint takes a long time to process (common with AI/LLM workflows), when network connectivity is intermittent, or when the server is under heavy load. Check your internet connection and verify the webhook endpoint is responding. If the pending status persists, check the endpoint’s logs to see if the request was received. Some platforms process webhooks asynchronously and may not return an immediate response.

Inspecting the full request and response

FlowTrigger logs every execution with full HTTP details. Go to the trigger’s Activity tab and tap any execution entry to view the details. You will see: the complete request URL, the full request body (JSON or multipart fields), request headers (including Content-Type, authentication headers, and any custom headers you configured), the HTTP status code returned by the server, and the full response body. This is invaluable for debugging webhook issues — you can verify exactly what FlowTrigger sent and what the server returned.

Android background reliability

Android aggressively kills background processes, which breaks any trigger that must run when the app is not in the foreground. This affects notification triggers and location triggers the most. If either type is unreliable, fix battery optimization first before debugging the trigger itself.

Disabling battery optimization

To disable battery optimization for FlowTrigger, go to Android Settings → Apps → FlowTrigger → Battery → select “Unrestricted”. This prevents Android from killing FlowTrigger’s background services, which is essential for notification triggers and location triggers to work reliably.

Manufacturer-specific quirks

The exact wording for the “Unrestricted” battery setting varies by manufacturer — Samsung uses “Unrestricted”, Xiaomi uses “No restrictions”, Pixel uses “Unrestricted”. On Xiaomi, Huawei, and Samsung devices you may also need to disable additional battery-saving features like “Adaptive Battery” or add FlowTrigger to a battery whitelist. Check dontkillmyapp.com for device-specific instructions.

Manual trigger

Sending multiple photos

Currently, FlowTrigger’s manual trigger supports sending one photo per trigger execution. The photo is included in the HTTP request as a multipart form data field. If you need to send multiple photos, you can create separate trigger executions for each photo, or configure your automation workflow to accept sequential uploads and aggregate them. Each execution is logged independently in the Activity tab.

Voice-to-text vs voice recording

In the manual trigger setup, FlowTrigger offers two distinct voice input modes. “Voice to Text” uses your device’s speech recognition engine to convert spoken words into text, which is sent in the textInput JSON field — useful when your workflow expects text input. “Voice Input” records an audio file and sends it as the audioInput field in multipart form data — useful when your workflow needs the actual audio for processing or transcription on the server side. Choose the mode that matches how your automation workflow expects to receive the data.

Notification trigger

Notifications not being forwarded

If your notification triggers are not working in FlowTrigger, check the following: 1) Notification listener permission must be granted — see “Granting notification access permission” below. 2) Verify the trigger is active in FlowTrigger’s Overview tab (the “Trigger Active” toggle must be on). 3) Battery optimization must be disabled for FlowTrigger — see Android background reliability above. 4) Confirm the monitored app is actually sending notifications (check your notification shade). 5) If you selected specific apps to monitor, make sure the correct apps are selected in the trigger configuration.

Granting notification access permission

To grant notification access permission for FlowTrigger, go to Android Settings → Apps → Special app access → Notification access (or search for “Notification access” in the Settings search bar). Find FlowTrigger in the list and toggle it on. Android will show a warning that FlowTrigger will be able to read your notifications — this is required for the notification trigger feature to detect incoming notifications and forward them to your webhook. FlowTrigger only reads notification title, body, app name, and timestamp, and sends this data only to the webhook URL you configure.

Location trigger

Geofence not firing

If your FlowTrigger location trigger is not firing, check these common causes in order: 1) Battery optimization — see Android background reliability above. 2) Location permission — must be set to “Allow all the time” (not “While using the app”). 3) Geofence radius — if set below 100 meters, triggers may be unreliable due to GPS accuracy limitations. 4) GPS accuracy — indoor locations and urban canyons with tall buildings degrade GPS signal significantly. 5) Ensure the trigger is toggled active in FlowTrigger’s Overview tab.

Minimum geofence radius

FlowTrigger allows configuring geofence zones with custom radii, but for reliable triggering we recommend a minimum radius of 100 meters. Smaller radii may work in open outdoor areas with strong GPS signal, but they become unreliable indoors, near tall buildings, or in areas with poor satellite visibility. GPS accuracy on most Android devices is typically 3–15 meters in ideal conditions but can degrade to 50+ meters in challenging environments. If your location triggers are firing inconsistently, increasing the radius is the first thing to try.

Delayed or inaccurate geofence events

Location accuracy depends on several factors:

  • GPS accuracy: Indoor locations or dense urban areas may have reduced accuracy. The accuracyMeters field in each payload shows the GPS precision for that reading.
  • Geofence zone size: Very small zones (under 100m radius) may trigger less reliably. Android recommends a minimum radius of 100 meters for consistent detection.
  • Background restrictions: Some Android manufacturers aggressively limit background activity. Ensure battery optimization is disabled for FlowTrigger and check dontkillmyapp.com for device-specific settings.
  • Transition delays: Android may batch geofence events for battery efficiency, causing slight delays (typically under 2 minutes) in ENTER/EXIT notifications.

Push notifications (workflow → app)

Push notifications are the reverse direction of regular triggers: your workflow sends a request to FlowTrigger’s Push URL, and the app displays a notification on your device.

Push notifications not arriving

If your workflow is sending requests to the Push URL but notifications aren’t appearing:

  • Check the Push URL: Ensure your workflow is sending a POST request to the exact URL shown on the trigger’s overview screen.
  • Check the payload: The request body must include a message field with a string value.
  • Check device settings: Ensure notifications are enabled for FlowTrigger in your Android notification settings.
  • Check battery optimization: Some Android manufacturers restrict background activity. Disable battery optimization for FlowTrigger — see Android background reliability above.

n8n-specific issues

Issues that only affect n8n workflows.

Test URL vs Production URL

n8n webhook nodes expose two different URLs: a Test URL that only listens while you have the workflow editor open and the “Listen for test event” button active, and a Production URL that always listens once the workflow is toggled Active. FlowTrigger must use the Production URL. If you copied the Test URL, requests will fail with a 404 once you close the editor. Open the webhook node, switch to the Production URL tab, copy that URL, and confirm the workflow’s Active toggle (top-right of the editor) is on.

Make-specific issues

Issues that only affect Make scenarios.

Scenario must be saved and turned on

Make scenarios do not accept incoming webhooks until the scenario itself is switched on. A scenario can be saved, valid, and have a webhook URL assigned, and still return errors or “Accepted” because the on/off toggle (bottom-left of the scenario editor) is off. Open the scenario and turn it on. If the scenario is set to run “On demand” rather than “Immediately as data arrives”, change it to immediate so each FlowTrigger request runs the scenario right away. Refer to https://help.make.com/webhooks for more info about Make webhook module.

Managing triggers

Changing a webhook URL

To change the webhook URL for an existing trigger in FlowTrigger, open the trigger from the Overview tab, tap the three-dot menu icon in the top-right corner, and select “Edit”. Update the webhook URL in the configuration screen along with any other settings you want to change, then save. The new URL will be used for all future executions. Previous execution history remains unchanged and still shows the URL that was used at the time of each execution.

Deleting a trigger

To delete a trigger in FlowTrigger, open the trigger from the Overview tab, tap the three-dot menu icon in the top-right corner, and select “Delete”. Confirm the deletion when prompted. The trigger configuration and all its execution history will be permanently removed from the app. Since FlowTrigger stores data locally, deleted triggers cannot be recovered unless you have previously exported your data using the Premium backup feature.