Integrations
Inbound Webhooks
Receive data from external systems with automatic field mapping.
Inbound webhooks receive data from external systems and map incoming fields to your pipeline blueprint automatically.
Setup
- Go to Settings → Company Settings → Integrations
- Click "Create Integration"
- Name your integration (e.g., "Zapier", "Make", "n8n")
- A unique webhook URL is generated. Copy it and provide it to the external tool.
Source mappings
Source mappings define how incoming data translates to your pipeline fields.
- Go to Settings → Company Settings → Source Mappings
- Create a mapping and select Integration as the type
- Paste a sample JSON payload and Slate automatically detects the fields
- Map each detected field to a pipeline field
For example, if the external tool sends:
{
"name": "John Doe",
"email": "john@example.com",
"company": "Acme Inc"
}
Map the fields as follows:
name→ your "Contact Name" fieldemail→ your "Email" fieldcompany→ your "Company" field
Field validation
Inbound webhooks do not enforce field validation rules (such as required fields or format checks). All incoming data is accepted as is to avoid dropping data from external systems. Validation is only applied to items created manually or via CSV import.
Duplicate handling
If your pipeline has duplicate detection enabled, inbound webhooks respect it. Depending on your configuration:
| Warn | Creates the item but flags the duplicate |
| Skip | Ignores the duplicate |
| Update | Merges data into the existing item |