Zapier API Keys is the admin screen where each CRM user gets a key for Zapier. Click Generate, enter a Name, and the key appears once.

• Create a key from the Generate a New Key popup with a Name field.
• Copy the new key at once, because Krayin CRM keeps only a hash of it.
• See the Name, Created, and Last Used date for every key.
• Revoke a key after you confirm the Are you sure? prompt.
• Search and filter keys when many users connect Zapier.

Connecting Krayin CRM in Zapier takes two fields. The Krayin CRM app asks for the Krayin URL and the API Key, then Connect.

• Enter the Krayin URL you use to reach the CRM.
• Paste the API Key copied from Zapier API Keys.
• Click Connect to save the account in Zapier.
• Pick the saved account in any trigger or action step.

Krayin CRM trigger events start a Zap the moment a lead, person, or quote is created, updated, or deleted.

The Krayin CRM Zapier Integration uses REST Hooks, so every event is marked Instant and Zapier never polls the CRM.

• Choose New Lead, Updated Lead, or Deleted Lead.
• Choose New Person, Updated Person, or Deleted Person, including bulk deletes.
• Choose New Quote, Updated Quote, or Deleted Quote.
• Receive deleted records as a full snapshot captured before removal.
• Get custom EAV fields and a crm_url record link in every payload.
• Keep rapid successive edits from being dropped by Zapier deduplication.

Test trigger shows real Krayin CRM records while you build a Zap, so you map each field against actual values.

Sample data and live deliveries share one transformer. A field mapped in a test arrives with the same name in a live Zap.

• Load up to three recent records with Find new records.
• Open a record to see fields such as Name, Email, Organization, and Crm Url.
• Set the count under Records shown in Test trigger.
• Search the loaded records to find the right one.

Krayin CRM action events write data into the CRM from any Zap. The list holds Create Lead, Create Person, Update Lead, and Update Person.

This Zapier Integration for Krayin CRM checks the email first, so contacts from forms and chats do not become duplicates.

• Create Lead attaches the lead to a person matched by email.
• Create Person returns the existing contact when the email is already saved.
• Update Lead changes only the fields you fill in and leaves the rest alone.
• Update Person accepts the same kind of partial update.
• Moving a lead to Won or Lost stamps the close date automatically.

The Create Lead action lists every lead field in the Zap editor, from Title and Lead Value to Person Email and Person Name.

Dropdowns load live CRM values, so you pick a pipeline or stage instead of typing an ID.

• Fill Title, Description, Lead Value, and Expected Close Date.
• Select Pipeline, Stage, Source, Type, and Sales Owner from live lists.
• Add Person Email and Person Name to link or create the person.
• Choose a stage, and the matching pipeline fills in automatically.
• Write custom EAV fields, which show up in the editor on their own.

Connected Zaps lists every Zap listening to the CRM. Zapier adds and removes these entries itself as Zaps are switched on and off.

• See the Zap, Trigger, API Key, Status, and Connected date for each entry.
• Check which API key each Zap uses.
• Click Disconnect to stop one Zap without touching the others.
• Search and filter the list as the number of Zaps grows.

Delivery Logs record every webhook sent to Zapier. Summary cards show Success Rate, Delivered, Failed, Zap Turned Off, and Blocked.

Click View on any row to open Delivery Detail with the target host and the full Payload Sent.

• Read When, Trigger, Record, Status, HTTP, and Duration for each delivery.
• Filter logs by status to find failed sends quickly.
• Open Delivery Detail for the payload and the response.
• Get a warning banner when the queue worker is not running.

Zapier Configuration Settings control delivery, payload size, and logging. Nine fields sit under Delivery, Payload, and Delivery logging.

• Set Delivery timeout (seconds), Retry attempts, and Failures before pausing a Zap.
• Limit Maximum Zaps per API key, which is 100 by default.
• Cap Maximum fields per record and Records shown in Test trigger.
• Turn Log every delivery on or off, and set Days to keep logs.
• Set Fields stored per log entry, or override any setting with ZAPIER_* variables.

Zapier role permissions decide which admins can manage the connector inside Krayin CRM.

Under Settings > Roles, the Zapier group covers API Keys, Connected Zaps, and Delivery Logs.

• Allow Create and Delete on API Keys for each role.
• Allow Disconnect on Connected Zaps for each role.
• Grant access to Delivery Logs on its own.
• Send webhooks only over HTTPS to allowed hosts, rechecked before every send.
• Turn off a Zap and delete its subscription when Zapier returns 410 Gone.