# Return an order status from your business API

Receive an order identifier, extract a selected status from a connected business API, and return a compact response.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## The business outcome

Receive an order identifier, extract a selected status from a connected business API, and return a compact response.

This is an importable starter using Chatigram’s current native nodes. It needs destination-specific setup; it does not imply a dedicated connector for every CRM or ERP brand. Check your software’s API documentation and permissions.

## Before you begin

Set the endpoint secret, order-system API URL, authorization, expected order identifier, and response extraction path. Add the access checks your use case requires.

The reserved example.invalid endpoint is deliberately non-working. No real customer data, account credentials, or private resource identifiers are embedded. Keep the workflow disabled until setup is complete.

## Configure the workflow

1. Set a fresh secret on the workflow endpoint. The example is not a public customer identity or order-ownership verification system.
2. Configure orderLookup against the read endpoint your order system provides and map its order identifier.
3. Select only the status field your caller needs. The example deliberately does not forward the full order, address, or payment response.
4. Add the validation and access checks appropriate to your caller before exposing real order information.

## Test the outcomes

- Test an authorized order, a missing order, and an unavailable API response.
- Check that an empty status is not presented as a valid delivery update.
- Confirm the caller receives only the intended fields.

Open [Workflow Activity](/workflows/activity/) after the test. Import validation checks the definition; it does not prove a remote API accepted the business operation. Check the destination before repeating a send or write.

## Make it your own

Put reusable public settings in [Properties](/workflows/properties/), configure credentials through the protected connection options, and keep explicit error paths. Explore [App Connections](/integrations/overview/) for existing provider-specific actions you can substitute through the editor.

Use the copy controls below for the complete workflow or its first node. The diagram and downloads come from the same definition. Use Share recipe to share the guide’s public address.


## Copyable workflow

https://docs.chatigram.com/examples/order-status-api.json