Custom Actions in Adalo let you connect your app to external services like Zapier, enabling automation without coding. Zapier supports over 5,000 tools, allowing your app to trigger workflows (like sending emails or updating records) or respond to external events. To get started, you'll need an Adalo Professional Plan or higher for Custom Actions and a Zapier account.
Key Steps to Integrate Adalo with Zapier:
- Prepare Your App: Ensure your Adalo app has collections with test data and API access enabled.
- Set Up Custom Actions: Use a button or trigger component in Adalo to send data to a Zapier Webhook using POST requests.
- Build Zaps: Create workflows in Zapier by setting Adalo as a trigger or action, then map fields between tools.
- Test and Troubleshoot: Validate connections using tools like Postman and Zapier's testing features. Fix errors like incorrect data formatting or missing records.
Quick Tips:
- Use Magic Text to dynamically insert values into JSON requests.
- Custom Actions apply across all apps in a team, so test thoroughly before making changes.
- On Zapier's free plan, updates sync every 15 minutes.
By integrating Adalo and Zapier, you can automate repetitive tasks, streamline workflows, and connect your app to essential tools like Gmail, Slack, or Google Sheets.
Adalo Zapier Integration Workflow: 4-Step Setup Process
Adalo Custom Actions Tutorial - Zapier Webhook
Preparing Your Adalo App for Zapier
Get your Adalo app ready to connect with Zapier, whether you're using database triggers or more advanced Custom Actions.
What You'll Need Before Starting
Before diving in, make sure you've got an active Adalo account and a Zapier account. Both platforms should be open and ready to go. Your Adalo app should already exist and include at least one collection (database table) with some data. Without test records, you'll hit a roadblock during the integration testing stage.
The plan you’re on will determine what features you can use. Basic database triggers work on all plans, including the free one. However, Custom Actions - like those initiated by button clicks - require at least a Professional Plan. If you're working with external automations, you'll need a Team or Business Plan to access the API Key.
It’s helpful to have a good grasp of Adalo Actions, Magic Text, and database fundamentals. Planning to use Custom Actions with webhooks? You’ll need to configure HTTP methods (usually POST), API endpoint URLs, and headers like Content-Type: application/json. Testing your API endpoint in Postman before integrating is a smart move.
Turning On API Access in Adalo
For straightforward integrations, Adalo's built-in Zapier connection handles API access automatically. Just go to Action > New Integration > Services and select Zapier from the options.
If you’re setting up a Custom Action to send data to a Zapier Webhook, the process changes slightly. On a compatible component - like a button (note: form submission buttons don’t support Custom Actions) - choose Add Action > Custom Action > New Custom Action. Name the action, set the method to POST, and enter your Zapier Webhook URL. Then, add headers, define dynamic inputs (e.g., User Email, Task Name), and build your JSON body using Magic Text.
"Connections triggered outside of Adalo require use of the Adalo API Key which is available on the Team and Business plans."
- Adalo Help Center
One key point to remember: Custom Actions are saved at the team level, not the app level. This means any edits you make to a Custom Action will apply across all apps where it’s used. This setup is great for agencies and teams managing multiple apps but might require recreating actions if your projects have different needs.
Once your app and API access are ready, you can start building and testing your Custom Actions in Adalo.
Building Custom Actions in Adalo
Once your app and API access are ready, it’s time to create the Custom Action that pushes data from Adalo to Zapier. This involves setting up a webhook connection and formatting your app's data into the JSON structure Zapier requires.
Setting Up the Webhook URL
Start by selecting the trigger component in your app, like a button. In the Click Actions panel, choose Custom Action > New Custom Action. Give your action a clear, descriptive name. Set the HTTP method to POST, which is commonly used for sending data to webhooks.
Next, copy the webhook URL generated by Zapier when you create a "Catch Webhook" trigger. Paste this URL into the API Base URL field in Adalo. Then, click +Add Header, enter Content-Type as the Name, and application/json as the Value. This tells Zapier to expect JSON-formatted data.
Add inputs for each variable you need to send, such as User Email, Order ID, or Task Name. For each input, assign a label, select the appropriate data type (Text, Number, or Date/Time), and provide a realistic example value. These examples help test the connection later.
Mapping Data Fields to JSON Format
In the Body field, structure your data as a JSON object using the format {"key": "value"}. If you’re including multiple parameters, separate them with commas, like this: {"email": "value1", "orderID": "value2"}. Be careful not to leave a trailing comma after the last parameter.
Use Magic Text to dynamically insert values into the JSON body. Wrap text inputs in double quotes, and format any date or timestamp values correctly - use YYYY-MM-DD for dates or 2022-07-04T02:00:00Z for date and time in ISO 8601 format.
When the JSON body is ready, run a test request. Check Zapier to confirm the data is being received correctly. Save any response fields as outputs by clicking +Add Item in Adalo. To review the returned data, use the Show Full Response option. If everything looks good, save the outputs for use in later steps of your app's workflow.
With the JSON setup tested and working, you’re ready to build Zaps in Zapier and integrate them seamlessly with your Adalo app.
Creating Zaps with Adalo
Once your Custom Action is set up and tested, you’re ready to create Zaps in Zapier. This lets you connect Adalo with over 5,000 services and platforms, like Slack, Google Sheets, and Airtable. This is where automation shines - turning app data into actionable workflows.
Setting Up an Adalo Trigger in Zapier
Adalo triggers are activated by database changes, not by button clicks. You have two main trigger options: New Record (when a new record is added) and Updated Record (when an existing record is modified).
To get started, create a new Zap and select Adalo as your trigger app. Then, choose either New Record or Updated Record and connect your Adalo account. After that, pick the specific App and Collection you want Zapier to monitor.
"The collection that you use to trigger your Zap should have at least 1 record for Zapier to test the Trigger during setup." - Adalo Help
If you want a Zap to run only when a specific button is pressed (instead of triggering on any database change), use the Custom Action webhook method you set up earlier. Note that on Zapier’s free plan, it checks Adalo for updates every 15 minutes.
Once your trigger is configured, you can move on to adding actions to your Zap.
Adding Actions to Your Zap
With your trigger in place, it’s time to define what happens next. Click Add Action and choose your destination app - this could be Gmail for sending emails, Google Sheets for updating a spreadsheet, or Slack for posting notifications. Then, select the specific action event, like "Send Outbound Email" or "Create Spreadsheet Row".
Zapier will display sample data from your Adalo app, helping you map fields accurately. For instance, if you’re sending an email, you might map the User Email field from Adalo to the recipient field in Gmail. You could also include dynamic data, like an Order ID, in the email body.
Once everything is mapped, give your Zap a clear name, test the workflow to ensure it works as expected, and then toggle it On. Your Zap will now run automatically based on the trigger conditions.
| Trigger Method | Trigger Event | Adalo Plan Required | Best Use Case |
|---|---|---|---|
| Standard Trigger | New Record Created | All Plans (including Free) | Syncing new signups to a mailing list |
| Standard Trigger | Record Updated | All Plans (including Free) | Updating a spreadsheet when a status changes |
| Custom Action | Webhook Sent | Professional and above | Triggering a specific workflow from a button |
sbb-itb-d4116c7
Testing and Fixing Issues
Thorough testing is essential to ensure your Adalo-Zapier integration works as intended.
Before activating workflows, use Adalo's test request feature to verify the connection and check the JSON structure. Click "Show Full Response" to review the returned JSON and identify any error codes. Testing each individual request ensures that all data points are accurate.
Running Test Requests
Start by testing your API endpoint in a tool like Postman to validate the URL, headers, and JSON body. Once everything checks out, switch to Adalo and use its test request feature to confirm the connection. If you’re working with Zapier Webhooks, use the "Test Trigger" option in Zapier to view the specific fields and values being transmitted.
When editing or re-testing a Custom Action in Adalo, the API response structure refreshes, which clears previously mapped outputs. You’ll need to manually re-add these mappings after each test.
If you encounter errors during testing, refer to the troubleshooting steps below.
Fixing Common Problems
One frequent issue is 500 errors caused by incorrect data formatting. To avoid this, ensure the following:
- Dates are in the YYYY-MM-DD format.
- Date & Time values follow ISO 8601 formatting (e.g., 2022-07-04T02:00:00Z).
- Boolean values are lowercase (true or false).
- Numbers are clean - no symbols, currency signs, or letters.
If a Custom Action test fails, use "Show Full Response" to locate specific error codes. For authentication errors, double-check that there’s a space between "Bearer" and your API key in the Authorization header. Additionally, Zapier triggers require your Adalo collection to have at least one record for the "Test Trigger" step to function properly.
| Data Type | Required Format | Common Mistake |
|---|---|---|
| Date | YYYY-MM-DD | Using MM/DD/YYYY or DD/MM/YYYY |
| Date & Time | 2022-07-04T02:00:00Z | Missing the "T" or "Z" |
| True/False | true or false | Using "True" or "FALSE" |
| Number | 1234.56 | Adding symbols or formatting |
Keep in mind that Custom Actions are tied to your team and require a Professional Plan or higher. Changes to a Custom Action will affect all apps within your team where it’s used, so it’s crucial to test thoroughly before making updates to shared actions.
Launching and Managing Your Workflows
Once your workflows have been thoroughly tested, it's time to move them into production. Keep in mind that Custom Actions impact every app using them. To avoid potential conflicts, it's a good idea to re-create Custom Actions for each individual app. Use clear naming conventions - like appending the app name - to keep things organized and easy to manage.
When working with Zapier triggers, double-check that your Zap is connected to the correct Adalo app and collection. By default, standard Zaps trigger on any database change, such as a New Record or Updated Record. If you need more precise control, consider using a Custom Action to hit a Zapier Webhook. This method lets you trigger workflows from specific buttons or actions rather than every database update. Keep in mind that Webhook workflows require an Adalo Professional Plan or higher.
Before going live, ensure all Magic Text inputs are properly mapped to production data fields. If your external service uses different API endpoints for testing and production, update the API Base URL to match the production environment. Additionally, use the YYYY-MM-DD format for dates and follow the ISO 8601 format for Date/Time values (e.g., 2022-07-04T02:00:00Z) to avoid errors.
Finally, configure your Zapier triggers to work exclusively with production data.
Moving Workflows to Production
Ensure that your Zap is correctly linked to the production app and collection. Run a final test request to refresh responses and manually re-add outputs if necessary. For workflows triggered by database changes, confirm that the production collection has at least one record.
If you're on an Adalo Free plan, monitor your record limits closely. Any records created or updated through Zapier integrations will count toward these limits. Similarly, if you're using Zapier's Free plan, remember that it checks for new Adalo data every 15 minutes, so there may be a slight delay in triggering actions.
Tracking and Improving Performance
Once your workflows are live, ongoing monitoring becomes crucial. Zap Actions are logged as App Actions in Adalo, so tracking these logs will help you manage plan limits and spot unexpected spikes in activity. Use the "Show Full Response" feature in Adalo to view detailed error codes and the full JSON structure for troubleshooting.
It's also essential to keep an eye on Zapier's task history. Be aware that some API errors might mark tasks as completed even if they fail silently. This means you'll need to manually inspect logs to catch any hidden issues. As your app scales, upgrading to a paid Zapier plan may be worth considering. Paid plans offer faster processing times and advanced features that are better suited for high-volume environments.
Conclusion
Integrating Adalo with Zapier through Custom Actions opens the door to thousands of external services, cutting down on manual tasks. With precise triggers, you can automate specific actions, giving you complete control over how your integrations function.
Once you've set up your trigger, the process is straightforward. You'll need to enable API access, configure webhooks, map your data, and thoroughly test everything. Keep in mind, this feature requires an Adalo Professional Plan or higher. The result? A seamless two-way data flow that not only sends information out but also retrieves responses instantly. This allows you to handle tasks like sending messages, updating your CRM, or triggering SMS notifications - all directly within your app.
As you build workflows, remember that Custom Actions are shared at the team level, meaning any changes will affect all connected apps. To avoid confusion, stick to clear naming conventions and test extensively. Regularly check Zap task history and Adalo logs to troubleshoot any issues quickly.
Start small with workflows like sending a welcome email or adding events to a calendar. Once you're comfortable, you can scale up to more complex integrations. Adalo’s visual builder combined with Zapier’s vast app library lets you automate nearly any repetitive task - no coding required. This blend of automation and simplicity showcases the true potential of Custom Actions and Zapier working together.
FAQs
What do I need to set up Adalo with Zapier?
To connect Adalo with Zapier, you'll need both an active Adalo account and access to Zapier. Ensure your Adalo app is set up to handle custom actions or supports Zapier integrations. Preparing your app’s data and actions in advance will make the automation process smoother.
Before diving in, double-check that you have the right permissions in Adalo to create and manage custom actions. Also, confirm that your Zapier account is authenticated and linked to Adalo. Following Adalo's setup guidelines can save time and help prevent any hiccups during the integration process.
How do I fix common issues with Custom Actions?
To address common issues with Custom Actions, start by pinpointing the problem and comparing what’s happening to what you expect. Ask yourself questions like, Where is the data coming from? or What could be triggering this error? These can help you zero in on potential causes.
Custom Actions frequently rely on API requests, so it’s crucial to double-check your API endpoints, request parameters, and authentication details. Pay close attention to any error messages - they often offer valuable hints. If the API for an external service has been updated, ensure your configuration aligns with those changes.
Make changes incrementally - adjust one thing at a time and test after each tweak to identify the root cause. If the issue continues, confirm that your setup matches the latest API documentation. When in doubt, don’t hesitate to contact support for further assistance.
What are the advantages of using Custom Actions in Adalo?
Custom Actions in Adalo open up a world of possibilities by letting you connect your app to third-party services through APIs. Whether it's updating records, triggering external workflows, or linking to platforms like Zapier, these actions let you handle it all directly within your app.
By automating tasks like sending notifications or updating databases, Custom Actions simplify operations and cut down on manual work. They also add extra functionality to your app, making it more flexible and capable - all without needing deep coding expertise.
Related Blog Posts
