OpenClaw

baserow

Work with Baserow tables/rows over the REST API for reads, inserts, and updates. Use when user asks to view or modify Baserow CRM/pipeline data.

ericjbone0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install ericjbone/baserow

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Baserow Skill

Use Baserow REST API directly via Python stdlib (urllib). API docs: https://baserow.ericbone.me/api-docs/database/265

Local auth convention (this workspace)

Primary env vars in ~/.openclaw/.env:

BASEROW_BASE_URL=https://baserow.ericbone.me
BASEROW_TOKEN=<personal API token> (static; no expiry)

Auth header for DB calls:

Authorization: Token <BASEROW_TOKEN>

Core API patterns

Base endpoint:

$BASEROW_BASE_URL/api/database/rows/table/{table_id}/

Always include: ?user_field_names=true

Renpho CRM table map (DB 265)

827 Sales Pipeline (BD Opportunity table)
828 Opportunity Line Items
829 Contacts
830 Interactions
831 Account Execution

Operating conventions (Renpho)

For inbound/outbound emails that are active deal motion: log in Interactions (830) and link Contact + Opportunity.
Create/update a Sales Pipeline (827) opportunity for real BD opportunities.
BD Inbox field can be used for intake linkage when that inbox object is present, but in-progress opportunity work should still live in Pipeline + Interactions.
Keep Interactions to real sales interactions (no LinkedIn enrichment spam).

⚠️ Critical: .env Must Have Real Newlines

The .env file must use real newlines between vars, NOT \n literals:

BASEROW_BASE_URL="https://baserow.ericbone.me"
BASEROW_TOKEN="mOsuizlNhyUWclr7xKjIgxJxdMPVmkNy"

If written by an agent (e.g. write tool), verify with cat ~/.openclaw/.env — literal \n breaks export $(grep ...) silently.

⚠️ Use curl for Writes (PATCH/POST), Python for Reads

Python urllib returns 403 on PATCH/POST against this Baserow instance. Use curl for all writes. Python urllib is fine for GET/reads.

Minimal examples

List rows (Python OK for reads)

export $(grep -v '^#' ~/.openclaw/.env | xargs) && python3 - <<'PY'
import os, json, urllib.request
base=os.environ['BASEROW_BASE_URL'].rstrip('/')
token=os.environ['BASEROW...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/ericjbone/baserow
Version: —
Commit: 39a8778c7f8a1ee759fafa3aba6e7c74c23d3115
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Baserow Skill

Use Baserow REST API directly via Python stdlib (`urllib`). API docs: https://baserow.ericbone.me/api-docs/database/265

## Local auth convention (this workspace)

Primary env vars in `~/.openclaw/.env`:
- `BASEROW_BASE_URL=https://baserow.ericbone.me`
- `BASEROW_TOKEN=<personal API token>` (static; no expiry)

Auth header for DB calls:
```
Authorization: Token <BASEROW_TOKEN>
```

## Core API patterns

Base endpoint:
```
$BASEROW_BASE_URL/api/database/rows/table/{table_id}/
```

Always include: `?user_field_names=true`

## Renpho CRM table map (DB 265)

- `827` Sales Pipeline (BD Opportunity table)
- `828` Opportunity Line Items
- `829` Contacts
- `830` Interactions
- `831` Account Execution

## Operating conventions (Renpho)

- For inbound/outbound emails that are active deal motion: log in **Interactions (830)** and link Contact + Opportunity.
- Create/update a **Sales Pipeline (827)** opportunity for real BD opportunities.
- **BD Inbox** field can be used for intake linkage when that inbox object is present, but in-progress opportunity work should still live in Pipeline + Interactions.
- Keep Interactions to real sales interactions (no LinkedIn enrichment spam).

## ⚠️ Critical: .env Must Have Real Newlines

The `.env` file **must** use real newlines between vars, NOT `\n` literals:

```
BASEROW_BASE_URL="https://baserow.ericbone.me"
BASEROW_TOKEN="mOsuizlNhyUWclr7xKjIgxJxdMPVmkNy"
```

If written by an agent (e.g. `write` tool), verify with `cat ~/.openclaw/.env` — literal `\n` breaks `export $(grep ...)` silently.

## ⚠️ Use curl for Writes (PATCH/POST), Python for Reads

Python `urllib` returns 403 on PATCH/POST against this Baserow instance. **Use curl for all writes.** Python urllib is fine for GET/reads.

## Minimal examples

### List rows (Python OK for reads)
```bash
export $(grep -v '^#' ~/.openclaw/.env | xargs) && python3 - <<'PY'
import os, json, urllib.request
base=os.environ['BASEROW_BASE_URL'].rstrip('/')
token=os.environ['BASEROW...

搜索