Connect Screpy to Zapier
Connect a Screpy REST API key to Zapier and build automated SEO workflows.
The Screpy integration for Zapier connects your Screpy projects, crawls, audit data, performance data, and uptime checks with other apps in a Zap. It uses a dedicated Screpy REST API key, so you can choose whether a Zap may only read data or may also change Screpy projects and start crawls.
Private integration availability
The Screpy integration is currently prepared for private Zapier testing. You need an invitation from Screpy until the public Zapier App Directory listing is available. This page will link to the public listing after release.
Before you connect
You need:
- A Screpy account with access to the projects used by the Zap.
- Access to the private Screpy integration in Zapier.
- A dedicated Screpy REST API key.
- A read-and-write key if the Zap will create, update, or delete projects or start crawls.
Read-only keys can use triggers, searches, list actions, comparisons, crawl data, Core Web Vitals, and uptime data. Screpy checks the key's current scope on every request.
Create the Screpy connection
- Sign in to Screpy.
- Open Settings > Connected Apps.
- Create a REST API key for the Zapier connection.
- Choose Read-only or Read and write based on the workflow.
- Copy the key when Screpy displays it. The key is shown only once.
- In Zapier, add a Screpy step and select Sign in.
- Paste the key into the API Key field and confirm the connection.
Zapier tests the connection against the authenticated Screpy account. If the test fails, create a new key and confirm that the key has not expired or been revoked.
Use a REST API key
Screpy MCP OAuth credentials cannot authenticate the Zapier integration. Create a REST API key in Connected Apps instead.
Choose a trigger, search, or action
| Component | Available workflows |
|---|---|
| Triggers | Start a Zap when a crawl is created or completes successfully. |
| Searches | Find a project, crawl, or exact crawled page. |
| Project actions | List, create, update, or delete projects. |
| Crawl actions | Start crawls and retrieve crawl status, summaries, pages, links, images, sources, and Quick Wins. |
| Comparison actions | Compare two crawls or two to five projects. |
| Account and health actions | Read account usage, Core Web Vitals, and uptime data. |
Project and crawl fields provide searchable choices. You can also map a project UID or crawl UID from an earlier Zap step.
Build a crawl-completion workflow
This example sends completed crawl data to another app:
- Create a new Zap.
- Select Screpy as the trigger app.
- Choose Crawl Completed.
- Select the Screpy connection and project.
- Test the trigger with a project that has a completed crawl.
- Add the destination app and map the crawl UID, status, and timestamps.
- Test the complete Zap before turning it on.
The trigger returns crawls from newest to oldest and uses the crawl UID as the stable deduplication value. A running crawl is not emitted by Crawl Completed until its status becomes successful.
Paginate and filter crawl data
List actions can return one API page or follow every opaque cursor with Return All. Use Starting Cursor only with a cursor returned by Screpy; do not edit or decode it.
Page, link, and image actions support structured filters. Add no more than 20 filters to one request. The In operator accepts comma-separated values or a JSON array with up to 100 values.
Keep the connection secure
- Use one API key for the Zapier connection instead of reusing a general-purpose key.
- Start with read-only access and replace the key only when the workflow needs a write action.
- Do not place the key in Zap fields, notes, screenshots, code, or shared documents.
- Revoke the key in Connected Apps when the Zap is retired or ownership changes.
- Use disposable projects when testing the permanent Delete Project action.