Automation library · Documents and files

Verify subcontractor licenses from form submissions with Apify

Started by someone submitting a form, and works across Apify and Slack. 9 steps, 1 branch: a working afternoon to understand properly.

Medium

Download free
9 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 6Service 2

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

  1. 1Subcontractor submits the formForm triggerStarts it
  2. 2Validate the submissionCodeLogic
  3. 3Route by stateCodeLogic
  4. 4Can we check it?IfLogic
  5. 5Look up the licenceApifyService
  6. 6Send it to a humanSetLogic
  7. 7Decide the verdictCodeLogic
  8. 8Write the audit rowCodeLogic
  9. 9Post the verdict to SlackSlackService

How it's built

Starts on
Someone submitting a form
Steps
9, with 1 branch
Size
Medium: a working afternoon
Connects to
Apify, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Apify and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on someone submitting a form.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

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.