# Slate Documentation ::u-page-hero --- class: dark:bg-gradient-to-b from-neutral-900 to-neutral-950 orientation: vertical --- #title Slate [Documentation]{.text-primary} #description Slate is a customer relationship management and workflow platform. :br Build pipelines for sales, support, hiring, or any multi step process with everything you need built in. #links :::u-button --- size: xl to: https://docs.slate.zerulean.com/getting-started trailing-icon: i-lucide-arrow-right --- Get Started ::: :::u-button --- color: neutral size: xl to: https://docs.slate.zerulean.com/api/authentication variant: outline --- API Reference ::: :: ::u-page-section --- class: dark:bg-neutral-950 feature-cards --- #title Everything you need #features :::u-page-feature --- icon: i-lucide-kanban orientation: vertical to: https://docs.slate.zerulean.com/core-concepts --- #title Pipelines & Stages #description Visual Kanban boards with custom stages, statuses, and fields. Model any workflow without writing code. ::: :::u-page-feature --- icon: i-lucide-users orientation: vertical to: https://docs.slate.zerulean.com/core-concepts/contacts --- #title Contacts #description Manage people and companies across all your pipelines. Link contacts to items, track activity, and store detailed contact information. ::: :::u-page-feature --- icon: i-lucide-check-square orientation: vertical to: https://docs.slate.zerulean.com/features/tasks --- #title Tasks #description Track to dos and follow ups with list and calendar views. Assign to team members, set priorities, and link to items. ::: :::u-page-feature --- icon: i-lucide-shield orientation: vertical to: https://docs.slate.zerulean.com/core-concepts/teams --- #title Teams & Permissions #description Organize users into teams. Control access to pipelines and stages with granular user and team permissions. ::: :::u-page-feature --- icon: i-lucide-file-text orientation: vertical to: https://docs.slate.zerulean.com/features/proposals --- #title Proposals #description Create, send, and track proposals with PDF generation and public sharing links. ::: :::u-page-feature --- icon: i-lucide-receipt orientation: vertical to: https://docs.slate.zerulean.com/features/invoices --- #title Invoices #description Invoice management with payment tracking and public invoice pages for customers. ::: :::u-page-feature --- icon: i-lucide-pen-tool orientation: vertical to: https://docs.slate.zerulean.com/features/proposals#e-signatures --- #title E-Signatures #description Send proposals for electronic signature with a consent flow. Track signing status in real time. ::: :::u-page-feature --- icon: i-lucide-package orientation: vertical to: https://docs.slate.zerulean.com/features/inventory --- #title Inventory #description Product catalog with stock tracking. Record adjustments, view history, and update stock levels in bulk. ::: :::u-page-feature --- icon: i-lucide-inbox orientation: vertical to: https://docs.slate.zerulean.com/features/conversations --- #title Inbox & Conversations #description Handle email conversations directly inside your pipeline with a shared inbox, threading, and delivery tracking. ::: :::u-page-feature --- icon: i-lucide-mail orientation: vertical to: https://docs.slate.zerulean.com/integrations/email-domains --- #title Email Domains & Templates #description Send from your own domain. Create reusable email templates with variables for automations, proposals, invoices, and support tickets. ::: :::u-page-feature --- icon: i-lucide-bar-chart-3 orientation: vertical to: https://docs.slate.zerulean.com/features/reports --- #title Reports #description Seven report types covering funnels, velocity, activity, win/loss, revenue, trends, and forecasts with CSV export. ::: :::u-page-feature --- icon: i-lucide-activity orientation: vertical to: https://docs.slate.zerulean.com/features/analytics --- #title Analytics #description KPI dashboard with key metrics, pipeline funnel visualization, and item trend tracking at a glance. ::: :::u-page-feature --- icon: i-lucide-target orientation: vertical to: https://docs.slate.zerulean.com/features/lead-scoring --- #title Lead Scoring #description Score items based on configurable rules per pipeline. Use scores for card colors, reporting, and automatic decay for stale items. ::: :::u-page-feature --- icon: i-lucide-zap orientation: vertical to: https://docs.slate.zerulean.com/features/automations --- #title Automations #description Multi step workflows with conditions, delays, emails, webhooks, and stage changes. Trigger on item events or schedules. ::: :::u-page-feature --- icon: i-lucide-copy-check orientation: vertical to: https://docs.slate.zerulean.com/features/duplicate-detection --- #title Duplicate Detection #description Catch duplicates before they are created. Configure match fields, scope, and behavior per pipeline. ::: :::u-page-feature --- icon: i-lucide-plug orientation: vertical to: https://docs.slate.zerulean.com/integrations --- #title Integrations #description Connect external tools with inbound and outbound webhooks, web forms, CSV import, and a REST API. ::: :::u-page-feature --- icon: i-lucide-file-input orientation: vertical to: https://docs.slate.zerulean.com/integrations/web-forms --- #title Web Forms #description Embeddable lead capture forms with custom styling and rate limiting. ::: :::u-page-feature --- icon: i-lucide-upload orientation: vertical to: https://docs.slate.zerulean.com/integrations/csv-import --- #title CSV Import #description Bulk import items from spreadsheets with progress tracking and rollback support. ::: :::u-page-feature --- icon: i-lucide-code orientation: vertical to: https://docs.slate.zerulean.com/api/authentication --- #title API Reference #description API key authentication with scoped access and rate limiting. REST endpoints for items, tasks, pipelines, and webhooks. ::: :::u-page-feature --- icon: i-lucide-book-open orientation: vertical to: https://docs.slate.zerulean.com/guides --- #title Guides #description Step by step walkthroughs for common tasks. Create pipelines, send proposals, set up automations, and more. ::: :::u-page-feature --- icon: i-lucide-circle-help orientation: vertical to: https://docs.slate.zerulean.com/faq-and-support/faq --- #title FAQ & Support #description Answers to common questions about accounts, billing, data, and security. Get help from our team. ::: :: # Introduction Slate is a customer relationship management and workflow platform. It provides pipelines for sales, support, hiring, and any multi step process you need to manage. ## Core Capabilities - **Build custom pipelines** with stages, statuses, and custom fields on a Kanban board - **Manage contacts** for people and companies across your workflows - **Handle conversations** via email directly inside your pipeline with a shared inbox - **Automate workflows** with multi step automations including emails, stage changes, webhooks, conditions, and delays - **Create proposals and invoices** with PDF generation and e-signatures - **Track tasks** with list and calendar views - **Analyze performance** with reports and analytics dashboards - **Integrate** with external tools via API, webhooks, CSV import, and embeddable web forms ## How Slate is organized ```text Organization └── Company ├── Pipelines (Sales, Support, Hiring) │ └── Stages (Open, Proposal, Won, Lost) │ │ ├── Statuses (optional substeps: Draft, Created, Sent) │ └───┴── Items (deals, tickets, candidates) │ ├── Contacts (people and companies) ├── Tasks (followups, calls, meetings) └── Settings (teams, integrations, billing) ``` Each **company** is a self contained workspace with its own pipelines, contacts, and settings. An organization can contain multiple companies. When you create a company, you select a **region** that determines where your data is stored. Once set, your region cannot be modified. ## Authentication Slate uses **passwordless authentication** exclusively. | | | | ----------------------- | ---------------------------------------- | | **Email passcodes** | A one time code sent to your email | | **Passkeys / WebAuthn** | Biometric or hardware key authentication | ## Plans | | | | -------------- | -------------------------------------------------------------- | | **Individual** | 1 user, core pipeline features | | **Pro** | Teams, automations, reports, e-signatures, duplicate detection | | **Business** | Analytics, advanced scoring, unlimited automations | | **Enterprise** | Custom limits, priority support | All plans start with a **14-day free trial** with no credit card required. After the trial expires, access to pipeline data is suspended until you select a plan. Companies that remain unsubscribed for 30 days after trial expiry are permanently deleted. ## Referral program Existing users can generate a referral code and share it. When a new user applies the code during their trial: | | | | ------------ | --------------------------------------------------------------------------------------------------- | | **Referee** | Extended 60 day trial instead of 14 days | | **Referrer** | Subscription credit equal to the referee's per user monthly plan price, up to 10 referrals per year | # Quickstart ## 1. Create your account [Sign up](https://slate.zerulean.com/signup){rel=""nofollow""} with your email address. After creating your account, you can add a passkey for passwordless login. ## 2. Create an organization After logging in, create an **organization**. This is the top level container for your business, and one organization can hold multiple companies. ## 3. Create a company Create your first **company** within the organization. You will configure the following during creation: | | | | ---------- | ---------------------------------------------------------------------------------- | | **Name** | The workspace name visible to all members | | **Region** | Where your data is stored (e.g., Europe). Once set, your region cannot be modified | | **Plan** | Trial, Individual, Pro, Business, Enterprise | ## 4. Create your first pipeline A pipeline represents a workflow. You can start from a template or create a blank one: 1. **Choose a template.** Select one tailored to your industry, or start with a blank pipeline 2. **Configure stages** as columns on your Kanban board (e.g., Lead, Qualified, Proposal, Negotiation, Closed) 3. **Add statuses** as optional substeps within stages (e.g., Draft, Sent, Reviewed) 4. **Define fields** by enabling built in fields (email, phone) and adding custom fields across multiple types and variants For a detailed walkthrough of every setting, see [Create a Pipeline](https://docs.slate.zerulean.com/guides/create-a-pipeline). ## 5. Add your first item Click **"Add Item"** on your pipeline board. Fill in the fields and save. Your new item appears as a card in the first stage. From the Kanban board you can: | | | | ----------------- | --------------------------------------------------------------------- | | **Drag and drop** | Move cards between stages | | **Hover** | See quick info and actions | | **Click** | Open the detail view with overview, activity, proposals, and invoices | | **Log activity** | Record notes, calls, emails, and meetings | | **Assign** | Add team members with multiple assignees and a primary designation | Learn more about working with items in the [Manage Items](https://docs.slate.zerulean.com/guides/manage-items) guide. ## 6. Invite your team Go to **Settings → Company Settings → Users** and invite people by email. | | | | ----------- | -------------------------------------------------------------- | | **Member** | The default role. Can work with items, contacts, and tasks | | **Admin** | Can create and update items, pipelines, teams, and add members | | **Billing** | Managed exclusively by the company creator (Owner) | To control access to specific pipelines or stages, create **teams** in **Settings → Company Settings → Teams** and assign permissions at the pipeline or stage level. For the full setup, see the [Invite Team Members](https://docs.slate.zerulean.com/guides/invite-your-team) guide and [Teams & Permissions](https://docs.slate.zerulean.com/core-concepts/teams). ## 7. Subscribe to a plan Before the 14-day trial expires, select a plan from **Settings → Company Settings → Billing**: | | | | -------------- | ----------------------------------------------------------------------------- | | **Individual** | 1 user, core pipeline features | | **Pro** | Teams, automations, reports, e-signatures, duplicate detection, conversations | | **Business** | Analytics dashboard, advanced lead scoring with decay, unlimited automations | | **Enterprise** | Custom limits, priority support | Billing is available monthly or annually. If you have a referral code, you can apply it during company creation or before your first checkout to extend your trial from 14 to 60 days. If the trial expires without an active subscription, access to pipeline data is suspended until you select a plan. ## Next steps [Core Concepts](https://docs.slate.zerulean.com/core-concepts) to learn the data model and organizational hierarchy :br[Guides](https://docs.slate.zerulean.com/guides) for step-by-step operational walkthroughs :br[API Reference](https://docs.slate.zerulean.com/api/authentication) for external API integration # Overview Slate's data model is built around a hierarchy designed to support any workflow. The following sections describe how the pieces fit together. ## Organizations & Companies An **organization** is the top level container, typically your business. Under it, you create **companies**, each acting as an independent workspace with its own pipelines, team members, contacts, and settings. Most teams use a single company. Multiple companies are useful for separate departments, clients, or brands. ## Pipelines A **pipeline** represents a workflow, the journey something takes from start to finish. Examples: | | | | ------------ | ---------------------------------------------------------------------------------------- | | **Sales** | Deal Pipeline with stages like Lead, Qualified, Proposal, Negotiation, and Closed | | **Support** | Ticket Pipeline with stages like New, In Progress, Waiting, and Resolved | | **Hiring** | Recruitment pipeline with stages like Applied, Phone Screen, Interview, Offer, and Hired | | **Projects** | Task Board with stages like Backlog, In Progress, Review, and Done | Each pipeline has its own **blueprint**, the set of custom fields that define what data you track. Blueprints are versioned, so changes to your fields do not affect existing items. Pipeline templates are available for common workflows across various industries. ## Stages Stages are the columns on your Kanban board. Items move through stages as they progress. You can configure: | | | | --------------- | ----------------------------------------------- | | **Order** | Set using sort order to control column position | | **Permissions** | Restrict who can view or edit items in a stage | | **Fields** | Each stage can show different fields | ## Statuses Statuses are optional substeps within stages that help track item progress. For example, an item in a "Proposal" stage might move through statuses like **Draft**, **Sent**, and **Reviewed** to indicate where it stands within that stage. ## Reporting designations For reporting purposes, you can mark specific stages or statuses as **Won** or **Lost**. This powers win/loss rates and revenue metrics across your pipeline reports. ## Items Items are the individual records in your pipeline, whether that is a deal, a ticket, a candidate, or a task. Each item has: - **Short ID**, an automatically generated identifier that is automatically assigned - **Custom fields** defined by your pipeline blueprint - **Stage** and **status** - **Assignees**, the team members responsible - **Activity log** for notes, calls, and emails - **Score**, an optional lead score when scoring is enabled - **Proposals, invoices, and tasks** linked to it Items can be deleted and restored, and moved between stages using drag-and-drop on the Kanban board. ### Searching items The dashboard search bar filters items client-side by name, contact name, email, phone, and short ID. For deeper search across all pipelines, press **Cmd+P** (or **Ctrl+P**) to open the **command palette**. Type to search items in the database by name, contact details, or short ID. Select a result to open its detail view. The command palette also provides quick navigation to any page. ## Fields Fields are organized into categories, each with its own set of types and display variants: | | | | --------------- | -------------------------------------------------------------------------- | | **Input** | Text, email, URL, phone, currency, number, file upload, textarea, and more | | **Radio** | Single select with buttons, cards, tabs, scale, dropdown, and more | | **Select** | Dropdown, tags, listbox, large cards, tabs, and more | | **Checkbox** | Multi-select with buttons, cards, list, tabs, and more | | **Date & Time** | Date, time, date and time, date range, natural language date, and more | Each pipeline also has optional **built in fields** for email and phone that you can enable per pipeline. Fields support validation rules, conditional visibility, currency formatting, and card indicator colors. ## Roles and Permissions Access in Slate is controlled at two levels. ### User roles Each user has a company wide role: | | | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Owner** | The company creator. Can manage all company settings, delete the company, and remove members. Always has full access to all pipelines and stages | | **Admin** | A promoted member. Can create and update items, pipelines, stages, and teams, and add members | | **Member** | The default role. Can view items, contacts, and tasks within the pipelines and stages they have been granted access to | ### Teams Users can be organized into teams (e.g., "Sales", "Support"). Each team member has a role within the team: | | | | ----------- | ----------------------------------- | | **Manager** | Can manage the team and its members | | **Member** | Standard team member | ### Pipeline and stage permissions For more granular control, you can assign permissions to teams or individual users at the pipeline or stage level: | | | | ---------- | --------------------------------------------------------------------------------- | | **Read** | View items in the pipeline or stage | | **Write** | Create and edit items | | **Manage** | Full control, including managing assignees and tasks within the pipeline or stage | Owners always have full access to all pipelines and stages. See [Teams & Permissions](https://docs.slate.zerulean.com/core-concepts/teams) for details. # Contacts The built in CRM manages **people** and **companies** across all your pipeline interactions. ## Contact types | | | | ----------- | ----------------------------------------------------- | | **Person** | An individual (e.g., a lead, client, or candidate) | | **Company** | An organization (e.g., a business you are selling to) | Contacts are shared across all pipelines in your company workspace. ## Contact fields When creating a contact, the available fields depend on the contact type: ### Shared fields (Person and Company) | | | | ---------------------------------- | --------------------------------------------------------------------------------------------- | | **Name** | Contact name | | **Email** (optional) | Email address | | **Phone** (optional) | Phone number | | **Parent Company** (optional) | Link to a company contact (disabled for company type) | | **Location** (optional) | Address or location | | **Timezone** (optional) | Contact's timezone | | **Preferred Method** (optional) | Email, phone, SMS, WhatsApp, in person, or video call | | **Best time from / to** (optional) | Preferred contact hours | | **LinkedIn** (optional) | LinkedIn profile URL | | **Website** (optional) | Website URL | | **Source** (optional) | Where the contact came from (website, referral, cold outreach, inbound, event, import, other) | | **Tags** (optional) | Custom tags for categorization | | **Do not contact** (optional) | Flag to prevent outreach | ### Person only fields | | | | ----------------------- | ----------------- | | **Position** (optional) | Job title or role | ### Company only fields | | | | ----------------------------- | ---------------------------- | | **Description** (optional) | Company description | | **Industry** (optional) | Industry sector | | **Company Size** (optional) | Number of employees | | **Annual Revenue** (optional) | Estimated annual revenue | | **Founded** (optional) | Year the company was founded | ## Linking contacts to items When you create or edit an item, you can link it to a contact. This creates a bidirectional relationship: - See all items associated with a contact across every pipeline - View activity history spanning all linked items - Track tasks linked to the contact - Conversations and email threads are associated through the contact link ## Contact detail Click on a contact to see: | | | | ------------ | ------------------------------------------ | | **Activity** | All notes and interactions | | **Items** | Linked pipeline items across all pipelines | | **Tasks** | Tasks associated with the contact | ## Search & filtering The contacts page supports: - Full text search across contact names and details - Filtering by type (person or company) - Sortable columns - Pagination for large contact lists # Teams & Permissions ## User roles Each user in a company has a role: | | | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Owner** | The company creator. Can manage all company settings, delete the company, and remove members. Always has full access to all pipelines and stages | | **Admin** | A promoted member. Can create and update items, pipelines, stages, and teams, and add members | | **Member** | The default role. Can view items, contacts, and tasks within the pipelines and stages they have been granted access to | You can promote a member to Admin from **Settings → Company Settings → Users**. ## Teams Group your users into teams for easier permission management. A user can belong to multiple teams. Go to **Settings → Company Settings → Teams** to create a team and add members. Each team member has a role within the team: | | | | ----------- | ----------------------------------- | | **Manager** | Can manage the team and its members | | **Member** | Standard team member | ## Pipeline and stage permissions For granular control, you can assign permissions to teams or individual users at the pipeline or stage level: | | | | ---------- | --------------------------------------------------------------------------------- | | **Read** | View items in the pipeline or stage | | **Write** | Create and edit items | | **Manage** | Full control, including managing assignees and tasks within the pipeline or stage | Owners always have full access to all pipelines and stages and bypass these permissions. ### How permissions are resolved 1. If a **user level permission** exists for the pipeline or stage, it takes priority 2. Otherwise, **team permissions** are checked across all teams the user belongs to 3. If no permission rules exist for a pipeline or stage, access is **unrestricted** by default ### Example: Pipeline-level access A company has two pipelines: **Sales** and **Support**. The Sales team only has access to the Sales pipeline, and the Support team only has access to the Support pipeline. Neither team can see the other's pipeline. ### Example: Stage-level access Within a Recruitment pipeline, the **HR team** has access to the "Applied", "Screening", and "Interview" stages, while the **Finance team** only has access to the "Offer" and "Hired" stages. Items move through the full pipeline, but each team works within their own stages without seeing each other's. ### When to use permissions - Different teams work on different pipelines - Sensitive stages (e.g., salary negotiation) should be restricted to specific users - Multiple teams share a pipeline but each team only needs to see certain stages - Members should only see the pipelines relevant to their role - You need a combination of user level and team level control on the same pipeline # Overview A comprehensive feature set for workflow management, contact communication, document generation, and performance analysis. ## Workflow & Automation - [Automations](https://docs.slate.zerulean.com/features/automations) for multi step workflows triggered by events or schedules - [Tasks](https://docs.slate.zerulean.com/features/tasks) for task management with list and calendar views - [Duplicate Detection](https://docs.slate.zerulean.com/features/duplicate-detection) to identify duplicates before they are created ## Communication - [Conversations & Inbox](https://docs.slate.zerulean.com/features/conversations) for email conversations inside your pipeline with a shared inbox (SMS/WhatsApp planned) - [Email Domains & Templates](https://docs.slate.zerulean.com/integrations/email-domains) for custom domain verification, outbound senders, inbound email, and reusable email templates ## Documents - [Proposals](https://docs.slate.zerulean.com/features/proposals) to create, send, and track proposals with PDF generation - [E-Signatures](https://docs.slate.zerulean.com/features/proposals#e-signatures) to send proposals for electronic signature with consent flow - [Invoices](https://docs.slate.zerulean.com/features/invoices) for invoice management with payment tracking ## Analytics - [Reports](https://docs.slate.zerulean.com/features/reports) covering pipeline funnels, deal velocity, win/loss, revenue, and trends - [Analytics Dashboard](https://docs.slate.zerulean.com/features/analytics) with a KPI grid, funnel chart, and item trends - [Lead Scoring](https://docs.slate.zerulean.com/features/lead-scoring) to score items based on configurable rules ## Other - [Inventory](https://docs.slate.zerulean.com/features/inventory) for product catalog and stock management - [Web Forms](https://docs.slate.zerulean.com/integrations/web-forms) for embeddable forms and public lead capture # Lead Scoring Automated scoring assigns point values to pipeline items based on configurable rules, helping your team prioritize high value leads. ## How it works 1. Open your pipeline settings 2. Enable **Lead Scoring** 3. Define scoring rules based on field values Each rule adds or subtracts points when a condition is met. The total score is computed automatically whenever items are created or modified. ## Score rules Rules evaluate field values and assign points. For example: - "Deal Value" > $10,000 → +20 points - "Source" = "Referral" → +15 points - "Industry" = "Enterprise" → +10 points Set a **max score** to cap the total. ## Score decay On Business+ plans, enable score decay to automatically reduce scores over time for stale items. Configure: | | | | ------------------ | ------------------------------------------------------------- | | **Decay rate** | How many points to subtract per interval | | **Decay interval** | How often decay is applied (e.g., every 7 days of inactivity) | Decay ensures that items which haven't been updated recently lose priority naturally, keeping your highest-scored items current and actionable. ## Using scores | | | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Card colors** | Bind card background color to score ranges in pipeline settings. Define color thresholds (e.g., green for 80+, yellow for 50-79, red for below 50) so high value items are visually prominent on the Kanban board | | **Stage sorting** | Expand a stage header to sort items by score (highest first or lowest first). Sort controls appear when any item in the pipeline has a score | | **Reporting** | Scores feed into pipeline analytics and can inform forecast weighting | # Conversations & Inbox Send and receive emails directly within pipeline items, with each item functioning as a conversation thread. ## Enabling conversations Conversations are enabled per pipeline: 1. Open your pipeline settings 2. Toggle **"Email Conversations"** on 3. Set up an [email domain](https://docs.slate.zerulean.com/integrations/email-domains) for sending Once enabled, each item in that pipeline becomes a conversation thread. ## Working with conversations ### In the item detail view When conversations are enabled, the item detail shows: | | | | ------------------------- | ----------------------------------------------- | | **Reply to Customer** tab | Send an email to the contact linked to the item | | **Internal Note** tab | Add a private note visible only to your team | Replies are sent from your configured email domain and threaded properly. ### Conversation thread The conversation thread shows all messages chronologically: | | | | ---------------------------------------- | -------------------------------------------- | | **Inbound messages** (from the customer) | Displayed on the left | | **Outbound messages** (from your team) | Displayed on the right with user avatar | | **Internal notes** | Marked as internal, not visible to customers | Each message shows delivery status (sent, delivered, etc.) and sender name. ## Inbox The **Inbox** page shows all conversations across all conversation enabled pipelines in one place. - Split panel: item list on the left, conversation thread on the right - **Unread badges** show which conversations have new messages - Click a conversation to read and reply - Unread count is shown in the sidebar badge ## Sender selection When your company has multiple email senders configured, the inbox reply area shows a combined channel and sender dropdown. The senders available to you depend on your team membership: | | | | ----------- | ------------------------------------------------------------- | | **Admins** | See all company senders | | **Members** | See senders assigned to their teams, plus the company default | To assign a sender to a team, open the sender's edit dialog in **Settings → Emails** and check the teams that should use it. ## Email threading When a customer replies to an email, Slate matches it to the correct item using email threading and a subject line token embedded in outbound messages. This ensures replies are linked to the right conversation automatically. ## Inbound email Inbound emails are matched to existing conversations automatically. If a match is found, the message is appended to the conversation thread. If no match is found, a new item is created in the configured pipeline. ## Read tracking Unread tracking is per user. When you open a conversation, it is marked as read for you without affecting other team members' unread counts. ## Multi channel roadmap Conversations currently support **email**. SMS and WhatsApp channels are planned for future releases. # Tasks Task management for to dos and follow ups with list and calendar views. ## Creating tasks Tasks can be created: - From the **Tasks** page - From an **item detail view** (linked to that item) - From a **contact detail view** (linked to that contact) Each task includes the following fields: | | | | -------------------------- | --------------------------------------- | | **Title** | What needs to be done | | **Description** (optional) | Detailed context about the task | | **Due date** | When the task is due | | **Due time** | Time of day for the task | | **Priority** | None, low, medium, high, or urgent | | **Task type** | To do, call, email, meeting, follow up | | **Assigned to** | The team member responsible | | **Duration** (optional) | Estimated time for the task in minutes | | **Reminder** (optional) | Get reminded before the task is due | | **Item link** (optional) | Connection to a pipeline item | | **Notes** (optional) | Additional context or follow up details | ## Views ### List view A sortable, filterable table of all tasks. Filter by: - Completion status (all, active, completed) - Priority (high, medium, low, none) - Task type (to-do, call, email, meeting, follow up) - Search ### Calendar view Tasks are displayed on a calendar with three view modes: | | | | -------------- | -------------------------------------- | | **Day view** | Hour-by-hour breakdown of a single day | | **Week view** | Seven day overview with time slots | | **Month view** | Full month grid with task indicators | ## Completing tasks Click the **"Complete"** button on a task to mark it as done. Completed tasks can also be reopened. ## Visibility Tasks respect your company's access levels: - **Regular users** see tasks assigned to them plus tasks they created - **Admins** see all tasks across the company - Tasks linked to items inherit the item's pipeline permissions. If a user cannot access the pipeline, they will not see tasks linked to its items. You can also create tasks from a **contact detail view**, linking the task to that contact for consolidated tracking. # Duplicate Detection Duplicate detection validates incoming items against existing records before creation, preventing redundant entries across pipelines. ## Configuration Set up duplicate detection per pipeline: 1. Open your pipeline settings 2. Enable **Duplicate Detection** 3. Choose which fields to match on (e.g., email, phone, company name) 4. Set the **match mode**: - **Exact**: fields must match character-for-character (case-insensitive) - **Fuzzy**: fields are compared using similarity scoring, catching near matches like typos or abbreviations 5. Set the **scope**: - **Current pipeline**: only check for duplicates within the same pipeline - **All pipelines**: check across every pipeline in the company 6. Choose the **on duplicate** behavior ## On duplicate behavior | | | | ---------- | ------------------------------------------------- | | **Warn** | Item is created, but a duplicate warning is shown | | **Skip** | Item is not created if a match is found | | **Update** | Existing item is updated with the new data | ## Where it applies All creation paths use the same detection logic, ensuring consistent behavior regardless of how the item is created: | | | | -------------------- | ----------------------------------------------------------------------------------------------------- | | **Manual creation** | Shows a warning dialog listing matched items with options to view the match, create anyway, or cancel | | **CSV import** | Applies the configured on duplicate behavior row by row during import | | **Inbound webhooks** | Applies the configured on duplicate behavior automatically | | **Inbound email** | Applies the configured on duplicate behavior when an inbound email creates a new item | # Automations Multi step workflows that execute automatically based on triggers. ## Triggers An automation starts when a trigger fires: | | | | ------------------ | ---------------------------------------- | | **Item created** | When a new item is added to the pipeline | | **Item updated** | When an item's fields change | | **Stage changed** | When an item moves to a specific stage | | **Status changed** | When an item's status changes | | **Scheduled** | Runs on a recurring schedule | | **Date field** | Fires when a date field value is reached | ## Steps Each automation is a sequence of steps: | | | | ------------------ | ----------------------------------------------------------------------------------- | | **Action** | Do something (send email, change stage, assign user, create proposal, send webhook) | | **Wait** | Pause for a duration (e.g., wait 2 days) | | **Wait until** | Pause until a condition is met or a date is reached | | **Condition gate** | Continue only if a condition is true | | **Branch** | Split into different paths based on conditions | ## Actions | | | | ------------------- | ----------------------------------------------------------- | | **Change stage** | Move the item to a different stage | | **Change status** | Set the item's status (e.g., mark as Won) | | **Assign user** | Assign a team member to the item | | **Send email** | Send an email using a template, with variable interpolation | | **Create proposal** | Automatically generate a proposal from a template | | **Send webhook** | POST item data to an external URL | ## Email template variables When an automation sends an email, the following variables are available in the template: | | | | -------------------- | -------------------------------------- | | **{contact\_name}** | Name of the contact linked to the item | | **{contact\_email}** | Email of the linked contact | | **{item\_title}** | Item title | | **{stage\_name}** | Current stage | | **{status\_name}** | Current status | | **{assigned\_to}** | Assigned user | | **{company\_name}** | Your company name | ## Example workflows ### Follow up email after 3 days 1. **Trigger:** Item created 2. **Wait:** 3 days 3. **Condition:** Status is still "Open" 4. **Action:** Send follow up email ### Automatically assign based on source 1. **Trigger:** Item created 2. **Branch:**Check item source field - If "Website" → Assign to Sales Team A - If "Referral" → Assign to Sales Team B - Default → Assign to Sales Manager ### Stale deal reminder 1. **Trigger:** Scheduled (daily) 2. **Condition:** Item hasn't moved stages in 14 days 3. **Action:** Send notification to assignee ## Templates Ready-made automation templates are available to help you get started quickly: | | | | ----------------------- | ---------------------------------------------------------------------------- | | **Email follow up** | Sends a follow up email after a configurable delay if the item is still open | | **Stale deal reminder** | Notifies the assignee when an item hasn't moved stages within a set period | | **Lead assignment** | Automatically assigns new items to team members based on field values | | **Proposal follow up** | Sends a reminder email after a proposal has been sent but not yet accepted | Select a template when creating a new automation and customize it for your workflow. ## Run history Each automation tracks its execution history. Open an automation's summary dialog to see: - A visual **workflow diagram** showing the trigger, conditions, and each step with icons - **Run history** with status filter (All, Running, Waiting, Completed, Failed, Cancelled) - Expandable run details with a step-by-step **timeline** showing what happened at each step - Running or waiting instances can be **cancelled** at any time ## Managing automations - Go to **Settings → Company Settings → Automations** - **Create** new automations - **Toggle** automations on/off without deleting them - **Duplicate** an automation to use as a starting point - **Reorder** automations to control execution priority # Inventory A product catalog with automatic stock management. Stock is held when proposals are sent, decremented when invoices are created, and restored when documents are deleted. ## Products Create and manage your product catalog: | | | | ---------------------------------- | --------------------------------------------------------------------------------- | | **Name** | Product display name | | **Product type** | Physical, digital, or service | | **Unit cost** | Cost per unit | | **Unit price** | Selling price per unit | | **Currency** | Currency for pricing | | **Description** (optional) | Detailed product description | | **SKU** (optional) | Stock keeping unit identifier | | **Tax percent** (optional) | Default tax rate | | **Track inventory** | Enable to track stock levels | | **Stock quantity** (optional) | Total stock on hand | | **Low stock threshold** (optional) | Triggers a notification to admins when stock falls below this level | | **Allow oversell** | When enabled, proposals and invoices can be created even if stock is insufficient | Go to **Settings → Inventory** to manage products. ## Stock levels Products with inventory tracking show three stock values: | | | | ------------- | ----------------------------------------------------------------------- | | **Stock** | Total units on hand | | **On Hold** | Units reserved by sent proposals (highlighted in amber when above zero) | | **Available** | Stock minus held. This is what can be committed to new orders | ## Automatic stock management Stock adjusts automatically throughout the proposal and invoice lifecycle: | | | | -------------------------------- | ------------------------------------------------------------------------------------------- | | **Proposal sent** | Stock is placed on hold for each product in the line items | | **Proposal rejected or expired** | Held stock is released back to available | | **Proposal deleted** | Held stock is released | | **Invoice created** | Stock is decremented. If the invoice was created from a proposal, the hold is also released | | **Invoice updated** | Old line item stock is restored, new line item stock is applied | | **Invoice deleted** | Stock is restored to previous levels | If a product has **Allow oversell** disabled and available stock is insufficient when sending a proposal, a warning is shown but the proposal can still be sent. ## Low stock notifications When an invoice sale brings a product below its **low stock threshold**, all company admins receive an in-app notification with the product name and current stock level. ## Stock adjustments Record manual stock changes with a reason: | | | | -------------- | ------------------------------- | | **Restock** | Received new inventory | | **Sale** | Manual sale outside of invoices | | **Return** | Customer returned items | | **Correction** | Inventory count adjustment | View the full **adjustment history** per product in the stock management view. Each entry shows the adjustment type, quantity change, before/after levels, and source. Entries created by proposals or invoices link back to the originating document. ## Bulk updates Update stock levels for multiple products at once using the bulk update dialog. ## Using products in documents Products serve as the line item catalog for proposals and invoices. When adding a line item: - Select a product from the catalog - Name, description, SKU, and price fill automatically - Adjust quantity and override the price if needed - Stock is managed automatically when the document is sent or created # Proposals Generate professional proposals with PDF output and delivery tracking. ## Creating a proposal 1. Open an item's detail view 2. Go to the **Proposals** tab 3. Click **"Create Proposal"** 4. Add line items if needed (description, quantity, unit price). Line items are optional. 5. Save and preview You can also create proposals from **templates** with layouts and field mappings that automatically fill from item and contact data. ## Proposal templates Templates define the PDF layout and which fields to pull from the item: - Go to **Settings → Proposals → Templates** - Use the **PDF designer** to customize the layout - Map template variables to pipeline fields - Create multiple templates for different use cases (quote, contract, SOW) Template presets are available for common formats. Variables like `{contact_name}`, `{contact_email}`, and `{item_title}` are resolved automatically from the item's linked contact. ## PDF preview Click **"Preview"** on a proposal to generate and view the PDF in a new browser tab. If the proposal already has a saved PDF, it opens directly. ## Sending proposals Once a proposal is ready: | | | | ----------------- | ------------------------------------------------ | | **Send by email** | The contact receives a link to view the proposal | | **Copy link** | Share the public proposal URL directly | When a proposal is sent, stock is automatically placed on hold for any tracked products in the line items. See [Inventory](https://docs.slate.zerulean.com/features/inventory) for details. ## E-Signatures Slate supports two e-signature providers: | | | | ----------------------------------------------------- | -------------------------------------------------------------------------------------------- | | **SES (Simple Electronic Signature)** | Built-in. The signer receives a consent page, acknowledges what data is collected, and signs | | **AES/QES (Advanced/Qualified Electronic Signature)** | Available via DocuSign. Bring your own DocuSign credentials to enable | To send a proposal for signature: 1. Click **"Send for Signature"** on a proposal 2. The signer receives a link to a **consent page** 3. The consent page shows what data will be collected (name, email, IP, timestamps) 4. After acknowledging, the signer is redirected to sign Track signature status: pending, signed, declined, or voided. ## Converting to invoice When a proposal is accepted, a **"Convert to Invoice"** button appears in the proposal detail. Clicking it creates an invoice with all line items carried over. Only one invoice can be created per proposal. If the proposal template has **auto-create invoice** enabled, an invoice is generated automatically when the customer accepts. ## Compliance & retention Proposals are retained for **7 years** in accordance with compliance requirements. Signature requests associated with proposals follow the same 7-year retention period. After the retention period expires, records are purged automatically. # Invoices Full invoice lifecycle management with line items, PDF preview, and payment tracking. ## Creating an invoice Invoices can be created in two ways: | | | | ------------------- | ---------------------------------------------------------------------------------------------------- | | **Manually** | From the item detail view, Invoices tab | | **From a proposal** | Click "Convert to Invoice" on an accepted proposal, or enable auto-creation in the proposal template | ### Manual creation 1. Open an item's detail view 2. Go to the **Invoices** tab 3. Click **"Create Invoice"** 4. Set a title, currency, and optionally a due date and template 5. Add line items from your product catalog 6. Add client notes and terms & conditions When an invoice is created with tracked products, stock is automatically decremented. See [Inventory](https://docs.slate.zerulean.com/features/inventory) for details. ## PDF preview Click **"Preview"** on an invoice to generate and view the PDF in a new browser tab. Template variables like `{contact_name}` and `{contact_email}` are resolved from the item's linked contact. ## Sending invoices | | | | ----------------- | ----------------------------------------------- | | **Send by email** | The contact receives a link to view the invoice | | **Copy link** | Share the public invoice URL directly | ## Public invoice page Each invoice has a public viewing page. Recipients can view the full invoice with line items, totals, and payment terms without needing a Slate account. ## Recording payments Track payments against invoices: | | | | ------------------ | ------------------------------------- | | **Unpaid** | No payments have been recorded | | **Partially Paid** | Some amount received, balance remains | | **Paid** | Full amount has been received | Record partial or full payments with amount and date. View complete payment history per invoice. ## Deleting invoices Only draft invoices can be deleted. Invoices that have been sent, viewed, or paid cannot be deleted. When a draft invoice is deleted, stock is automatically restored for any tracked products. ## Compliance & retention Invoices are retained for **10 years** to meet tax and legal compliance requirements. Associated files (PDFs, signed documents) follow the same 10-year retention period. Expired records are purged automatically. # Reports Reports for pipeline performance analysis across seven report types. ## Available reports | | | | ------------------- | ---------------------------------------------------------------------------------------------------------------- | | **Pipeline Funnel** | Conversion rates between stages. See where items drop off and which stages have the highest throughput. | | **Deal Velocity** | Average time items spend in each stage, helping identify bottlenecks in your workflow | | **Activity** | Activity volume over time broken down by type (notes, emails, calls, meetings) | | **Win/Loss** | Win rate percentage, loss reasons distribution, and status breakdown over time | | **Revenue** | Revenue totals by period, stage, and status. Requires a revenue field configured in pipeline settings. | | **Trends** | Item creation and movement trends over time with volume patterns | | **Forecast** | Weighted pipeline value by stage combined with time bucketed revenue projections based on current pipeline state | To use revenue and forecast reports, configure a **revenue field** in your pipeline's reporting settings. Win/loss reports require at least one stage or status to be designated as **won** or **lost**. If your pipeline uses multiple currencies, revenue data is displayed with separate breakdowns per currency. ## Filters All reports support: | | | | --------------------- | -------------------------------------- | | **Date range** | Pick a period with the calendar picker | | **Pipeline selector** | Filter to a specific pipeline | ## CSV export Export any report's data as a CSV file for further analysis in spreadsheets or BI tools. ## How it works Reports refresh daily, so they reflect data as of the previous day's close. This approach ensures fast load times even with large datasets. # Analytics A real time executive dashboard for monitoring your key performance indicators. ## KPI Grid A grid of KPI cards displaying your most important metrics at a glance: | | | | ------------------------- | --------------------------------------------------- | | **Total items** | Active items across selected pipelines | | **New items** | Items created within the selected period | | **Conversion rate** | Percentage of items reaching a "won" status | | **Revenue** | Total value of won items (requires a revenue field) | | **Average deal size** | Mean value of closed items | | **Average time to close** | Mean duration from creation to won status | Each KPI card shows the current value along with a trend indicator comparing against the previous period. Revenue metrics are displayed per currency when multiple currencies are used. ## Pipeline Funnel Visualize how items flow through your pipeline stages with a funnel chart. Each band represents a stage, with width proportional to the number of items. Identify exactly where drop-offs occur and which stages act as bottlenecks. ## Item Trends Track item creation and movement patterns over time with a time series chart. See daily, weekly, or monthly volume of new items entering and exiting your pipeline to spot seasonal patterns and growth trends. # Guides Operational walkthroughs for configuration, daily use, and administration. ## Configuration - [Create a pipeline](https://docs.slate.zerulean.com/guides/create-a-pipeline) - [Add custom fields](https://docs.slate.zerulean.com/guides/add-custom-fields) - [Invite team members](https://docs.slate.zerulean.com/guides/invite-your-team) - [Configure an email domain](https://docs.slate.zerulean.com/guides/set-up-email-domain) ## Operations - [Manage items](https://docs.slate.zerulean.com/guides/manage-items) - [Send a proposal](https://docs.slate.zerulean.com/guides/send-a-proposal) - [Create an invoice](https://docs.slate.zerulean.com/guides/create-an-invoice) - [Track tasks](https://docs.slate.zerulean.com/guides/track-tasks) ## Automation & Integration - [Configure an automation](https://docs.slate.zerulean.com/guides/first-automation) - [Capture leads via web form](https://docs.slate.zerulean.com/guides/capture-leads) - [Connect an external tool via webhook](https://docs.slate.zerulean.com/guides/connect-webhook) - [Import data from CSV](https://docs.slate.zerulean.com/guides/import-from-csv) ## Account & Security - [Add a passkey](https://docs.slate.zerulean.com/guides/add-passkey) - [Enable two factor authentication](https://docs.slate.zerulean.com/guides/enable-two-factor-auth) - [Sync Google Calendar](https://docs.slate.zerulean.com/guides/sync-google-calendar) # Create a Pipeline A pipeline is how you model a workflow in Slate. Whether you are tracking deals, support tickets, or hiring candidates, this guide covers every setting available, from the basics to advanced features like lead scoring and duplicate detection. ## Step 1: Create the pipeline Go to your company **Dashboard** and click **"Create Pipeline"**. ### Name and sort order | | | | -------------- | ---------------------------------------------------------------------------------------- | | **Name** | Enter a descriptive name such as "Enterprise Sales", "Support Tickets", or "Recruitment" | | **Sort order** | Controls the order of pipeline tabs on your dashboard. Lower numbers appear first | ### Templates or blank pipeline You can start with a blank pipeline and configure everything yourself, or select a **template** to get preconfigured stages, statuses, and fields that you can customize later: | | | | --------------- | ----------------------------------------------------------------------------------------------- | | **Sales** | B2B or B2C deal tracking with stages like Lead, Qualified, Proposal, Negotiation, Won, and Lost | | **Recruitment** | Hiring workflows from Applied through Screening, Interview, Assessment, Offer, and Hired | | **Real Estate** | Property sales with New Lead, Viewing Scheduled, Under Offer, Sold, and Lost | | **Support** | Customer support tickets moving through New, In Progress, Waiting, and Resolved | | **Software** | Software and SaaS sales cycles | | **Solar** | Renewable energy project sales | | **Shop** | Retail and e-commerce operations | | **Bakery** | Bakery order and production tracking | Templates also include suggested fields. For example, the Sales template adds a currency field for deal value, a dropdown for lead source, and a date field for expected close. ## Step 2: Configure stages Stages are the **columns on your Kanban board**. As items move through your process, they move across stages from left to right. ### Adding a stage Click **"Add Stage"** and configure: | | | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Name** | Use process oriented labels like "Qualified", "Under Review", or "Awaiting Approval" | | **Sort order** | Determines column position. Lower numbers sit further left | | **Icon** (optional) | A visual identifier displayed alongside the stage name. Recommended for a cleaner UI | | **Display type** | How statuses within this stage appear, either as a **count** (number badge) or as **icons**. This is set when you create the first status in the stage | ### Designing your stage structure Stages should represent decision points in your process, not individual tasks: ::prose-pre{title="Sales example"} Lead → Discovery → Proposal → Negotiation → Contract → Closed :: ::prose-pre{title="Support example"} New → Triaged → In Progress → Waiting on Customer → Resolved :: ::prose-pre{title="Recruitment example"} Applied → Phone Screen → Technical Interview → Final Round → Offer → Hired :: The number of stages depends on your workflow and how your teams are organized. Since [stage level permissions](https://docs.slate.zerulean.com/core-concepts/teams) allow you to control which teams see which stages, you can structure your pipeline to match your access requirements. You can **reorder stages** at any time by changing their sort order. Existing items stay in their current stage when you do. ## Step 3: Configure statuses Statuses are **optional substeps within a stage** that help you track exactly where an item stands. For example, a "Proposal" stage might have statuses like "Draft", "Sent", and "Reviewed". ### Adding a status Within a stage, click **"Add Status"** and configure: | | | | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | A short label for the sub-step | | **Sort order** | Position within the stage | | **Icon** | Required when the display type is set to icon. Otherwise optional but recommended for a cleaner UI | | **Display type** | Either count or icon. The first status you create in a stage sets the display type, and all subsequent statuses in that stage follow the same type | ### Example status setups | | | | --------------------------------- | --------------------------------------------- | | **Sales → Proposal stage** | Draft, Sent, Reviewed, Revised | | **Support → In Progress stage** | Investigating, Waiting on Customer, Escalated | | **Recruitment → Interview stage** | Scheduled, Completed, Feedback Pending | For reporting, you can mark specific statuses as **Won** or **Lost** in the [reporting configuration](https://docs.slate.zerulean.com/#step-6-reporting-configuration) below. This powers win/loss rates and revenue reports without changing how statuses work day-to-day. ## Step 4: Define your blueprint A **blueprint** is a collection of fields that defines what data you capture per item. Before you can add items to your pipeline, you need to create at least one blueprint. This is the form your team fills out when creating or updating an item. ### Blueprint basics | | | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Blueprint** | A named set of fields that customizes your item forms. A blueprint is required before you can add items to the pipeline | | **Versioning** | Each time you change a blueprint, a new version is created. Previous versions are preserved, so your historical data stays consistent | | **Multiple blueprints** | You can create more than one blueprint per pipeline, useful when you track different item types (e.g., "Individual" and "Corporate" in a sales pipeline) | Open **"Manage Blueprints"** from your pipeline settings to create, edit, or delete blueprints. ### Built-in fields Every blueprint includes built in fields. **Name** and **Contact Type** are always present, while **Email** and **Phone Number** can be toggled on or off: | | | | --------------------------- | ------------------------------------------------------------------------- | | **Name** | Item name or title. Always enabled | | **Contact Type** | Whether the item represents a person, company, or neither. Always enabled | | **Email** (optional) | Contact email with format validation | | **Phone Number** (optional) | Contact phone number | Each item also receives an automatically generated **Short ID** for easy reference. This is assigned automatically and cannot be edited. ### Field categories Fields are organized into five categories. Each category has distinct types, and some types offer multiple **display variants**. For example, a single select field can appear as a dropdown, radio buttons, cards, inline buttons, or a listbox. #### Input fields | | | | ----------------------- | --------------------------------------------------------------------------- | | **File Upload** | Single or multiple file upload with configurable file types and size limits | | **Text Input** | Short text with format validation | | **Decimal Number** | Numeric input with decimal precision | | **Integer Number** | Whole numbers only | | **Currency** | Monetary value with currency code, symbol, and formatting | | **URL** | Validated URL input | | **Email** | Validated email address | | **Phone Number** | Standard phone number | | **International Phone** | Phone with country code selector | | **Custom Format** | Text input with a custom validation pattern | | **Multi-line Text** | Textarea for longer content | | **Validated Text Area** | Textarea with format validation | Additional categories include **Radio** (single select), **Select** (multi select), **Checkbox** (multi select toggle), and **Date/Time** fields, each with multiple display variants. You can explore all available types and variants in the field builder when adding a field to your blueprint. ### Field configuration Every field supports these settings: #### Core properties | | | | ---------------------------- | ------------------------------------------------------------ | | **Label** | The name shown to users (e.g., "Deal Value", "Company Size") | | **Name** | A unique identifier within the blueprint | | **Description** (optional) | Help text displayed below the field | | **Required** | When on, the item cannot be saved without filling this field | | **Default value** (optional) | Pre-filled value when creating a new item | #### Stage assignment | | | | ------------------- | ---------------------------------------- | | **Specific stage** | Field only appears in one stage | | **Multiple stages** | Field appears in the stages you pick | | **All stages** | Field appears everywhere in the pipeline | This controls where the field shows up. For example, a "Rejection Reason" field might only appear in the final stage. #### Display options | | | | ------------------------- | --------------------------------------------------------------------------------------------------- | | **Display order** | Where the field sits relative to others. Lower numbers appear first | | **Show on hover** | Displays the field value when hovering over an item on the board | | **Show in detail view** | Displays the field when clicking on an item to view its details | | **Read-only after stage** | Locks the field once the item moves past a certain stage (e.g., lock "Deal Value" after "Contract") | #### Validation rules | | | | -------------------- | ------------------------------------------------------- | | **Min / Max value** | Restrict the numeric range (number and currency fields) | | **Min / Max length** | Restrict character count (text fields) | | **Pattern** | Custom format validation using regex (text fields) | | **Integer only** | Reject decimal values (number fields) | | **Positive only** | Reject negative values (number fields) | #### Currency specific settings | | | | ---------------------- | ---------------------------------------- | | **Currency code** | Standard code like EUR, USD, GBP, or INR | | **Currency symbol** | Display symbol (€, $, £, etc.) | | **Symbol position** | Before the value, after, or both | | **Decimal precision** | Number of decimal places | | **Allow negative** | Whether negative amounts are permitted | | **Allowed currencies** | Restrict which currencies are available | #### File upload settings | | | | ------------------ | --------------------------------------------------------------- | | **Multiple files** | Allow uploading more than one file | | **Accepted types** | Restrict to specific file types (e.g., images, PDFs, documents) | | **Max file size** | Size limit per file | | **Max file count** | Maximum number of files when multiple uploads are enabled | #### Option configuration (Radio, Select, Checkbox) For fields with predefined choices, each option supports: | | | | -------------------------- | ------------------------------------------------------------------------------------- | | **Label** | The display text | | **Sublabel** (optional) | Secondary descriptive text | | **Description** (optional) | Additional detail shown below the option | | **Icon** (optional) | A visual identifier from the icon library. Recommended for options with icons enabled | | **Default** (optional) | Pre-selected state when the form loads | #### Card indicators Card indicators add visual markers to items on the Kanban board based on field values. | | | | ------------ | ---------------------------------------------------------------------------------------------------- | | **Enabled** | Toggle indicators on or off | | **Position** | Show on the left side of the item card, either at the top (alongside the item name) or at the bottom | | **Mappings** | For text fields: map values to icons using exact match, contains, or pattern matching | For select and radio fields, card indicators use the field options' icons directly. #### Card background color You can also bind a field to control the background color of item cards on the board. When enabled, each item card is color coded based on the field's value. | | | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Enabled** | Toggle card color binding on or off | | **Color mappings** | For option based fields (radio, select, checkbox), assign a color to each option. For text fields, map values to colors using match rules | This is useful for visually distinguishing items at a glance, such as color coding by priority, status, or category. ## Step 5: Pipeline settings Once your pipeline is set up, you can fine-tune a few additional options. ### Self-assignment | | | | --------------- | ------------------------------------------------------------------------------------- | | **Self-assign** | Allows users to assign themselves to items without needing an admin to do it for them | ### Default contact type | | | | ------------------------ | ----------------------------------------------------------------- | | **Default contact type** | Whether new items default to a "person" or "company" contact type | ### Email conversations | | | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | **Conversations enabled** | Turns items into email threads. Your team can send and receive emails directly from the item detail view, with a shared inbox for the whole pipeline | This requires an [email domain](https://docs.slate.zerulean.com/guides/set-up-email-domain) to be set up. Messages can be **public** (customer-facing) or **internal** (team-only). See [Conversations & Inbox](https://docs.slate.zerulean.com/features/conversations) for more. ## Step 6: Reporting configuration Connect your pipeline to the reporting engine so revenue, win/loss, and funnel reports reflect accurate data. ### Revenue field | | | | ----------------------- | ------------------------------------------------------------------------------------------ | | **Revenue field** | Pick which currency field represents the monetary value of your items (e.g., "Deal Value") | | **Multiple blueprints** | If you have more than one blueprint, you can map a revenue field for each | ### Won and lost designations You can mark stages, statuses, or a combination of both as won or lost. This is flexible since statuses are optional. | | | | -------- | ------------------------------------------------------------------------------------------------ | | **Won** | Which stages or statuses count as a successful outcome. Used for win rate and revenue reports | | **Lost** | Which stages or statuses count as an unsuccessful outcome. Used for loss rate and churn analysis | A stage or status cannot be both won and lost. These designations power the [Reports](https://docs.slate.zerulean.com/features/reports) and [Analytics](https://docs.slate.zerulean.com/features/analytics) dashboards. ## Step 7: Duplicate detection Catch duplicate records before they are created. ### Configuration | | | | ---------------- | ----------------------------------------------------------------------------- | | **Enabled** | Turn duplicate detection on or off | | **Match fields** | Which fields to compare, such as email, phone, name, or any custom text field | | **Match mode** | Match if **any** selected field matches, or only when **all** of them match | | **Scope** | Check within this pipeline only, or across every pipeline in the company | | **On duplicate** | What should happen when a match is found | ### On duplicate behavior | | | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Warn** | The item is still created, but a warning with the matched records is displayed. On manual creation, a dialog allows you to view the match, create anyway, or cancel | | **Skip** | The item is not created. The existing match is returned instead | | **Update** | The existing item is updated with the incoming data | This works the same way everywhere: manual creation, CSV imports, inbound webhooks, and inbound emails. See [Duplicate Detection](https://docs.slate.zerulean.com/features/duplicate-detection) for more. ## Step 8: Lead scoring Score items automatically based on field values so your team can focus on the highest-potential leads. ### Enable scoring Toggle **Lead Scoring** on in your pipeline settings and set a **max score** to cap the total. ### Scoring rules Each rule evaluates a field value and adds or subtracts points: | | | | ------------ | ------------------------------------------------------------------------------------------- | | **Field** | Any built in field (email, phone, name, stage, status, source) or custom field | | **Operator** | Equals, not equals, contains, not contains, greater than, less than, is empty, is not empty | | **Value** | The value to compare against | | **Points** | How many points to add or subtract when the rule matches | **Example rules for an enterprise sales pipeline:** - "Deal Value" greater than 50,000 → +25 points - "Source" equals "Referral" → +15 points - "Company Size" equals "Enterprise" → +20 points - "Email" is empty → -10 points - "Stage" equals "Negotiation" → +10 points Scores update automatically whenever items are created or modified. ### Score decay You can enable **score decay** to gradually reduce scores on items that have not been updated: | | | | ----------------------- | -------------------------------------------------- | | **Decay enabled** | Toggle decay on or off | | **Interval** | How often points are deducted (e.g., every 7 days) | | **Points per interval** | How many points are subtracted each time | ### Card colors You can color code item cards on the board based on their score. Define thresholds like green for high scores, yellow for medium, and red for low, so the most promising leads stand out at a glance. Thresholds are fully configurable. After changing rules, click **"Recompute Scores"** to recalculate all items. See [Lead Scoring](https://docs.slate.zerulean.com/features/lead-scoring) for more. ## Step 9: Start adding items Return to your dashboard, select the pipeline, and click **"Add Item"**. Fill in the fields from your blueprint and save. Your first card appears on the Kanban board. ## What to configure next With your pipeline up and running, here are some natural next steps: - [Add custom fields](https://docs.slate.zerulean.com/guides/add-custom-fields) to extend your blueprint as your process evolves - [Invite team members](https://docs.slate.zerulean.com/guides/invite-your-team) and set roles and team permissions - [Configure an automation](https://docs.slate.zerulean.com/guides/first-automation) to trigger actions on stage changes, field updates, or schedules - [Capture leads via web form](https://docs.slate.zerulean.com/guides/capture-leads) by embedding a form on your site - [Connect a webhook](https://docs.slate.zerulean.com/guides/connect-webhook) to receive items from tools like Zapier, Make, or n8n - [Import from CSV](https://docs.slate.zerulean.com/guides/import-from-csv) to bring in existing data in bulk # Add Custom Fields Custom fields define the data model for each pipeline, determining what information you capture per item. ## Where to add fields 1. Go to **Settings → Company Settings → Pipelines** 2. Select the pipeline you want to edit 3. Open the blueprint editor ## Choosing field types Fields are organized into five categories (Input, Radio, Select, Checkbox, Date), each with multiple display variants. The most common: | | | | ---------------------------- | ------------------------------------ | | **Text input** | Name, company, notes | | **Email** | Email address (validates format) | | **Phone** | Phone number | | **URL** | Website | | **Currency** | Dollar amount (with currency symbol) | | **Number** | Numeric value | | **Dropdown / Radio buttons** | Choose one option | | **Checkbox group** | Choose multiple options | | **Date picker** | A date | | **File upload** | File attachment | ## Adding a field 1. Click **"Add Field"** in the blueprint editor 2. Pick a field type and variant from the gallery 3. Enter a label and name (e.g., "Deal Value", "Company Size") 4. Configure settings: - **Required** – must be filled before saving - **Options** – for dropdowns, radio, and checkbox fields, define the available choices - **Validation** – min/max values, character limits, or regex patterns depending on field type - **Currency** – for currency fields, set the currency code, symbol, and formatting - **File settings** – for file uploads, set accepted types and size limits - **Stage assignment** – control which stages the field appears in - **Display** – configure show on hover, show in detail view, and read-only after stage - **Card indicator** – display an icon on item cards based on the field value - **Card background color** – color code item cards based on the field value ## Reordering fields Drag fields up or down to change the order they appear in the form and on item cards. ## Visual customization You can bind fields to visual elements on item cards for quick information at a glance: | | | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Card indicator** | Display an icon on item cards based on the field value. For option based fields, each option can have its own icon. For text fields, map values to icons using match rules | | **Card background color** | Color code item cards on the board based on a field value. Assign colors per option, or define match rules for text fields | ## Stage and visibility control Fields can be scoped to specific stages and locked at certain points in the workflow: | | | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | **Stage assignment** | Control which stages the field appears in. A field can appear in one stage, multiple stages, or all stages | | **Read-only after stage** | Lock the field once an item moves past a certain stage. Useful for preventing changes to values like "Deal Value" after a contract is signed | | **Show on hover** | Display the field value when hovering over an item card on the board | | **Show in detail view** | Display the field when clicking on an item to view its details | ## Best practices - Start with essential fields. You can add more at any time without affecting existing data. - Use **dropdown** fields for data you want to filter or report on (e.g., Source, Industry, Priority). - Use **currency** fields instead of plain numbers for monetary values. They format automatically. # Invite Team Members Add users to your company workspace with configurable access levels for collaboration across pipelines. ## Inviting users 1. Go to **Settings → Company Settings → Users** 2. Click **"Invite"** 3. Enter their email address 4. Click **Send** The invitee receives an email with a link to accept the invitation. To accept, they log into their Slate account (or create one if they do not have one yet). They join the company as a **Member** by default. ## Managing users From **Settings → Company Settings → Users** you can promote members to **Admin**, remove admin access, or remove users from the company. | | | | ---------- | ---------------------------------------------------------------------------------------- | | **Admin** | Can create and update items, pipelines, teams, and add members | | **Member** | Can work with items, contacts, and tasks within pipelines and stages they have access to | ## Setting up teams Teams are separate from user roles. While a user's role controls what they can do company wide, **teams** control what users can see at the pipeline and stage level. 1. Go to **Settings → Company Settings → Teams** 2. Create a team (e.g., "Sales", "Support", "Engineering") 3. Add members to the team 4. Assign the team permissions on specific pipelines or stages For example, your "Sales" team might have access to the Sales pipeline but not the Support pipeline. A user who is a Member with the "Sales" team only sees the pipelines and stages that team has been granted access to. See [Teams & Permissions](https://docs.slate.zerulean.com/core-concepts/teams) for more details. # Configure Email Domain Configure a verified email domain so you can send all outbound communication from your organization's address (e.g., `team@yourbusiness.com`). ## Step 1: Add your domain 1. Go to **Settings → Company Settings → Email Domains** 2. Click **"Add Domain"** 3. Enter your domain (e.g., `yourbusiness.com`) ## Step 2: Add DNS records Slate displays the DNS records you need to add. Go to your domain registrar (GoDaddy, Cloudflare, Namecheap, etc.) and add: - **DKIM** records for email authentication - **SPF** record to authorize Slate to send on your behalf Copy each record exactly as shown. ## Step 3: Verify Click **"Verify"** in Slate. Verification may take a few minutes depending on DNS propagation. ## Step 4: Add senders Once verified, add email addresses you want to send from: 1. Go to the **Senders** section 2. Add addresses like `sales@yourbusiness.com` or `support@yourbusiness.com` 3. Set one as the **default sender** ## Result All outbound email from conversations, automations, and document notifications will be delivered from your verified domain. To also receive inbound email (for conversations), contact support to configure inbound routing for your domain. # Manage Items Items are the primary records in a pipeline, each representing a deal, ticket, candidate, or other entity moving through your workflow. ## Creating an item 1. Click the **"+ Add Item"** button on your dashboard 2. If you have multiple blueprints, pick one 3. Fill in the fields 4. Click **Save** Your new item appears as a card in the first stage. Each item receives an automatically generated **short ID** for easy reference. If your pipeline has [duplicate detection](https://docs.slate.zerulean.com/features/duplicate-detection) enabled, Slate checks for matches before creation and may show a warning dialog with potential duplicates. ## Viewing an item **Hover** over a card to see a quick summary of the item's key fields. **Click** a card to open the full detail view, which includes: | | | | -------------------- | ------------------------------------------------------------------ | | **Overview** | Summary of the item with key fields, assignees, and linked contact | | **Fields** | All field values with inline editing | | **Activity** | Notes, calls, emails, meetings, and conversation messages | | **Proposals** | Linked proposals (if enabled) | | **Invoices** | Linked invoices (if enabled) | | **Tasks** | Tasks linked to this item | | **Automations** | Active automation instances running on this item | | **Progression Logs** | History of stage and status changes over time | ## Editing an item Fields are editable inline within the detail view. Changes persist automatically. ## Moving items between stages Items progress through statuses and stages: | | | | ----------------- | ---------------------------------------------------------------------------------------- | | **Next button** | In the detail view, use the next button to progress through statuses and stages in order | | **Drag and drop** | On the board, drag a card and drop it into another stage column | ## Assigning team members Click the assignee area on a card (or in the detail view) to assign team members. You can: - Assign multiple people - Set a **primary** assignee - Self-assign with one click ## Adding activity In the item detail view, use the activity form to log: | | | | ------------ | ----------------------------- | | **Notes** | Free-text updates | | **Calls** | Log a phone call with outcome | | **Emails** | Record email interactions | | **Meetings** | Log meetings | ## Deleting items Open the item detail and use the delete option. Deleted items can be restored from **Settings → Company Settings → Deleted Items** within 7 days. After that, they are permanently removed. ## Filtering items Use the toolbar above your board: | | | | ------------ | ----------------------------------------- | | **My Items** | Toggle to show only items assigned to you | | **Search** | Find items by name or short ID | # Send a Proposal Create a proposal, send it to your contact via email or shared link, and track whether it is accepted or rejected. ## Step 1: Open the item Navigate to the item you want to create a proposal for and open its detail view. ## Step 2: Go to the Proposals tab Click the **Proposals** tab in the item detail. ## Step 3: Create the proposal Click **"Create Proposal"** and configure: | | | | --------------------------------- | ---------------------------------------------------------------------------------- | | **Title** | Name of the proposal | | **Currency** | Currency used for the proposal | | **Valid Until** (optional) | Expiry date for the proposal | | **Template** | Select a proposal template. A default template is preselected if one is configured | | **Line items** (optional) | Add products or services from your catalog with description, quantity, and price | | **Client Notes** (optional) | Notes visible to the recipient | | **Terms & Conditions** (optional) | Payment terms, conditions, or other details | ## Step 4: Download and review Once the proposal is created, you can download the PDF to review exactly what the recipient will see. ## Step 5: Send You have two options: | | | | ----------------- | --------------------------------------------- | | **Send by email** | Slate emails the proposal link to the contact | | **Copy link** | Copy the public URL and share it yourself | ## Recipient experience The recipient views the proposal on a public page and can: - **Accept** the proposal - **Reject** the proposal Status updates are reflected in the Proposals tab in real time. ## Requesting a signature With e-signatures enabled, select **"Send for Signature"** on the proposal. The flow: 1. A **consent page** link is generated for the signer 2. The consent page shows the company name, sender name, document title, and a **data disclosure** list (what will be collected: name, email, IP address, browser info, timestamps, geolocation) 3. The signer must acknowledge the disclosure before being redirected to the e-signature provider for signing 4. Track status with badges: **pending**, **signed**, **declined**, **voided** ## Converting to invoice You can convert accepted proposals to invoices directly. All line items carry over automatically. # Create an Invoice Generate invoices with line items and payment tracking. Invoices can also be generated automatically from a proposal when this option is enabled in the proposal template settings. Line items carry over automatically. ## Creating an invoice 1. Open an item's detail view 2. Go to the **Invoices** tab 3. Click **"Create Invoice"** and configure: | | | | --------------------------------- | -------------------------------------------------------------------------------- | | **Title** | Name of the invoice | | **Currency** | Currency used for the invoice | | **Due Date** (optional) | When payment is due | | **Template** (optional) | Select a template to automatically fill content | | **Line items** (optional) | Add products or services from your catalog with description, quantity, and price | | **Client Notes** (optional) | Notes visible to the recipient | | **Terms & Conditions** (optional) | Payment terms, conditions, or other details | ## Sending the invoice | | | | ----------------- | ------------------------------------------- | | **Send by email** | The contact receives a link to view and pay | | **Copy link** | Share the public invoice URL directly | ## Recording payments When you receive a payment: 1. Open the invoice 2. Click **"Record Payment"** 3. Enter the amount, date, and reference number 4. Save The invoice status updates automatically: | | | | ------------------ | -------------------- | | **Unpaid** | No payments recorded | | **Partially Paid** | Some amount received | | **Paid** | Full amount received | ## Managing invoices Invoices are managed from the item detail view under the **Invoices** tab. Invoice templates can be configured in **Settings → Invoices**. The public invoice page allows recipients to view the full invoice without a Slate account. Invoices are retained for **10 years** for tax and legal compliance. # Track Tasks Manage tasks and follow ups with assignment, priority levels, and calendar scheduling. ## Creating a task Tasks can be created from multiple places: | | | | ----------------------- | ---------------------------------------------------------------------------------------- | | **Tasks page** | Click **"Create Task"** from the list view, or click on a date in the calendar view | | **Item detail view** | Create a task from the Tasks tab. It automatically links to that item | | **Contact detail view** | Create a task from a contact. It automatically links to that contact | When creating a task, configure: | | | | --------------------------- | --------------------------------------------------------------------------- | | **Title** | What needs to be done | | **Description** (optional) | Additional context about the task | | **Type** | To do, call, email, meeting, follow up, etc. | | **Due date** | When it is due | | **Due time** | Time of day for the task | | **Priority** | None, low, medium, high, or urgent | | **Assigned to** | Who is responsible | | **Duration** (optional) | Estimated time for the task in minutes | | **Reminder** (optional) | Get reminded before the task is due | | **Notes** (optional) | Additional notes or follow up details | | **Link to item** (optional) | Connect to a pipeline item (automatically filled when created from an item) | ## Viewing tasks Switch between two views: | | | | ----------------- | ------------------------------------------------------------------ | | **List view** | Sortable table with filters for status, priority, type, and search | | **Calendar view** | See tasks on a day, week, or month calendar | ## Completing a task Click the **"Complete"** button on a task to mark it as done. Completed tasks can also be reopened. ## Best practices - Use **high priority** for time sensitive follow ups - Link tasks to items to consolidate all related activity - Set due dates so tasks show up on the calendar at the right time # Configure an Automation This guide walks you through creating a common automation: a delayed follow up email triggered by item creation. ## Step 1: Open automations Go to **Settings → Company Settings → Automations** and click **"Create Automation"**. You can start with a blank automation or choose a template to get started faster. ## Step 2: Set the trigger Choose **"Item created"** as the trigger. This fires whenever a new item is added to the pipeline. ## Step 3: Add a wait step Click **"Add Step"** and choose **Wait**. Set it to **3 days**. This tells Slate to pause the automation for 3 days before continuing. ## Step 4: Add a condition (optional) Add a **Condition gate** step: check that the item's status is still **"Open"**. This way, if the item was already moved to "Won" or "Lost", the follow up is not sent. ## Step 5: Add the email action Click **"Add Step"** and choose **Action → Send email**. Select an email template (or create one). Templates support variables like `{contact_name}` and `{item_name}` that fill in automatically. ## Step 6: Save and enable Save the automation and toggle it **on**. From now on, every new item will automatically get a follow up email after 3 days. ## More ideas - **Automatically assign** items to team members based on source - **Move to stage** when a proposal is accepted - **Send a webhook** to notify an external tool - **Remind the assignee** if an item has not moved in 2 weeks See [Automations](https://docs.slate.zerulean.com/features/automations) for the full list of triggers, steps, and actions. # Capture Leads via Web Form Deploy an embeddable form on your website that submits directly to your pipeline. ## Step 1: Create a source mapping 1. Go to **Settings → Company Settings → Source Mappings** 2. Create a mapping and select **Web Form** as the type 3. Map the form fields to your pipeline fields ## Step 2: Create a web form 1. Go to **Settings → Company Settings → Web Forms** 2. Click **"Create Web Form"** 3. Select the source mapping you created 4. Set the **target stage** for new submissions 5. Pick which pipeline fields to show on the form ## Step 3: Style it Customize the form's colors and branding to match your website. ## Step 4: Embed on your site Copy the embed code and paste it into your website's HTML: ```html ``` The form renders in an iframe on your page. ## Submission processing Submissions are validated and checked for spam. A new item is created in your pipeline in the configured target stage and appears on your Kanban board. Forms are rate limited to prevent abuse. ## Best practices - Keep forms short. 3-5 fields convert better than 10. - Use a **dropdown** for "How did you hear about us?" to track lead sources - Toggle forms on/off without deleting them # Connect via Webhook Inbound webhooks accept HTTP POST requests from external systems and map incoming payloads to your pipeline blueprint. ## Step 1: Create an integration 1. Go to **Settings → Company Settings → Integrations** 2. Click **"Create Integration"** 3. Enter a name (e.g., "Zapier", "My Website", "n8n") 4. Copy the **webhook URL**. A unique webhook URL is generated for each integration. ## Step 2: Set up a source mapping Source mappings tell Slate how to translate incoming data into your pipeline fields. 1. Go to **Settings → Company Settings → Source Mappings** 2. Create a mapping and select **Integration** as the type 3. Paste a sample JSON payload and Slate automatically detects the fields 4. Map each detected field to a pipeline field For example, if the external tool sends: ```json { "name": "Jane Smith", "email": "jane@example.com", "company": "Acme Inc" } ``` Map `name` → "Contact Name", `email` → "Email", `company` → "Company". ## Step 3: Configure the external tool In your external tool (Zapier, Make, n8n, or any custom app): 1. Set up a webhook/HTTP action 2. Paste the Slate webhook URL 3. Set method to **POST** 4. Send your data as JSON ## Step 4: Test it Send a test payload from your external tool. Check your pipeline board. A new item should appear with the mapped fields filled in. ## Best practices - Use **auto-matching**. Send a sample payload and Slate tries to match fields automatically based on field names. - If you have [duplicate detection](https://docs.slate.zerulean.com/features/duplicate-detection) enabled, incoming webhooks respect it (warn, skip, or update depending on your config) - You can create multiple integrations with different mappings for different data sources # Import from CSV Bulk import items from CSV files with progress tracking and full rollback capability. ## Step 1: Prepare your CSV Make sure your CSV file has: - A **header row** with column names - One row per item - Consistent data formatting **Example:** ```text Name,Email,Phone,Deal Value,Source Jane Smith,jane@example.com,+1234567890,15000,Website John Doe,john@example.com,+0987654321,25000,Referral ``` ## Step 2: Create a source mapping Before importing, you need a source mapping that defines how CSV columns translate to your pipeline fields. 1. Go to **Settings → Company Settings → Source Mappings** 2. Create a mapping and select **CSV Import** as the type 3. Paste your CSV headers or a sample row, and Slate automatically detects the fields 4. Map each detected field to a pipeline field (e.g., `Name` → Contact Name, `Email` → Email, `Deal Value` → Deal Value) Review and adjust the automatically detected mappings as needed. ## Step 3: Start the import 1. Go to **Settings → Company Settings → CSV Imports** 2. Select the pipeline and the source mapping you created 3. Choose how to handle duplicates (skip, update existing, or always create new) 4. Upload your CSV file (maximum 10 MB) 5. Click **"Start Import"** Large imports run as **background jobs**, so you can close the page and return later. Progress is tracked in real time. ## After the import - View import history with row counts, success/failure breakdown, and status - **Cancel** a running import at any time. Items already created are preserved. - **Rollback** a completed import. This deletes all items created by that import in one operation. - Failed rows are counted and displayed in the import history ## Best practices - Clean up your spreadsheet before importing. Remove blank rows and fix inconsistent data. - Validate with a small test file (10-20 rows) before importing full datasets - If you are importing from another CRM, export as CSV from that tool first # Add a Passkey Passkeys let you sign in using biometrics (Face ID, Touch ID) or a hardware security key, so you do not need to wait for an email passcode. ## Adding a passkey 1. Go to **Settings → Account** 2. Open the **Passkeys** section 3. Click **"Add Passkey"** 4. Follow your device's prompt to register the passkey (e.g., scan your fingerprint or face) 5. Give the passkey a name for easy identification You can register up to 5 passkeys per account. ## Managing passkeys From the **Passkeys** section in your account settings, you can: | | | | ---------- | ----------------------------------------------------------------- | | **Rename** | Edit the passkey name for easier identification | | **Delete** | Remove a passkey. You will no longer be able to use it to sign in | Each passkey shows its creation date and when it was last used. # Enable Two Factor Authentication Two factor authentication adds an extra layer of security by requiring a code from an authenticator app when you sign in. ## Setting up 1. Go to **Settings → Account** 2. Open the **Two Factor Authentication** section 3. Click **"Set Up"** 4. Scan the QR code with your authenticator app (Google Authenticator, Authy, or similar). If you cannot scan, enter the secret code manually. 5. Enter the 6 digit code from your authenticator app 6. Click **"Verify & Enable"** Two factor authentication is now active on your account. ## Disabling To disable two factor authentication: 1. Go to **Settings → Account** 2. Open the **Two Factor Authentication** section 3. Click **"Disable"** and confirm Your account will return to email passcode or passkey authentication only. # Sync Google Calendar Connect your Google Calendar to automatically sync Slate tasks as calendar events. ## Connecting 1. Go to **Settings → Account** 2. Open the **Google Calendar** section 3. Click **"Connect Google Calendar"** 4. Review the permissions Slate will request: - Create and manage a dedicated "Slate Tasks" calendar - View your Google account email address 5. Click **"Continue to Google"** and authorize access Once connected, your tasks with due dates are synced to a dedicated **Slate Tasks** calendar in Google Calendar. Only task titles, due dates, and durations are synced. No other data is accessed. ## Disconnecting 1. Go to **Settings → Account** 2. Open the **Google Calendar** section 3. Click the disconnect button and confirm Your tasks will no longer sync. Existing calendar events will remain in your Google Calendar. # Overview Slate integrates with external tools through webhooks, file imports, embeddable forms, and a REST API. ## Bringing data in | | | | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | **[Inbound Webhooks](https://docs.slate.zerulean.com/integrations/inbound-webhooks)** | Receive data from external tools like Zapier, Make, or n8n. Set up a field mapping and Slate creates items automatically | | **[CSV Import](https://docs.slate.zerulean.com/integrations/csv-import)** | Import items in bulk from a spreadsheet. Map columns to pipeline fields and track progress | | **[Web Forms](https://docs.slate.zerulean.com/integrations/web-forms)** | Embed a lead capture form on your website. Submissions create items directly in your pipeline | | **[Email Inbound](https://docs.slate.zerulean.com/integrations/email-domains)** | Receive emails that create new items or continue existing conversations | ## Sending data out | | | | --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | **[Outbound Webhooks](https://docs.slate.zerulean.com/integrations/outbound-webhooks)** | Send item data to an external URL when events occur in your pipeline | | **[REST Hooks](https://docs.slate.zerulean.com/api/webhooks)** | Subscribe to events programmatically via the API. Compatible with Zapier and similar platforms | | **[API](https://docs.slate.zerulean.com/api/authentication)** | Full access to items, tasks, and pipelines via a REST API | | **[CSV Export](https://docs.slate.zerulean.com/features/reports)** | Export report data as CSV for analysis in spreadsheets or BI tools | ## Source mappings Source mappings define how incoming data translates to your pipeline fields. There are three types, each for a different data source: | | | | --------------- | --------------------------------------------------------- | | **CSV Import** | For importing data from spreadsheet files | | **Integration** | For receiving data from external tools via webhooks | | **Web Form** | For capturing leads from embeddable forms on your website | You can create and manage source mappings in **Settings → Company Settings → Source Mappings**. When creating a mapping, paste a sample payload and Slate automatically detects the fields for you. ## How integrations work Connecting an external tool to Slate typically involves two steps: 1. **Create an integration** in **Settings → Company Settings → Integrations**. This generates a unique webhook URL for the external tool to send data to. 2. **Create a source mapping** and select the appropriate type. Define how incoming fields translate to your pipeline fields. Once configured, the external tool sends data to the webhook URL, Slate applies the mapping, and items are created in your pipeline. If [duplicate detection](https://docs.slate.zerulean.com/features/duplicate-detection) is enabled, it is applied automatically. This pattern works with any tool that can send HTTPS requests. # Inbound Webhooks Inbound webhooks receive data from external systems and map incoming fields to your pipeline blueprint automatically. ## Setup 1. Go to **Settings → Company Settings → Integrations** 2. Click **"Create Integration"** 3. Name your integration (e.g., "Zapier", "Make", "n8n") 4. 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. 1. Go to **Settings → Company Settings → Source Mappings** 2. Create a mapping and select **Integration** as the type 3. Paste a sample JSON payload and Slate automatically detects the fields 4. Map each detected field to a pipeline field For example, if the external tool sends: ```json { "name": "John Doe", "email": "john@example.com", "company": "Acme Inc" } ``` Map the fields as follows: - `name` → your "Contact Name" field - `email` → your "Email" field - `company` → 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](https://docs.slate.zerulean.com/features/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 | # Outbound Webhooks Outbound webhooks notify external systems when events happen in your pipeline, delivering item data to a URL you configure. ## Setup 1. Go to **Settings → Company Settings → Webhooks** 2. Click **"Create Webhook"** 3. Enter the **target URL** (must be HTTPS) 4. Select which **events** to subscribe to 5. Save. A **secret** is generated for verifying that requests came from Slate. ## Payload When an event occurs, Slate sends the item data to your endpoint: ```json { "event": "item.created", "item_id": "01234567-...", "name": "Acme Corp Deal", "pipeline": "Sales", "stage": "Qualified", "status": "Open", "contact_name": "John Doe", "email": "john@example.com", "deal_value": 15000, "created_at": "2026-04-01T10:30:00Z", "updated_at": "2026-04-01T10:30:00Z" } ``` Custom fields are included using their human readable names. ## Signature verification Each request includes a signature. Use the secret from your webhook settings to verify that the request came from Slate. ## Retries Failed deliveries are retried automatically with increasing delays. ## Delivery logs Each webhook tracks its delivery history. Click the **history button** on a webhook row to view: - **Stats overview** with success rate, average response time, and delivery counts for the last 7 and 30 days - **Delivery breakdown** bar showing the proportion of delivered, failed, and pending deliveries - **Recent deliveries** list with status filter. Expand a delivery to see HTTP status code, response time, attempt count, and error details ## Webhook status Each webhook row shows its current health: | | | | ------------ | ----------------------------- | | **Healthy** | Recent deliveries succeeded | | **Errors** | Some recent deliveries failed | | **Failing** | Multiple consecutive failures | | **Inactive** | Webhook is disabled | ## Testing Use the **"Test Webhook"** button to send a sample payload to your URL and confirm it is receiving data correctly. ## Secret rotation You can rotate the webhook secret at any time. After rotating, update your verification code to use the new secret. # CSV Import Bulk import pipeline items from CSV files with progress tracking and full rollback. ## How to import 1. Go to **Settings → Company Settings → CSV Imports** 2. Select the pipeline and a **CSV Import** source mapping 3. Choose how to handle duplicates (skip, update existing, or always create new) 4. Upload your CSV file 5. Click **"Start Import"** ## During import Imports run as **background jobs**, so you can close the page and return later. - Progress is tracked in real time with a completion percentage - You can **cancel** a running import at any time. Items already created are preserved. ## After import - View import history with row counts, success/failure breakdown, and status - **Rollback** a completed import. This deletes all items created by that import in one operation. ## Best practices - Ensure your CSV has a header row with column names - When creating a **CSV Import** source mapping, paste your CSV headers and Slate automatically detects the fields. Review the matches before confirming. - If your pipeline has [duplicate detection](https://docs.slate.zerulean.com/features/duplicate-detection) enabled, it applies row by row during import # Web Forms Embeddable lead capture forms that create pipeline items from public submissions. ## Creating a web form 1. Create a source mapping in **Settings → Company Settings → Source Mappings** and select **Web Form** as the type 2. Go to **Settings → Company Settings → Web Forms** 3. Click **"Create Web Form"** 4. Select the source mapping you created 5. Configure: - **Target stage** - select which stage new submissions are placed in - **Styling** - customize colors and branding to match your website 6. Save and copy the embed code ## Embedding Add the embed script to your website: ```html ``` The form renders in an iframe on your page. ## How submissions work When a visitor fills out the form: 1. Submissions are validated and checked for spam 2. A new item is created in your pipeline in the configured stage 3. The new item appears on your Kanban board ## Rate limiting Forms are rate limited to prevent abuse. Submissions that exceed the limit are temporarily rejected. ## Managing forms - **Toggle** forms on/off without deleting them. Deactivated forms return an error to visitors. - Edit fields, styling, and target stage at any time without changing the embed code # Email Domains Configure verified custom domains for branded outbound email delivery across conversations, automations, and document notifications. ## Setting up a domain 1. Go to **Settings → Company Settings → Email Domains** 2. Add your domain (e.g., `yourbusiness.com`) 3. Add the **DNS records**Slate provides: - **DKIM** records: cryptographic keys for email authentication (multiple TXT records) - **SPF** record: authorizes Slate's email infrastructure to send on your behalf 4. Click **"Verify"**. Slate checks the records against your DNS. Verification retries automatically to account for DNS propagation delays across registrars. ## Outbound senders Once your domain is verified, you can configure outbound senders: - Add email addresses (e.g., `sales@yourbusiness.com`, `support@yourbusiness.com`) - Set a **default sender** for the company - Each sender is used for different contexts (conversations, automations, proposals) ## Inbound email Inbound email allows you to receive emails that automatically create items or continue existing conversations in your pipeline. ### Setting up inbound email 1. Go to **Settings → Emails** 2. Enable **inbound email** on your domain 3. Add an inbound email address (e.g., `support@yourdomain.com`) 4. Select which **pipeline** and **stage** new items should be created in 5. Slate generates a unique **forwarding address** 6. In your email provider, set up forwarding from your email address to the Slate forwarding address ### How it works When an email is forwarded to Slate: - If it matches an existing conversation (via email threading), it is appended to that item's conversation thread - If no match is found, a new item is created in the configured pipeline and stage ## Email templates You can create reusable email templates with variable interpolation: - Use `{contact_name}`, `{item_name}`, `{stage}`, and other context variables in subject and body - Templates support **header HTML** and **footer HTML** for consistent branding across all emails - **Variable fallbacks** allow you to specify default values when a variable has no value for a given item - The HTML editor includes a **live preview** showing the rendered output ### Template presets Templates are available for common use cases: | | | | -------------- | ------------------------------------------ | | **Automation** | Follow-up emails, reminders, notifications | | **Proposal** | Proposal delivery and follow up | | **Invoice** | Invoice delivery and payment reminders | | **Ticket** | Support ticket acknowledgment and updates | Each preset includes context appropriate variables. See **Settings → Email Templates** to manage templates. # Authentication All external API endpoints require API key authentication and live under `/v1/ext/`. ## Creating an API key 1. Go to **Settings → Company Settings → API Keys** 2. Click **"Create API Key"** 3. Name your key (e.g., "Zapier Integration", "Internal Script") 4. Copy the key. It is only displayed once and cannot be retrieved later. ## Using your API key Include the key in the `x-api-key` header with every request: ```bash curl -H "x-api-key: YOUR_API_KEY" \ https://slate.zerulean.com/v1/ext/items ``` ## Scopes Each API key has scopes that control what it can access: | | | | ------------------ | -------------------------------- | | **`items:read`** | List and get items | | **`items:write`** | Create and update items | | **`tasks:read`** | List and get tasks | | **`tasks:write`** | Create and update tasks | | **`hooks:manage`** | Subscribe/unsubscribe REST hooks | New keys are created with all scopes by default. ## Rate limits - **60 requests per minute** per API key - Exceeding the limit returns `429 Too Many Requests` - The rate limit window is 60 seconds ## Errors | | | | --------- | -------------------------------------------------------------------------- | | **`401`** | Invalid or missing API key | | **`402`** | Company subscription inactive. API access requires an active subscription. | | **`403`** | Key lacks required scope | | **`429`** | Rate limit exceeded | ## Key management - **Rename** keys to keep track of what they are used for - **Revoke** keys immediately when no longer needed - Keys can have optional **expiration dates** # Items Create, retrieve, and update pipeline items. Requires `items:read` and/or `items:write` scopes. ## List items ```text GET /v1/ext/items ``` Returns a list of items in your company. Custom fields are included using their field names as keys. ### Response ```json [ { "item_id": "01926a3b-...", "short_id": "DEAL-42", "name": "Acme Corp Deal", "pipeline": "Sales", "stage": "Qualified", "status": "Open", "contact_id": "01926a3b-...", "source": "website", "email": "john@acme.com", "deal_value": 15000, "created_at": "2026-04-01T10:30:00Z", "updated_at": "2026-04-01T14:22:00Z" } ] ``` Custom fields from your pipeline blueprint are included using their field names. The `short_id` field is an automatically generated identifier. ### Query parameters ```json { "pipeline_id": "string, filter by pipeline", "stage_id": "string, filter by stage", "status_id": "string, filter by status", "created_after": "string (ISO 8601), filter by creation date" } ``` Use the [Pipelines API](https://docs.slate.zerulean.com/api/pipelines) to look up pipeline, stage, and status IDs. ## Get item ```text GET /v1/ext/items/{item_id} ``` Returns a single item by ID. ## Create item ```text POST /v1/ext/items ``` ### Fields ```json { "name": "string, required", "pipeline_id": "string, required", "stage_id": "string, required", "status_id": "string", "metadata": "object, custom field values keyed by field name" } ``` ### Example ```json { "name": "New Deal", "pipeline_id": "01926a3b-...", "stage_id": "01926a3b-...", "metadata": { "email": "jane@example.com", "deal_value": 25000 } } ``` ## Update item ```text PATCH /v1/ext/items/{item_id} ``` ### Fields ```json { "stage_id": "string", "status_id": "string", "version": "number, for optimistic locking", "metadata": "object, custom field values to update" } ``` Only include the fields you want to update. ### Example ```json { "stage_id": "01926a3b-...", "status_id": "01926a3b-...", "metadata": { "deal_value": 30000 } } ``` ## Optimistic locking Items include a `version` field that increments with each update. When updating an item, you can include the expected version in your request to prevent overwriting concurrent changes. If the version does not match, the update is rejected with a conflict error. ## Duplicate check Before creating an item, you can check for potential duplicates: ```text POST /v1/ext/items/check-duplicates ``` This uses the pipeline's duplicate detection configuration to find matches without creating the item. ## Looking up IDs To create or update items, you need pipeline, stage, and status IDs. Use the [Pipelines API](https://docs.slate.zerulean.com/api/pipelines) to look these up. # Tasks Create, retrieve, and update tasks. Requires `tasks:read` and/or `tasks:write` scopes. ## List tasks ```text GET /v1/ext/tasks ``` ### Response ```json [ { "task_id": "01926a3b-...", "title": "Follow up with Acme", "description": "Send the updated proposal", "due_at": "2026-04-05T09:00:00Z", "priority": "high", "is_completed": false, "task_type": "follow_up", "assigned_to": "01926a3b-...", "created_by": "01926a3b-...", "item_id": "01926a3b-...", "completed_at": null, "notes": null, "created_at": "2026-04-01T10:30:00Z", "updated_at": "2026-04-01T10:30:00Z" } ] ``` ## Create task ```text POST /v1/ext/tasks ``` ### Example ```json { "title": "Call back John", "description": "Discuss pricing", "due_at": "2026-04-05T14:00:00Z", "priority": "medium", "task_type": "call", "item_id": "01926a3b-..." } ``` ## Update task ```text PATCH /v1/ext/tasks/{task_id} ``` Only include the fields you want to update. ### Example ```json { "is_completed": true, "notes": "Discussed pricing, sending proposal tomorrow" } ``` ## Task fields reference ```json { "title": "string, required", "due_at": "string (ISO 8601), required", "assigned_to": "string, required", "description": "string", "priority": "none | low | medium | high | urgent", "task_type": "to_do | call | email | meeting | follow_up", "item_id": "string", "duration_minutes": "number", "reminder_minutes": "number", "notes": "string", "is_completed": "boolean" } ``` # Pipelines These read-only endpoints resolve pipeline, stage, and status identifiers needed for item creation and update operations. ## List pipelines ```text GET /v1/ext/pipelines ``` Returns all pipelines in your company. ### Response ```json [ { "id": "01926a3b-...", "name": "Sales", "created_at": "2026-01-15T08:00:00Z" }, { "id": "01926a3c-...", "name": "Support", "created_at": "2026-02-01T10:00:00Z" } ] ``` ## List stages ```text GET /v1/ext/pipelines/{pipeline_id}/stages ``` Returns all stages for a pipeline. Stages are returned in order. ### Response ```json [ { "id": "01926a3b-...", "name": "Lead" }, { "id": "01926a3b-...", "name": "Qualified" }, { "id": "01926a3b-...", "name": "Proposal" } ] ``` ## List statuses ```text GET /v1/ext/pipelines/{pipeline_id}/stages/{stage_id}/statuses ``` Returns all statuses available for a stage. ### Response ```json [ { "id": "01926a3b-...", "name": "Open" }, { "id": "01926a3b-...", "name": "Won" }, { "id": "01926a3b-...", "name": "Lost" } ] ``` ## Common workflow To create an item via API: 1. `GET /v1/ext/pipelines` to find your pipeline ID 2. `GET /v1/ext/pipelines/{id}/stages` to find the target stage ID 3. `POST /v1/ext/items` with the pipeline and stage IDs # REST Hooks Programmatic event subscription endpoints following the REST Hooks pattern, compatible with Zapier, Make, and similar integration platforms. Requires `hooks:manage` scope. ## Subscribe ```text POST /v1/ext/webhooks ``` ### Fields ```json { "target_url": "string, required", "event": "string, required" } ``` ### Example ```json { "target_url": "https://your-app.com/webhook", "event": "item.created" } ``` ### Response ```json { "id": "01926a3b-...", "target_url": "https://your-app.com/webhook", "event": "item.created", "created_at": "2026-04-01T10:30:00Z" } ``` ## Unsubscribe ```text DELETE /v1/ext/webhooks/{webhook_id} ``` Removes the subscription. No further events are sent to the target URL. ## Sample data ```text GET /v1/ext/webhooks/sample/items ``` Returns a sample item payload with realistic field values. Integration platforms such as Zapier and Make use this to display the data structure to users during setup. The sample uses your actual pipeline blueprint, so field names and types match real payloads. ## Difference from outbound webhooks | | | | ------------ | ---------------------------------------------------------------------------------------------------------------- | | **Setup** | You configure outbound webhooks in the UI via Settings. REST hooks are managed via the API (`/v1/ext/webhooks`). | | **Auth** | Outbound webhooks use your login session. REST hooks use an API key. | | **Use case** | Outbound webhooks are for manual configuration. REST hooks are for programmatic integrations (Zapier, Make). | | **Payload** | Both send the same item format | Both deliver the same item data. The difference is how the subscription is managed. # FAQ Common questions about your account, company settings, billing, and data management. ## Account ::prose-accordion :::prose-accordion-item{label="Can I update my profile?"} Yes. Go to **Settings → Account** to update your name, profile picture, and email address. If your company uses domain enforcement (restricting members to a specific email domain), changing to an email outside that domain will remove you from the company. ::: :::prose-accordion-item{label="Can I change my account region?"} No. Your account region is set during signup and cannot be changed. ::: :::prose-accordion-item{label="Can I delete my account?"} Yes. Go to **Settings → Account** and request deletion. Your account is deactivated immediately. After a **30-day grace period**, all personal data is permanently anonymized. If you need to reactivate your account during the grace period, email . You cannot delete your account if you are the sole owner of a company. Delete the company first or email for assistance. ::: :::prose-accordion-item{label="Can I have multiple organizations?"} Yes. A single account can create and belong to multiple organizations, each with their own companies and workspaces. ::: :::prose-accordion-item{label="Can I use Slate in a different language?"} Slate currently supports English. Additional languages are planned. If you would like to request a specific language, email . ::: :: ## Company & Organization ::prose-accordion :::prose-accordion-item{label="Can I change my company's region?"} No. The region you select during company creation is permanent and cannot be changed. Your data is stored in the selected region to comply with data residency requirements. If you need a different region, create a new company in the desired region and migrate your data using CSV export and import. ::: :::prose-accordion-item --- label: Can I have multiple companies in one organization? --- Yes. An organization can contain multiple companies, each with its own pipelines, contacts, teams, and settings. This is useful for managing separate departments, clients, or brands. ::: :::prose-accordion-item --- label: Can I restrict members to a specific email domain? --- Yes. You can enable domain enforcement on a company to restrict membership to users with a specific email domain (e.g., only `@yourbusiness.com`). If an existing member changes their email to a domain that does not match, they are automatically removed from the company. ::: :::prose-accordion-item{label="Can I rename my company or organization?"} Yes. Organization and company names can be changed at any time by an admin from the settings page. ::: :::prose-accordion-item{label="Can I transfer ownership of an organization?"} Ownership transfer is not currently available. ::: :::prose-accordion-item{label="What happens when I delete a company?"} All data associated with the company is permanently deleted, including pipelines, items, contacts, tasks, automations, integrations, and team members. Compliance records (invoices, proposals, and signed documents) are retained for up to 10 years for legal obligations. For full details, see our [Privacy Policy](https://slate.zerulean.com/privacy-policy#data-retention){rel=""nofollow""}. ::: :: ## Billing & Plans ::prose-accordion :::prose-accordion-item{label="Is there a free plan?"} There is no free plan. All new companies start with a **14-day free trial**. If you have a referral code, you can apply it to extend your trial to **60 days**. ::: :::prose-accordion-item{label="How does billing work?"} Billing is **per company**. You select a plan, number of users, and any addons (such as extra storage). Billing is available monthly or annually. ::: :::prose-accordion-item{label="What happens when my trial expires?"} After the 14-day trial, access to your pipeline data is suspended until you select a plan. You can still log in and access billing settings to subscribe. Companies that remain unsubscribed for 30 days after the trial expires are permanently deleted. ::: :::prose-accordion-item{label="Can I upgrade or downgrade my plan?"} Yes. You can switch between plans at any time from **Settings → Company Settings → Billing**. Upgrades are prorated immediately. Downgrades take effect at the end of the current billing period. ::: :::prose-accordion-item{label="How do I change my user limit?"} You can increase or decrease the number of users from **Settings → Company Settings → Billing**. Increasing the user count is prorated immediately. Decreasing takes effect at the end of the current billing period. ::: :::prose-accordion-item{label="What payment methods do you accept?"} Slate supports local and international payment methods. You can select your currency on the checkout page to see the available payment options for your region. ::: :::prose-accordion-item{label="Who is Dodo Payments?"} [Dodo Payments](https://dodopayments.com/){rel=""nofollow""} is our Merchant of Record (MoR). They handle payment processing, tax compliance, and invoicing on our behalf. Charges on your bank statement will appear from Dodo Payments. If you have questions about a charge, visit [Dodo Payments Support](https://dodopayments.com/support/why-has-dodo-payments-charged-me){rel=""nofollow""}. ::: :::prose-accordion-item{label="Can I get a refund?"} Monthly plans are non-refundable. Annual plans are eligible for a refund within 14 days of purchase. To request a refund, email . ::: :: ## Data & Privacy ::prose-accordion :::prose-accordion-item{label="Where is my data stored?"} Your account data is stored in the region you select when creating your account. Your company data (pipelines, items, contacts, documents) is stored in the region selected during company creation. Both regions are permanent and cannot be changed after creation. ::: :::prose-accordion-item{label="Is my data encrypted?"} Yes. All data is encrypted in transit using TLS. Data at rest is protected by infrastructure level disk encryption. Sensitive fields such as API keys, webhook secrets, and uploaded files are additionally encrypted at the application level using AES-256. ::: :::prose-accordion-item{label="Can I import data from another CRM?"} There is no direct import from other CRM platforms. You can export your data from the other CRM as a CSV file and import it into Slate using the [CSV Import](https://docs.slate.zerulean.com/integrations/csv-import) feature. You can also use the [API](https://docs.slate.zerulean.com/api/authentication) to programmatically create items and tasks. ::: :::prose-accordion-item{label="Can I export my data?"} Yes. Slate supports full data export for both companies and individual accounts. | | | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | | **Company export** | Admins can export all company data from **Settings → Export**. The export is prepared in the background and available for download for 7 days | | **Account export** | Any user can export their personal data from **Settings → Account** | ::: :::prose-accordion-item{label="Can I restore deleted items?"} Yes, within the retention window. Deleted items are kept for 7 days and can be restored from **Settings → Company Settings → Deleted Items**. After 7 days, items are permanently removed and cannot be recovered. ::: :::prose-accordion-item{label="How long is data retained?"} | | | | -------------------- | -------------------------------------------------------------- | | **Items** | Deleted items are recoverable for 7 days | | **Invoices** | Retained for 10 years for tax and legal compliance | | **Proposals** | Retained for 7 years, including associated e-signature records | | **Account deletion** | 30-day grace period before permanent anonymization | ::: :: ## Platform Limits ::prose-accordion :::prose-accordion-item{label="Are there limits on users, pipelines, or items?"} Limits on users, pipelines, automations, and other features depend on your plan. See the [pricing page](https://slate.zerulean.com/pricing){rel=""nofollow""} for full details. There is no limit on the number of items per pipeline. ::: :::prose-accordion-item{label="Can I move items between pipelines?"} Items belong to a specific pipeline and cannot be moved between pipelines directly. To move data, export items from one pipeline as CSV and import them into another. ::: :: ## Features ::prose-accordion :::prose-accordion-item{label="Can I use my own email domain?"} Yes. You can verify your own domain for outbound email and set up inbound email forwarding for conversations. See [Email Domains](https://docs.slate.zerulean.com/integrations/email-domains) for setup instructions. ::: :::prose-accordion-item{label="Can I connect Slate to Zapier or Make?"} Yes. Slate supports inbound webhooks (to receive data from external tools) and REST hooks (for programmatic event subscriptions compatible with Zapier and Make). See [Integrations](https://docs.slate.zerulean.com/integrations) for details. ::: :::prose-accordion-item{label="Does Slate support e-signatures?"} Yes. Slate supports SES (Simple Electronic Signature) built in, and AES/QES (Advanced/Qualified Electronic Signature) via DocuSign with bring-your-own credentials. See [Proposals](https://docs.slate.zerulean.com/features/proposals#e-signatures) for details. ::: :: ## Security & Authentication ::prose-accordion :::prose-accordion-item{label="What authentication methods are supported?"} Slate uses **passwordless authentication** exclusively. There are no passwords. Two methods are available: | | | | ------------------ | --------------------------------------------------------------------------- | | **Email passcode** | A one time code sent to your email address | | **Passkey** | Biometric or hardware key authentication (Face ID, Touch ID, security keys) | ::: :::prose-accordion-item{label="What browsers are supported?"} Slate works on all modern browsers including Chrome, Firefox, Safari, and Edge. Passkey authentication requires a device and browser that support WebAuthn. ::: :::prose-accordion-item{label="Is there a mobile app?"} There is no dedicated mobile app. Slate is accessible through your mobile browser and is designed to work on smaller screens. ::: :: # Get Help Reach out to us with your questions, we are happy to help. ::u-page-grid :::u-page-card --- icon: i-simple-icons-discord target: _blank to: https://slate.zerulean.com/discord --- #title Join our community #description Join us on Discord to hang out with other users and meet our team. ::: :::u-page-card --- icon: i-lucide-mail to: mailto:support@zerulean.com --- #title Email support #description Send us an email at and we will get back to you. ::: :: # For AI Give any AI tool full context about the Slate platform by sharing this link: **[llms-full.txt](https://docs.slate.zerulean.com/llms-full.txt)** Paste it into ChatGPT, Claude, Perplexity, or any AI assistant to ask questions about features, configuration, API, and integrations. A structured index is also available at **[llms.txt](https://docs.slate.zerulean.com/llms.txt)**.