Skip to main content

Call an API step

Call Any API From Testimonial Automations

Some jobs need your own systems in the loop: look a customer up before asking, write a new testimonial into an internal tool, or tell a service that someone just left a review. From Pro, an automation can call any API with the method, headers and authentication you set, and later steps can use what comes back. No middleman tool required.

  • Pick between a signed webhook and a full API call
  • Plan the method, headers, credentials and body
  • Test on your own contact and read the log

Planning checklist

Plan the call before you add the step

Most failed API steps are planning gaps, not product problems. Fill these in with the target API’s own documentation open.

1. The job
2. The request
3. The response
4. Test and watch

Your ticks are saved in your browser only. No request is made from this page.

The problem, solved

Jobs the API step handles

  • Problem 1

    Approved testimonials should land in our own system

    Copying each approved quote into an internal tool by hand is slow and gets skipped.

  • Problem 2

    We need account data before we ask

    Whether to ask, and how, depends on facts that only live in your own database.

  • Problem 3

    The target API needs authentication

    Generic webhooks cannot carry the token or key an API insists on.

  • Problem 4

    We only need to say something happened

    A full API call is more setup than a notification needs.

  • Problem 5

    The call fails and nobody notices

    A wrong key or a changed endpoint can stop an automation quietly.

Signed webhook or API call

QuestionSigned webhookCall an API
Who decides the request format?StoryProofYou: method, headers, authentication
Do later steps need the reply?NoYes, the response can be used later
Typical useTell your own receiver an event happenedRead from or write to another system’s API
Setup effortLowerHigher: you plan the whole request

In StoryProof

Adding the step

Step 1 of 4

Choose the trigger

For example a testimonial being approved, or a contact being created.

Before you start

Before you rely on it

  • No named integrations

    The step calls an API you describe. It is not a built-in connection to any particular product, and it does not know any vendor’s API for you.

  • The target API’s rules apply

    Rate limits, authentication rules and data terms belong to the other service. Read them before you put the call on a busy trigger.

  • Tests are real calls

    A test runs every step for real, so a write call will create or change real data unless you point it at a sandbox.

  • Logs are short-lived

    Run history is kept for 30 days. Keep your own records in the target system if you need longer.

FAQ

Questions people ask

Short answers to what usually comes up next.

Do I need Zapier or Make to call an API?

Not for a direct call. The automation’s own API step sends the request with your method, headers and authentication.

Can a later step use what the API returned?

Yes. StoryProof says the response can be used in later steps of the same automation.

Which APIs can it call?

Any API you can describe with a method, URL, headers and authentication. Whether the call succeeds depends on that API accepting it.

Is a signed webhook the same thing?

No. A signed webhook tells a receiver an event happened, in StoryProof’s format. The API step is for when you need to shape the request and use the reply.

Still have a question? Ask the StoryProof team or book a demo.

Connect your own systems to testimonial automations

Call any API from an automation and use the response in the steps that follow.

Last updated 2026-11-18.