Automation library · Alerts and monitoring

Monitor APK uploads and run MobSF analysis with OpenAI

Started by an event in a connected app, and works across Google Drive and Slack. It hands the judgement calls to OpenAI. 9 steps: a working afternoon to understand properly.

MediumCalls a model: OpenAI

9 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Model 1Logic 3Service 4

The steps in the order they run, from what starts it.

  1. 1Start Analysis TriggerGoogle Drive triggerStarts it
  2. 2Download ApkGoogle DriveService
  3. 3MobSF – Upload APKHttp RequestService
  4. 4MobSF – Start Static AnalysisHttp RequestService
  5. 5Extract used and detected packagesCodeLogic
  6. 6Identify Unused PackagesCodeLogic
  7. 7Classify Unused Package Risk LevelsCodeLogic
  8. 8Generate Developer SummaryOpen AiModel
  9. 9Notify Team on SlackSlackService

How it's built

Starts on
An event in a connected app
Steps
9
Size
Medium: a working afternoon
Connects to
Google Drive, Slack
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Google Drive and Slack accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.