Information Technologies · No-code automations and approvals
No-code automations and approvals: let the system notify, create and ask for sign-off for you
With Remotjob you define rules of the kind “when this happens, if that is true, then do this” across your orders, invoices, purchases, leads, inventory, subscriptions and help desk cases, without writing a line of code. And multi-level approvals live in a single engine, with deadlines, escalation and delegation when someone is away.
When everything depends on someone remembering, something gets missed
An overdue invoice nobody chases, a new lead with no first reply, a large purchase order waiting for weeks because the approver is on vacation. Remotjob turns those mental reminders into rules that run on their own, and approvals into a clear path with owners, deadlines and a record of every decision.
From idea to a working rule, in six steps
Everything is built from a single Settings screen, with a closed catalog of options that the system validates for you.
1
Start from a template or describe it
Pick a one-click template (notify the salesperson when an order is confirmed, remind about an overdue invoice, create a task for every new lead) or write what you want in your own words and the AI builds the rule for you to review.
2
Define when it triggers
Choose the record type and the moment: when it is created, when its status changes, when a field changes or when a date arrives, a few days before or after.
3
Add the conditions
Say in which cases it applies: up to ten conditions on the record’s data, where either all of them or just any one of them must be met.
4
Choose what happens
Notify in the app or by email, create a task with a due date, change an allowed field, send a signed webhook to your systems, request an approval or ask the AI to draft or classify.
5
Activate it and trust the engine
The rule runs on its own every few minutes, with caps so it never chains endlessly or repeats actions on a retry.
6
Review the log and the approvals
Every run is recorded with its result, and approval requests reach the inbox of whoever must decide, level by level.
What is included
“When, if, then” rules across seven record types
Shop orders, sales invoices, purchase orders, CRM leads, inventory transfers, subscriptions and help desk cases, with triggers on creation, status change, field change or a date.
Describe your automation, with AI
You write what you want in plain language and the AI builds the rule from the available data. It never invents recipients or addresses, and the rule opens inactive, with its explanation and warnings, until you save it. It uses AI credits.
Templates and a run log
One-click templates for the most common cases and a log that shows every time a rule ran, what it did and whether anything failed.
Signed webhooks to your systems
A rule can notify another system of yours with a digitally signed message, with a record of every delivery, automatic retries, manual resend and a pause if the destination keeps failing.
One multi-level approval engine
Policies for purchase orders, supplier invoices, expense reports, project hours and order discounts, with one or several levels in sequence or tiered by amount, and “any of” or “all” at each level. A preview shows which levels an amount would go through.
Deadlines, reminders, escalation and absence delegation
Each level can have a deadline: when it expires, the approver is reminded or the request escalates to another person, a role or the administrator. Whoever is away declares their dates and a delegate decides on their behalf, on the record.
Notices and tasks in “My activities”
Each person sees in their profile the tasks and notices assigned to them and the approvals they must decide, with a pending counter in the header. Administrators also see the whole team’s activities.
Its own process map, connected to your other modules
The module comes with its process map: what your team does, what the system does and what the AI does. It links with Shop, Invoicing, Procurement, Expenses, Projects, CRM, Inventory and the Help Desk, and what is decided and recorded here becomes knowledge that Company Brain and People Chat return as answers to decide on.
Automate with control: every rule and every decision leaves a trace
A badly set automation can create noise or damage, so the engine works with a closed catalog, validates every rule before saving it and keeps a person in charge of whatever gets activated.
Role-based permissions: some roles can view automations, others manage them and others respond to approvals.
Each organization sees and automates only its own data; notices only reach active members of your organization.
Only the fields, conditions and actions in the catalog can be used, and the system validates them on save; the AI does not invent recipients or addresses, and what it suggests is reviewed before it is activated.
Caps protect your operation: a limit on chained rules, a maximum number of runs per hour for each rule and protection against repeated actions.
Nobody approves their own request or two levels of the same request, unless the policy expressly allows it; every decision records who, when and on whose behalf.
A run log and a level-by-level trail of each approval, with its reminders and escalations.
What it is and what it is not
It is a rules engine with a closed catalog: seven record types and defined actions. It is not a free programming language; if you need something else, it is requested as an improvement to the platform.
A rule can only change the fields the catalog marks as editable, and the AI drafts or classifies but does not decide for you.
The webhook sends and records the signed notice; what your other system does with it depends on that system.
Multi-level approvals are switched on with one policy per record type; without a policy, each module approves as usual. Deadlines in business days count Monday to Friday, without holidays.
Video · 1 min 5 s
Automations and approvals, explained in a short video
Link copied
Link copied
English narration with Spanish subtitles.
How it works
Learn to use it in minutes
Link copied
Link copied
Your process, your rules, no programming · 25s
Frequently asked questions
Do I need to know how to code to create an automation?
No. You build the rule by choosing the record, the moment, the conditions and the actions from lists, or you start from a template. You can also describe it in your own words and the AI sets it up for you to review.
Can the AI activate a rule on its own?
No. A rule suggested by the AI opens inactive, with an explanation and warnings, and is only saved if a person presses “Save”. If what you ask for is not a rule for your company but a new platform feature, it builds nothing. Using the AI consumes AI credits.
How do multi-level approvals work?
You define a policy per record type: it can have one or several levels, in sequence or tiered by amount. Each level states who approves (people, roles or a permission) and whether one approval is enough or all must approve. The request moves level by level and the requester gets a notice with the decision.
What if the approver is on vacation or does not respond?
You can set a deadline per level: when it expires, the system reminds the approver or escalates the request to another person, a role or the administrator. Whoever is away can also delegate to someone for those dates, and the decision is recorded as “approved by X on behalf of Y”.
Can I connect the automation to my other systems?
Yes, with signed webhooks: a rule sends a digitally signed message to your system’s address, so you can verify it comes from Remotjob. Every delivery is recorded, with automatic retries and the option to resend it.
Let the repetitive run itself and give the important an owner
Tell us what you would like to automate or which approvals get stuck today; we will show you how it would look inside Remotjob.
