Skip to content
ReviewJalpi
Automations

No-code automations

Set up automated actions that trigger when reviews, surveys, messages, or listings change — no code or API key needed.

  1. Go to Automations and choose to start from scratch or pick a quick-start recipe (e.g., "Notify on a 1-star review"). Recipes install disabled.

  2. Pick a trigger event. Choose when the automation fires: new review, reply added, survey response, message received, or listing drift.

  3. Add filters (optional). Narrow down which events trigger the action — for example, only 1–2 star reviews, or only from Google. Leave empty to match all events.

  4. Choose an action. Set what happens:

    • HTTP POST — send data to a URL (e.g., Slack webhook, custom integration)
    • Email — send to a configured address
    • SMS — text a configured number
    • Add tag — auto-tag the review (review-based events only)
    • Create task — open a follow-up task (review-based events only)
  5. Fill in action details. Depending on your action, enter the webhook URL, recipient email, phone number, or tag name. Leave any optional fields blank if not needed.

  6. Enable the automation. Toggle it on. Your automation now runs whenever a matching event happens.

  7. View the runs log. Click any automation to see execution history and debug failed attempts.

The 6 quick-start recipes cover common workflows: alerting on negative reviews, tagging by source, NPS-based SMS, and listing drift notifications. Automations run on the same events as webhooks, so they're ideal if you don't have an external tool or API set up yet.

Tips

  • Recipes start disabled — fill in required fields (URL, email, tag name) before enabling to prevent empty actions from firing.
  • Filters use simple conditions: equals, not equals, contains, or comparison operators on numbers.
  • Each automation has one action; create multiple automations for multiple actions on the same event.
  • The runs log shows whether each execution succeeded or failed, with status codes and error details for troubleshooting.
Was this article helpful?