Zapier actions
Every WundertreOS action and the underlying API endpoint that powers it.
Each action is a single API call. Fields shown in the Zap editor map 1:1 to the request body documented in the API reference.
Contact actions
Create Contact
POST /api-contacts — see Create contact.
Only first_name is required. Defaults: status="active", source="api", tags=[]. Returns 201 with the new record.
Update Contact
PATCH /api-contacts/:id — see Update contact.
Only fields you populate in the Zap are sent in the body. Updatable: first_name, last_name, email, phone, company, company_id, job_title, industry, address_line1, address_line2, city, state, zip, country, tags, status, stage, source, notes, linkedin_url, score.
Delete Contact
DELETE /api-contacts/:id — see Delete contact.
Find Contact
POST /api-contacts-search — see Search contacts.
Search by email, phone, first_name, last_name, or tags (contact must contain ALL tags). Returns up to limit matches (default 10, max 50). Use Zapier's "Create WundertreOS contact if it doesn't exist yet" toggle to chain straight into a Create Contact step.
The current public API exposes deals and activities as read‑only endpoints (GET /api-deals, GET /api-contacts/:id/deals, GET /api-activities). They power Zapier triggers and search steps but cannot be created or updated via Zapier actions yet. Create deals and log activities from inside WundertreOS, then trigger downstream Zaps via deal.created / deal.updated events.
Use Find Contact with the "Create if not found" toggle when ingesting leads from any other Zapier app. WundertreOS will return the existing contact when there's a match (by email or tags) and create a new one otherwise — no duplicates.