crontap-supabase-edge-function-cron

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Schedule a Supabase Edge Function

调度 Supabase Edge Function

Use Supabase

pg_cron

for SQL-only database maintenance. Use this pattern when the recurring unit is an HTTP Edge Function and an external scheduler is desired.

对于仅涉及 SQL 的数据库维护，使用 Supabase

pg_cron

。当重复执行单元是 HTTP Edge Function 且需要使用外部调度器时，采用此模式。

Prerequisites

前置条件

Before using the required tools, check whether they are available. If any are missing, stop and offer the user exactly two choices:

Connect Crontap MCP at
```
https://mcp.crontap.com/mcp
```
. MCP access works on every Crontap tier.
Configure
```
$CRONTAP_CLIENT_ID
```
and
```
$CRONTAP_API_KEY
```
for the raw API. Raw API access requires Ultra.

Do not silently choose a path or continue until the user selects one.

Deploy the function before creating its schedule.
Make the function idempotent for one logical period.
Protect it with a dedicated server-side cron secret.
Never send a Supabase service-role key to Crontap.

在使用所需工具前，检查它们是否可用。如果有任何缺失，请停止操作，并向用户提供恰好两个选项：

在
```
https://mcp.crontap.com/mcp
```
连接 Crontap MCP。所有 Crontap 套餐均支持 MCP 访问。
配置
```
$CRONTAP_CLIENT_ID
```
和
```
$CRONTAP_API_KEY
```
以使用原生 API。原生 API 访问需要 Ultra 套餐。

在用户选择之前，不要擅自选择路径或继续操作。

创建调度之前，先部署函数。
使函数在同一个逻辑周期内具备幂等性。
使用专用的服务端 cron secret 进行保护。
绝不向 Crontap 发送 Supabase service-role key。

Function security pattern

函数安全模式

Read a dedicated header or bearer value and compare it with a server-only environment variable before doing work. If Supabase gateway JWT verification is disabled for the function, this application-layer check is mandatory.

Keep the function response bounded. For long work, durably enqueue the job and return success only after the queue accepts it.

在执行任务之前，读取专用的 header 或 bearer 值，并将其与服务端专用环境变量进行比较。如果该函数未启用 Supabase gateway JWT 验证，则此应用层检查是强制性的。

限制函数响应的大小。对于耗时较长的任务，将作业持久化入队，并且仅在队列接受该作业后返回成功。

Workflow

工作流

Deploy the Edge Function and configure its cron secret.
Call it manually from a controlled environment with and without the secret.
Confirm expected status codes and idempotency behavior.
Create the Crontap schedule with the deployed HTTPS URL.
Verify the resolved cadence and first retained run.

部署 Edge Function 并配置其 cron secret。
在受控环境中，分别携带和不携带 secret 手动调用该函数。
确认预期的状态码和幂等行为。
使用已部署的 HTTPS URL 创建 Crontap 调度。
验证最终解析出的执行频率和首个保留的运行记录。

MCP example

MCP 示例

json

{
  "tool": "create_schedule",
  "arguments": {
    "url": "https://project-ref.supabase.co/functions/v1/nightly-cleanup",
    "text": "every day at 02:00",
    "timezone": "UTC",
    "method": "POST",
    "headers": {
      "Authorization": "Bearer <cron-secret-from-secure-store>",
      "Content-Type": "application/json"
    },
    "body": {
      "source": "crontap"
    },
    "label": "Supabase nightly cleanup"
  }
}

Use the real project reference from the Supabase project URL. Do not place a secret in the function URL or JSON body.

json

{
  "tool": "create_schedule",
  "arguments": {
    "url": "https://project-ref.supabase.co/functions/v1/nightly-cleanup",
    "text": "every day at 02:00",
    "timezone": "UTC",
    "method": "POST",
    "headers": {
      "Authorization": "Bearer <cron-secret-from-secure-store>",
      "Content-Type": "application/json"
    },
    "body": {
      "source": "crontap"
    },
    "label": "Supabase nightly cleanup"
  }
}

使用 Supabase 项目 URL 中真实的 project reference。不要将 secret 放置在函数 URL 或 JSON body 中。

REST fallback

REST 回退方案

REST requires Ultra API access:

bash

curl --fail-with-body https://api.crontap.com/v1/schedule \
  -X POST \
  -H "ClientId: $CRONTAP_CLIENT_ID" \
  -H "ApiKey: $CRONTAP_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
    "url": "https://project-ref.supabase.co/functions/v1/nightly-cleanup",
    "interval": "0 2 * * *",
    "timezone": "UTC",
    "verb": "POST",
    "headers": {
      "Authorization": "Bearer <cron-secret-from-secure-store>",
      "Content-Type": "application/json"
    },
    "data": {"source": "crontap"},
    "label": "Supabase nightly cleanup"
  }'

Prefer MCP when available.

REST 需要 Ultra API 访问权限：