Skip to main content
This guide walks you through creating custom HTTP endpoints that execute action pipelines — without writing backend code.

Prerequisites

Building Your First Endpoint

1

Design Your Endpoint

Plan what the endpoint does:
2

Create the Endpoint

3

Test the Endpoint

Call your new endpoint:
Expected response:
4

Add Authorization

Use a condition expression to restrict access:
If the condition evaluates to false, the endpoint returns 403 Forbidden.
5

Monitor Execution History

Track how your endpoint is being used:

More Examples

Form Submission Endpoint

Accept form data and create a record:

Dashboard Data Endpoint

Aggregate data for a dashboard:

Troubleshooting

  • Verify the endpoint is enabled
  • Check the URL format: /api/v1/x/{path} (note the /x/ prefix)
  • Confirm the HTTP method matches (GET, POST, etc.)
  • Check path parameter syntax uses :param format
  • The condition expression evaluated to false
  • If auth_required is true, ensure you’re sending a valid auth token
  • Another endpoint with the same path and method already exists
  • Each (path, method) combination must be unique per account
Endpoints have a 30-second execution timeout. If your action pipeline is complex, consider:
  • Reducing query limit values
  • Simplifying filter expressions
  • Breaking complex logic into separate endpoints

Next Steps