airtable-participantsRead and query retreat participant data from the Ceremonia Airtable base. Use this skill when asked about participants, subscriber counts, retreat attendance...
Install via ClawdBot CLI:
clawdbot install austinmao/airtable-participantsQuery retreat participant data from the Ceremonia Airtable base. This is the
authoritative source of truth for who receives emails and SMS messages.
Access is read-only by default — record modifications require Austin's
explicit instruction per change.
Ensure AIRTABLE_API_KEY is set in .env.
You will also need:
Store confirmed values in TOOLS.md and MEMORY.md once verified.
Participant records are expected to have at minimum these fields:
| Field | Type | Description |
|-------|------|-------------|
| name | Text | Full name |
| email | Email | Primary email address |
| phone | Phone | E.164 format preferred (+1XXXXXXXXXX) |
| retreat_status | Select | e.g., active, alumni, prospective, unsubscribed |
| tags | Multi-select | e.g., february-2026, guide-circle, donor |
| last_contact | Date | Most recent outreach date |
| donation_status | Select | e.g., donor, non-donor |
[VERIFY actual field names with Austin on first use — update this section when confirmed]
curl -s "https://api.airtable.com/v0/{BASE_ID}/{TABLE_NAME}?filterByFormula={retreat_status}='active'&fields[]=name&fields[]=email" \
-H "Authorization: Bearer $AIRTABLE_API_KEY" | jq '.records[].fields'
curl -s "https://api.airtable.com/v0/{BASE_ID}/{TABLE_NAME}?filterByFormula=AND({retreat_status}='active',{phone}!='')&fields[]=name&fields[]=phone" \
-H "Authorization: Bearer $AIRTABLE_API_KEY" | jq '.records[].fields'
curl -s "https://api.airtable.com/v0/{BASE_ID}/{TABLE_NAME}?fields[]=retreat_status" \
-H "Authorization: Bearer $AIRTABLE_API_KEY" | jq '[.records[].fields.retreat_status] | group_by(.) | map({status: .[0], count: length})'
curl -s "https://api.airtable.com/v0/{BASE_ID}/{TABLE_NAME}?filterByFormula=FIND('february-2026',ARRAYJOIN({tags}))" \
-H "Authorization: Bearer $AIRTABLE_API_KEY" | jq '.records[].fields'
Note: Airtable paginates at 100 records. Use the offset parameter from the response to fetch subsequent pages:
curl -s "https://api.airtable.com/v0/{BASE_ID}/{TABLE_NAME}?offset={OFFSET_TOKEN}" \
-H "Authorization: Bearer $AIRTABLE_API_KEY" | jq .
Always paginate fully before reporting totals or building recipient lists.
When Austin instructs a record change (e.g., marking someone unsubscribed, updating last_contact):
Generated Mar 1, 2026
A retreat organizer uses this skill to manage participant data for wellness events, tracking attendance, contact information, and engagement status. It helps segment participants for targeted communications and monitor donation contributions, ensuring personalized outreach and operational efficiency.
A nonprofit organization leverages this skill to maintain donor and participant databases for fundraising events. It enables querying donation statuses, segmenting active supporters, and building recipient lists for email or SMS campaigns, while adhering to privacy rules and unsubscription preferences.
An event planning company uses this skill to handle attendee data for workshops or conferences, including registration statuses and contact details. It facilitates creating segmented lists for pre-event communications and post-event follow-ups, with pagination to manage large datasets effectively.
An educational institution employs this skill to manage student or participant records for courses or programs, tracking enrollment statuses and contact information. It supports querying active participants for announcements and monitoring engagement through tags and last contact dates.
A community organization uses this skill to maintain member databases for outreach initiatives, such as newsletters and SMS alerts. It helps filter active members, segment by interests via tags, and ensure compliance with unsubscription rules, enhancing communication strategies.
Businesses charge recurring fees for access to retreats or exclusive content, using this skill to manage subscriber data, track active participants, and segment users for renewal campaigns. Revenue is generated through monthly or annual subscriptions, with upsells for donor tiers.
Companies host paid retreats or workshops, using this skill to handle attendee registrations, track payment statuses, and build communication lists for event updates. Revenue comes from ticket sales, with additional income from donations or premium add-ons.
Consultants or coaches use this skill to manage client databases for personalized programs, tracking engagement levels and contact segments for targeted outreach. Revenue is earned through session packages, with potential for scaling via automated communications and donor recognition.
💬 Integration Tip
Ensure the AIRTABLE_API_KEY is securely set in the environment and verify base ID and table name with the administrator before initial use to avoid errors in data retrieval.
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a second-model review (API or browser) for debugging, refactors, design checks, or cross-validation.
Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Clawdbot to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
Local search/indexing CLI (BM25 + vectors + rerank) with MCP mode.
Use when designing database schemas, writing migrations, optimizing SQL queries, fixing N+1 problems, creating indexes, setting up PostgreSQL, configuring EF Core, implementing caching, partitioning tables, or any database performance question.
Connect to Supabase for database operations, vector search, and storage. Use for storing data, running SQL queries, similarity search with pgvector, and managing tables. Triggers on requests involving databases, vector stores, embeddings, or Supabase specifically.
Query, design, migrate, and optimize SQL databases. Use when working with SQLite, PostgreSQL, or MySQL — schema design, writing queries, creating migrations, indexing, backup/restore, and debugging slow queries. No ORMs required.