Input

WhatsApp inbound

Text a keyword to start a job

The WhatsApp inbound node lets people start a job by sending a WhatsApp message to your dojobase number. The message's text and any photos or PDFs attached become the job — ideal for field staff or partners who live in WhatsApp, not email.

How it works

Everyone messages the same WhatsApp number, so the node decides which workflow a message belongs to two ways: a keyword (the first word of the message, unique across your workflows) and a pre-registered sender list (a known number routes here with no keyword at all — perfect for repeat senders like brokers).

If someone is set up for more than one workflow and their message is unclear, dojobase replies asking them to pick from a numbered list, then starts the job from their original message once they choose. A message it can't place gets a short 'not recognized' reply instead of guessing.

WhatsApp inbound in a workflow

A simple example of where this node sits in a flow.

WhatsApp inbound Text a keyword to start a job Email outbound Send report link

What you set up

  • Set a keyword senders can text (e.g. LOAN), and/or list the phone numbers of known senders who should route here automatically.
  • Share your dojobase WhatsApp number (and the keyword, if any) with the people who'll submit.
  • Wire the node into the rest of the workflow — attached files feed Extract just like an emailed document.

Common questions

Do senders need the app's number saved?

They just message your dojobase WhatsApp number. Known senders you've pre-registered route automatically; everyone else leads with a keyword.

What if the message could go to several workflows?

dojobase replies with a numbered menu and starts the job from the original message once the sender picks — their earlier message and its attachments are what run.