A button column in an Elbuz table: from an order or product row it opens a link or window, calls your server or a carrier API, or runs Flow.
When you need this:
- Track a parcel — the button opens the carrier's page with the waybill number from the row.
- Send an order to your server — a webhook, in one click.
- Create a waybill without code — via the carrier API; the number goes to an order field.
- Not every row needs it — a condition hides or disables the button.
Where to start: document list → menu → “Set up grid” → “Add new field” → “Button”.
What a table button can do
- Open a link or an Elbuz window — with row data in the address.
- Send an HTTP request (webhook) — row data via macros, credentials from the connections directory.
- Save the server response to a field — a number or a tracking link.
- Work in product, document and contact grids — and Flow in eight grids.
How to add a button to a table
For the orders table: document list → menu → “Set up grid” → “Add new field” → type “Button” → “Button name”. The “Button action” window opens right after the field is created; later you open it with the “Set up the button action” gear in this field's row in the same grid settings window.
How to set up the button action
The window has five steps:
- “What the button does” — “Open a link”, “Send an HTTP request (webhook)”, “Open an Elbuz window” or “Run a Flow scenario”.
- “Action parameters”. For a webhook — “Address (URL)”, “Method”, “Body type”, “Request body”, “Headers” (one per line, “Name: value”) and “Connection with credentials”: the login, password and token come from the external connections directory and aren't stored in the button. Row data goes into both the address and the body via macros: pick a field in the “Row fields” list and click “+” next to the input you need. For , values are escaped automatically.
- “How the button looks” — caption (macros work here too), icon, color.
- “When the button is active” — a condition on the row: leave it empty and the button is always active; for other rows you can show it as inactive or hide it.
- “Confirmation and response” — “Ask for confirmation” with the question text, plus “Path to the value in the response” (for example
data.tracking_url) and “Save into field”: the value from your server's response is written to a field of this record.
Where you can send a request and how often
- Address. The request is sent from the Elbuz server, not from the browser, so the address must start with http:// or https:// and point to the internet. Elbuz rejects localhost, local network addresses and names that can't be resolved with the message “Request address rejected:”.
- Limit. One user can click request buttons no more than 30 times a minute — after that you see “Too many clicks in a row, please wait a minute”.
- Log. Webhook and Flow scenario clicks are recorded in the “Operation log” (Account → Operation log), not in the document card history. Not recorded: “Open a link”, “Open an Elbuz window” and clicks Elbuz rejected because of the limit, permissions or the button condition.
How to test a button without breaking anything
The “Test” button first saves the settings and then sends a real request — with data from the newest table record that matches the button condition.
Your server receives it as a normal request, the click is logged and counts toward the 30-per-minute limit, and if “Save into field” is set, the value from the response is written to that real record. Test on a test address or when such a request won't break anything.
Which tables support webhooks and Flow
Webhooks and Flow work in the grids of catalog products, price list products, contacts, documents, document lines, categories, manufacturers and articles. In other grids the window shows “This grid supports only browser-side actions: open a link and open a window”.
If data must be sent on its own, without a click, use an automatic rule with the HTTP request command.
Scenarios
A button to track a parcel by waybill number
What to do. In the orders grid, add a field of type “Button” named “Tracking”. In “What the button does”, choose “Open a link”. In “Address (URL)”, paste your carrier's tracking page address, with the waybill number field macro in place of the number: pick the field in “Row fields” and click “+”.
What you get. The value is taken from the row where the button was clicked and URL-encoded automatically. To show the button only where the waybill number is filled in, set a condition in the “When the button is active” step.
Send an order to your own server
What to do. In the “Button action” window, choose “Send an HTTP request (webhook)”, enter the “Address (URL)” and method, and in “Request body” insert macros of the order fields you need from the “Row fields” list. Click “Save”.
What you get. The button appears as a column in the orders grid and sends the data of the row where it was clicked. Each click is recorded in the “Operation log”.
Create a waybill through a delivery service API and save the number
A typical example is a delivery service integration without programming: a button in the orders grid sends order data to the Nova Poshta API or another carrier's API to create a waybill, and saves the waybill number or tracking link from the response to an order field.
You define the request body format yourself, following the service's documentation — the automation is fully in your hands; the window has no ready-made templates for carriers.
What to do. Choose “Send an HTTP request (webhook)”, enter the service API address, the “Method” and the “Request body” with order field macros. Pick the access key in “Connection with credentials”. In the “Confirmation and response” step, fill in “Path to the value in the response”, for example data.tracking_url, and set “Save into field” to an order field.
What you get. After a click, the value from the response is written to this record. The waybill number is saved the same way: its path in the response and a separate order field for the waybill number.
What to do when the button doesn't work
| What you see | Why | What to do |
|---|---|---|
| “Request address rejected:” | the address points to localhost or the local network, or the name can't be resolved | enter an internet server address starting with http:// or https:// (limits) |
| “Too many clicks in a row, please wait a minute” | more than 30 request button clicks in a minute | wait up to a minute and click again |
| “This grid supports only browser-side actions: open a link and open a window” | webhooks and Flow don't work in every grid | check the list of tables or send the request with an automatic rule |
| The button in a row is inactive or missing | the row doesn't match the condition from the “When the button is active” step | change the condition or fill in the required field in the row |
FAQ
A webhook button says “Too many clicks in a row, please wait a minute”. What's the limit?
30 clicks of webhook and Flow scenario buttons per minute per user, including “Test”. The counter resets with the next minute. “Open a link” and “Open an Elbuz window” don't count toward the limit.
Can I send data to a server without clicking a button?
Yes, but that's not a button — it's an automatic rule with the HTTP request command: it fires on an event by itself.
Where can I see who clicked the button and when?
In the “Operation log” (Account → Operation log) — for webhooks and Flow scenarios. Clicks aren't written to the document card history.
Does the button store an API password or token?
No. The login, password and token come from the external connections directory via “Connection with credentials”; they aren't stored in the button itself.
Are there ready-made settings for Nova Poshta or other carriers?
No, the window has no ready-made templates for carriers. You define the request body format yourself, following the delivery service's documentation.
Where it is and who has access
- Add a button
- table grid → menu → “Set up grid” → “Add new field” → “Button”
- Change the action
- the “Set up the button action” gear in the field's row
- Prepare
- for a webhook — the request address and format of your server or the service's
You add the button in the grid where you need it, not in “Table settings”. Like “Progress bar”, it's a virtual field: it creates no column in the database, and you can't filter, sort or export by it.
Related topics
- For the big picture on custom fields — custom fields.
- If data must be sent on its own, without a click — automatic rules.
- If a colleague needs to see the button in the grid — grid settings.
