Create a custom HTTPS connection

Connect your own business API by defining the requests Waaru may send and the response fields your workflows may use. This guide is for someone who understands that API’s authentication and HTTP requests. For a supported app with a ready-made connector, start with Integrations.

An action’s inputs are the values it needs. Its outputs are the values it returns. A typed field requires a specific format, such as text, a number, or a list. Custom connections define these actions; they do not run arbitrary scripts.

Create and verify the connection

1. Open Settings > Integrations > Custom connections.
2. Create the connection with a descriptive name and the approved HTTPS base address.
3. Choose a supported authentication method and enter its credentials only in the protected credential controls.
4. Choose WhatsApp number access. The default Selected numbers option requires at least one number; later connected numbers do not automatically gain access.
5. Configure a safe GET verification method. It should check access without creating, deleting or changing records.
6. Select Verify and connect and correct connection or authentication errors before using the connection. This verifies the safe GET method, not every action you add later.

Use the public HTTPS service you intend to access. The connection's network restrictions still apply; do not use private-network addresses or redirect tricks to work around a rejected destination.

Define a method

Give each method a name that states its operation. Choose its supported HTTP method and path, declare typed inputs, and select the response fields the workflow should receive. Expose only the data required by the next step.

For a read method, test a known permitted record and a missing record. For a write, use controlled test data and inspect the final source-system state. Confirm that success, failure and uncertain outcomes are interpreted correctly.

Select Add action to save the method. New actions become Active immediately. Test through a controlled workflow before publishing customer traffic. Use Disable when the action must not be available; Enable restores a disabled action. Choose it in connected actions only where the current editor offers it. Defining a custom method does not remove workspace, number or action permissions.

Change credentials or methods safely

Credential replacement requires safe GET verification. Recheck dependent actions after changing authentication or account access.

Editing a method creates a revision. Review the changed inputs and selected output fields in each dependent workflow, then validate and republish intentionally. Preserve a recovery path when an external operation can succeed but its response is interrupted.

If you cannot determine whether a write completed, inspect the source system before retrying it. Record the action, time and safe error details for support, without including the credential or customer payload.