TL;DR: The visual automation system in the TechnologyKSA dashboard builds workflows from a trigger and ordered steps. AbdoCode automates the system itself in two ways: it operates the dashboard through its agent browser and builds a workflow step by step with your approval, and it writes the services that receive webhook actions and connect workflows to your systems.
What is the visual automation system? A dashboard page where you create a workflow with a name and a trigger, add ordered steps — each with an action and settings — enable or disable it, and review a log of every run. No code required.
Workflow building blocks
- Trigger: one of ten — deal created, stage changed, won, lost, contact created, contact updated, company created, note added, email received, or manual.
- Steps: run in order, each using one of twelve actions.
- Status: enabled or disabled with one switch.
- Log: the result, success or error of every step in every run.
Settings of the most used actions
- AI insights: entity type and prompt.
- Owner approval: summary, requested action, risk level and time-to-live in minutes.
- WhatsApp: message text, or template name, language and parameters, plus an optional document URL.
- Webhook: URL, method, headers, body and timeout.
Method 1: AbdoCode builds the workflow in the dashboard, with your approval
- The agent opens the dashboard in its browser — you sign in yourself; it never enters your password.
- It reads the page and finds the create buttons and fields.
- It creates the workflow and adds the steps in order, asking for approval before each save.
- It leaves the workflow disabled and shows you a summary to review and enable yourself.
Method 2: AbdoCode writes the other side of the webhook
- Describe the goal: "a service that receives won-deal data and adds it to the invoice sheet".
- AbdoCode writes the service in a project on your machine and shows the files before saving.
- It runs and tests it with a sample request, reads the result and fixes errors.
- You put its URL in the webhook step:
POST, a secret signature header, the body and a sensible timeout.
Safe practices
- Build workflows disabled and test them with a manual run first.
- Put an owner-approval step before any customer-facing message in new workflows.
- Never put keys or passwords in webhook bodies; use a signature header the receiver verifies.
FAQ
Can AbdoCode control the automation dashboard on its own?
It works through its agent browser and asks for your approval on every impactful action; it does not sign in for you.
Do I need a developer?
Not to build workflows. Code is only needed for a service that receives a webhook — which AbdoCode writes with you.
