Troubleshooting Custom Actions

If your Custom Action is not working as expected, or Outputs seem to disappear, the issue is often related to how the action was saved or tested. Below are common problems, their causes, and how to fix them.

---

Best Practices

• Always re-test and re-add Outputs before saving any changes.

• Save immediately after adding Outputs.

• Use clear, descriptive names for each Output.

• Keep your responses simple and limited to the data you need.

• If you plan to reuse Custom Actions across apps, duplicate them instead of editing the shared version.

---

Outputs Disappear After SavingCustom Action Does Not Return DataNo Outputs Available in Action Flyout“Nothing Available” When Mapping OutputsOutputs Appear but Do Not PersistCustom Action Works in One App but Not AnotherBoolean or Array Data Not ShowingTimeout or Large Payload Error

---

Learn More

• Creating Custom Actions in Adalo

• Using External Collections

• Connecting Adalo with Make or Zapier