Zapier

Zapier is the no-code path when a vendor has no native Yareta connector.

Get a Zapier key

An organisation admin issues a Zapier integration key in the Yareta app (Integrations / developer settings, depending on your build). It is not the same as a Developer Assessment API key even if both look like secret tokens.

Send it as:

x-api-key: <your-zapier-key>

What Zaps can do

HTTP actions against https://platform.yareta.ai (production):

Method	Path	Purpose
GET	/api/zapier/me	Confirm the key and see user email / org name
GET	/api/zapier/profiles	List profiles (frameworks) you can submit into
POST / GET	/api/zapier/submissions	Create or list submissions (deals / people)
POST / GET	/api/zapier/resources	Attach files / resources
POST / GET	/api/zapier/transcripts	Attach transcripts
POST / GET / DELETE	/api/zapier/webhooks	Subscribe Zapier to Yareta outbound events

Creating a submission queues processing. The HTTP response is typically { "status": "queued", "job_id": "job_…" } — poll your workspace rather than expecting a full score in the Zap’s immediate output.

Create submission body

{
  "record_id": "unique-id-from-your-app",
  "profile_id": "<profile from GET /profiles>",
  "fields": {
    "email": "founder@example.com",
    "name": "Ada Lovelace",
    "company": "Example Ltd"
  },
  "filters": [],
  "source": "zapier"
}

record_id, profile_id, and fields are required.

Native Zapier app

If your organisation was given the Yareta Zapier app, use that instead of raw HTTP. Keys still apply.

Full HTTP reference: Zapier HTTP API.