Every send can feed your tools directly: n8n, Make, Zapier, Power Automate, or any HTTPS address (webhook). Photos go out exactly as taken, with the details entered, the date and the location. With no network, the send waits on the phone and goes out on its own when the network is back. The automation runs in your own environment, even if you entrust its development and maintenance to us.
Every send goes from the phone to your automation platform, which passes it on to your tools. No intermediary: your data doesn't go through us.
You send from the app: photos exactly as taken, voice memos, files and captured information travel together, encrypted (HTTPS).
It receives the send on its webhook address and runs your workflow.
Photos filed in the right place, register filled in, the right person notified, report drafted by an AI.
After that, every send goes to the right place without you thinking about it.
In your platform, a webhook trigger gives you an address starting with https://, with a key or a token depending on the case. Where to find it on your platform.
In the app, open Automations: “Scan the QR code received”, or “Set up by hand” with what you were given. “Test connection” confirms everything is connected.
Template by template, in “Where it goes”: by email, to the automation, or both. Every send is logged in My sends.
The automation is the same in Pro and Business. Business adds fleet deployment.
One-time purchase, no subscription. For one device: yours.
Annual subscription by device range: maintenance, updates and support included.
Any platform that can receive a send on an https:// address will do.
For the most common ones (as of Sept. 2026):
| Platform | Where to find the address | Possible security → answer in the app |
|---|---|---|
| n8n | The workflow's Webhook node, Production URL address (the Test URL address is only for trying it out in the editor). | Authentication: None → “An address, nothing else”; Header Auth → “An address and a key” (the header name is the one entered in n8n). Signed mode (“An address, a token and a signing secret”) needs a workflow that implements the app's integration spec: that is what our automation services deliver. Basic Auth and JWT Auth are not supported. |
| Make | The scenario's Webhooks › Custom webhook module: the address is shown when the webhook is created. | No option → “An address, nothing else”; with the webhook's API key option → “An address and a key”, header x-make-apikey. |
| Zapier | Webhooks by Zapier › Catch Hook trigger: the address is shown at the Test step. | “An address, nothing else” (a key checked by a filter in the Zap → “An address and a key”). |
| Power Automate | When an HTTP request is received trigger: the address appears after the flow is first saved (with its sig= signature when Anyone can trigger it). | Who can trigger the flow? • Anyone → “An address, nothing else”. • Specific users in my tenant (at Microsoft, the tenant is your organisation) → “Sign-in credentials” (OAuth 2.0). Microsoft-side setup ⓘYour Microsoft 365 administrator registers an application in Microsoft Entra, creates a client secret for it, then adds it to the flow's allowed users (by the object ID of its enterprise application). In the app: token URL https://login.microsoftonline.com/<tenant ID>/oauth2/v2.0/token, the application's ID and secret, scope https://service.flow.microsoft.com//.default (with the double slash).Avoid Any user in my tenant: the same token would open every flow set that way. |
| Other platform, server or business tool | Wherever the tool shows its receiving address (incoming webhook, API). | Depending on what the tool can check: address alone, key in a header, or Signed mode if you implement the integration spec. |
These labels are those of the interfaces as of September 2026; they may change with new versions. If in doubt, ask the person who built the automation for a QR code.
n8n files (JSON) to import into your n8n: simplified versions to get started, which put everything into Google Drive or Google Sheets. Notes inside each workflow explain, step by step, what to set up and adapt to your templates. For a fleet or stronger security (Signed mode, one secret per device, file integrity checks), the full version is designed and installed in your environment as part of our automation services.
Photos are sorted in Google Drive by customer and by site, named with the date and location.
Download the JSON ↓Voice memos are transcribed (Mistral Voxtral) and saved as text next to the audio in Google Drive: searchable, copyable, archivable.
Download the JSON ↓The GPS position of each photo becomes a plain-text postal address in a Google Sheets table, with the details entered.
Download the JSON ↓Photos, details and transcriptions assembled into a report (Google Doc), in one Google Drive folder per submission, shareable with the recipients.
Download the JSON ↓MVT Conseil designs, deploys and maintains your automations. They run in your own environment, even when you entrust their development and maintenance to us: we don't host your automations.
Your business template designed with you, tested, delivered as a file signed by the publisher and rolled out to your phones by QR code, including your PDF template in your own colours.
Analysis of your workflow, design, installation in your environment, testing with your teams, documentation. Sorting, transcription, automatic reports, IT system integration.
Monitoring, upgrades and troubleshooting for your automations. Monthly pricing or a bank of hours, as you prefer.
Are you an n8n agency or an integrator? ClicInSitu is a clean, signed field data source for your clients: write to us.
Describe your current workflow: we'll get back to you with a concrete proposal.
Write to contact@clicinsitu.fr