# Look up, remind and cancel requests

Find a request by your own External ID, read its status and answers, send the recipient a reminder, or cancel it, all from a Zap.

## Look up, remind and cancel requests

Four formbase actions work on a request that already exists. A typical Zap finds the request by the id your system knows it by, then reminds or cancels it.

<p>
  You need a <a href="/guides/zapier/connect">formbase connection in Zapier</a> and a request created with an External ID, as in{' '}
  <a href="/guides/zapier/send-a-request">Send a request from a Zap</a>. The same actions exist in the dashboard; see
  <a href="/requests/managing-requests">The Requests page</a>.
</p>

<h2 id="find-a-request">Find a request by External ID</h2>

<p>
  Your CRM knows the deal as <code>deal-1042</code>, not by formbase's request ID. Add a formbase action with the event{' '}
  <strong>Find Request</strong>
  and map your id into <strong>External ID</strong>:
</p>

<ul>
  <li>
    <strong>Form</strong> narrows the search to one form. Leave it empty to search the whole workspace.
  </li>
  <li>
    <strong>Include Test Requests</strong> is off by default, so a request created with Test Request on is not found. Turn it on while you
    build the Zap with test requests.
  </li>
  <li>
    If several requests share the External ID, the newest comes first, and Zapier uses it unless you change{' '}
    <strong>If multiple search results are found</strong>.
  </li>
</ul>

<p>The result is the whole request: its status, outcome, recipient, timestamps, and what you prefilled and locked.</p>

<h2 id="get-a-request">Read the answers with Get Request</h2>

<p>
  <strong>Get Request</strong> takes a <strong>Request</strong>: map the Request ID from a Create Request step, a Find Request step or a
  request trigger. It returns the request plus its link, and once the request is completed, the answers. Pick the request's form under{' '}
  <strong>Form</strong> so the answers are labelled with the question titles; without it they arrive under their field keys.
</p>

<h2 id="remind">Send a reminder with Remind Request</h2>

<p>
  <strong>Remind Request</strong> emails the recipient a reminder now. Scheduled reminders still go out as planned. It works when:
</p>

<ul>
  <li>the request is pending, has not passed its expiry date, and has a recipient email,</li>
  <li>the workspace is on Pro or Business,</li>
  <li>
    the last reminder went out at least ten minutes ago, and the request has had fewer than eight reminders in total. See{' '}
    <a href="/requests/invitations-and-reminders#manual">Chasing someone now</a>.
  </li>
</ul>

<p>A test request is never reminded.</p>

<h2 id="cancel">Withdraw a request with Cancel Request</h2>

<p>
  <strong>Cancel Request</strong> withdraws a pending request. The link stops working, and the recipient sees a withdrawn notice instead of
  the form. Fill in <strong>Reason</strong> to record why: it stays on the request and is carried by the
  <a href="/guides/zapier/request-outcome">Request Canceled</a> trigger, so another Zap can tell your team.
</p>

> ℹ️ **Only pending requests can be canceled**
> <p>
>     A completed, expired or already canceled request stays as it is, and the step fails with an error such as{' '}
>     <em>This request is already canceled and cannot be canceled.</em>
>   </p>

<h2 id="next">Next</h2>

<div class="not-prose grid gap-3 sm:grid-cols-2 mb-8">
  - [All guides](/guides/overview)
  - [The Requests page](/requests/managing-requests) — The same actions in the dashboard.
</div>