Adalo’s Test really sends messages: before connecting a notification button to your business

When connecting a notification API with Adalo’s Ada, first define the test destination, sample variables, and expected response. Test in Custom Actions makes a real request; even after a successful preview, check the external result before putting it into a production workflow.

Source: ada-help.adalo.com
November 7, 2026
4 min

Adding a “Notify the person responsible” button to an internal request app may look like one extra operation. What you actually need to deliver is a complete chain: what the user submits, where the message goes, what response comes back, and how the interface explains a failure. Adalo’s Ada can modify an app from natural-language instructions and connect external APIs through Custom Actions. But its official documentation explicitly says that Test in the action editor sends a real request.

For a first notification integration, prepare a destination used only for testing before asking Ada to connect the interface. The following analysis uses a notification sent after a request is submitted as its scenario. The validation sequence is based on the new Ada’s official documentation; no app was run and no message was sent.

Specify the destination, not just “add a button”

Start with one complete action: in a test app, the user enters a fictional request description, clicks a button, sends that description and a test record ID to the designated test destination, and then sees success or failure. Do not add approvals, payments, and record deletion to the same first attempt. Ada’s building guide recommends starting with one coherent change, making it easier to see whether the new feature has altered existing navigation or data behavior.

When naming the action, also describe its trigger and purpose. “Notify the test channel about the current test request,” for example, is easier to check than “Process the request.” The official Custom Actions documentation says Ada reads an action’s description to decide when and how to call it. If the description is unclear, even a working API connection may end up attached to the wrong place in the interface.

A test channel is simply the choice for this scenario; not every service offers a sandbox. If the receiving service has no isolated environment, first prepare an authorized test destination that will not disturb real customers. If that is not possible, keep the interface as a draft and do not connect production notifications.

Sample values are inputs to a real operation too

Use the receiving service’s API documentation to enter the method, address, and required variables, and check that all sample values are fictional. Pay particular attention to the target channel, email address, or record ID. Do not assume they will go unused just because they sit in an “example” area.

Ada’s documentation explains that Test executes the request with these sample values and, on success, keeps a response sample to help connect returned fields to the interface. It is not merely a format-checking button. Before testing, write down what you expect: which message should appear at which destination, and what the app should display. Afterward, inspect both the external result and the interface. An API success response with a notification sent to the wrong place is still a failed test.

Put keys in the dedicated Secrets configuration, not in prompts, ordinary input fields, or sample messages. The official documentation says these keys are encrypted on the server, injected when a call is made, and not distributed with the app. That mechanism does not decide which business data you may send to an external service; the outgoing fields still need individual review.

Follow the whole path beyond the button

Once the action test passes, walk through the preview from entering the request page rather than merely clicking the new button. Then check whether messages are understandable with empty input, while loading, and when the API fails. The official preview guide calls for checking the full user journey and these states; it does not guarantee that the generated interface already handles every situation correctly.

Use three acceptance questions for the notification chain: does a success message correspond to actual receipt at the destination; does a failure still incorrectly show “sent”; and do repeated clicks produce duplicate notifications the team cannot accept? If duplicates would have business consequences, ask the API owner to confirm how they will be prevented. Do not assume Ada or the receiving service already handles this automatically.

After each completed change, give the version a recognizable name, such as “Test notification chain checked.” Ada’s documentation says completed changes can be saved as versions that can be named and restored. Restoring an app version should not be treated as a way to retract messages already sent externally. Once a notification has left the app, handling it requires the receiving system’s own mechanisms.

Finally, separate preview acceptance from production acceptance. Production may use different destinations, keys, and permissions, so check the complete chain again with authorized test content after switching. Adalo’s official guidance also calls for testing the published experience separately. Only when the interface feedback matches the external action is the button ready for real business users.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:ada-help.adalo.com