Skip to content

Automation · Customer service and scheduling

Support the developer integrating your API on WhatsApp, with your Postman collection

An AI agent answers whoever integrates your API on WhatsApp with the collection, environment and mock your team keeps in Postman.

How do I answer, on WhatsApp, the questions of the developer integrating my API?

When a client's developer writes on WhatsApp because they do not know which endpoint to use or what their call is missing, the Met reads the workspace, collection and environment your team keeps for that API in Postman. It replies with the documented method, path and description, explains which variables the test environment expects without sharing secrets, and shares the mock server URL so they can test without touching production. It leaves a note on the contact with what they asked. If what they report looks like a bug in your API rather than a question, it hands the conversation to someone on the team.

What starts it

When the customer writes

It starts when a client's developer writes on WhatsApp with a question about your API. There is no trigger to configure: the Met assigned to the line handles it in that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Technical support Met for those integrating your API

Customer service team

This is not a named, seeded Met. It is the Met that handles your product's support line, with Postman connected: its work ends when the developer has the endpoint, variables and mock they needed, or when someone on the team takes the case.

Run by the customer support Met

Channels: WhatsApp

What you need connected

6 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Check the API's workspace

    The Met gets the workspace your team set in the skill and checks its visibility. If it is public, anyone can open it; if it is partner, only invited people can. That tells it whether it can suggest the developer look on their own.

  2. 2

    Find the endpoint in the collection

    The Met gets the API collection, first as its lightweight map and, if it needs the detail, the full collection. It replies to the developer with the method, path and description your team documented for that request.

  3. 3

    Explain the test environment

    The Met gets the test environment and explains which variables the API expects, such as the base URL. If the environment stores keys or tokens, the skill tells it not to share their values.

  4. 4

    Share the mock URL

    The Met gets the collection's mock server and shares its URL, so the developer can test their integration against example responses before calling your real API.

  5. 5

    Log it on the contact

    The Met adds an internal note to the contact with what the developer asked and the request it pointed to, so your team sees which questions keep coming back in the documentation.

  6. 6

    Escalate when it is an API bug

    If what the developer reports is not a question but a response that does not match the documentation, the Met escalates to someone on the team with the reason and leaves the conversation.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

Yes, if the skill includes the identifiers of each collection and tells the Met which one to use based on what the developer asks.

No. This procedure does not invite anyone or change the workspace's visibility; it only tells the developer whether the workspace is public or partner.

The Met does not make it up: it says it is not documented, leaves the note on the contact and, if needed, hands the conversation to someone on the team.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.