There is no ScreenApp Make integration
ScreenApp does not connect to Make. There is nothing to install in Make, nothing to connect under Settings, and ScreenApp does not post, sync or create anything in Make on its own. Anything that ends up in Make gets there because you put it there.
That is worth saying plainly, because the rest of this page is about the part that does work.
What you can actually do
- Record the meeting in ScreenApp, or upload a file you already have.
- Wait for the transcript and the AI summary.
- Copy the text, or export the transcript as PDF, DOCX, TXT, SRT and VTT.
- Move the text across by hand, or have a scenario call the ScreenApp API on a schedule.
- If people need to watch the recording, send them a share link. Share links are not password protected, so only send them to people who should see the recording.
What a Make scenario can and cannot do
ScreenApp does not offer webhooks, so the trigger is a scheduled scenario. Use Make’s HTTP module to check the ScreenApp API for finished recordings, retrieve the transcript, and map it to the destination. You build and maintain this workflow yourself.
For developers
ScreenApp has API keys and a public API. You can generate an API key and pull a recording, its transcript and its summary, then hand them to a Make scenario through its HTTP module, or skip Make and call the target tool directly. Use the API to retrieve recordings. ScreenApp does not offer webhooks, so your code or automation service checks the API for finished recordings and writes them to the destination; this is not a native integration.
Frequently asked questions
Is there a ScreenApp module in Make?
No. Use the generic HTTP module and an API key.
Can a scenario start the moment a recording finishes?
No. ScreenApp does not send events to Make. Run the scenario on a schedule and check the API for recordings that have finished processing.