Notification in
Relay events from an app
Notification in listens for event alerts relayed from another product you run, like your own customer app, and turns each alert into a job. It lets a workflow react the moment something happens, for example texting or messaging the person involved.
How it works
Say you operate an app where customers sign up, book, or hit a milestone. When one of those moments occurs, your app can send a small heads-up to this node. That heads-up starts a job, and your workflow decides what to do about it.
The point is reaction without anyone watching a screen. An event fires, dojobase catches it, and the workflow can reach back out through a text, a WhatsApp message, or a notification, closing the loop automatically.
Unlike a plain file upload, nothing is dropped in by hand here. The trigger is an event coming from software you already run, so the workflow keeps pace with your app in real time.
Common use cases
Real situations where this node earns its place in a flow.
Relay events from an app
Receive push events from a connected product (a new match, a status change) and turn each into an outbound message.
Fan an event out to a person
When something happens in one app, relay it to the right recipient on the right channel, whether SMS or WhatsApp.
Notification in in a workflow
A simple example of where this node sits in a flow.
What you set up
- Connect the app that will relay its events to this node.
- Decide which events should start a job and which to ignore.
- Map the event details your later steps need, such as who to contact.
Common questions
What kind of events can trigger this?
Whatever your own app chooses to relay, such as a new signup, a booking, or a status change. You decide which ones start a job.
Can it reply back to the customer?
Yes. Pair it with a message node like SMS out or WhatsApp out so the workflow can respond automatically.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
sharedSecretreqSecret shared with the source app, used to verify the HMAC over the inbound event body.
Type: string
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "notification-in",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "notification-in",
"kind": "input",
"title": "Notification in",
"subtitle": "Relay events from an app",
"config": {
"sharedSecret": ""
}
}
}