# Automations Fluid includes eight automations per pipeline. No add-on pricing, no upgrade required, no per-automation limits. ### How automations work in Fluid CRM Automations run per pipeline. Each pipeline can have its own configuration, so your sales pipeline and your onboarding pipeline can behave completely differently. You access them from Settings, then Automations, then select the pipeline you want to configure. Each automation: * Toggles on or off independently * Applies only to the selected pipeline * Can be changed anytime without affecting existing deals * Takes effect immediately There are no workflow builders, drag-and-drop logic trees or "if this then that" chains. Each automation does one specific job well. ### The eight automations Fluid groups automations into three categories based on when they fire: on deal creation, on stage change, and time-based. **On deal creation** Run automatically when a new deal is added to the pipeline, whether you create it manually, import it via CSV or it lands through the API or a Lead form. **Auto-set deal value** Sets a default value on every new deal in this pipeline. Useful when most of your deals in a pipeline have similar values. For example, if your average client retainer is €5,000, set this automation to €5,000 and every new deal starts with that value. You can change it on individual deals later if needed. **Due date auto-set** Sets an expected close date based on your average sales cycle. If your typical sales cycle is 30 days, every new deal gets an expected close date 30 days out. This populates your forecast immediately and saves you from setting close dates manually. **Auto-reminder** Adds a follow-up reminder automatically when a deal is created. Pick the delay (1 day, 3 days, 1 week, etc.) and Fluid sets the first reminder for you. Every deal lands in the pipeline with a next action already scheduled. No deals slip through the cracks from day one. **Auto-assign deals** Routes new deals to a specific team member. Useful for pipelines where a specific person owns intake. Your SDR pipeline auto-assigns to the SDR. Your partner pipeline auto-assigns to the partnerships lead. Your client onboarding pipeline auto-assigns to the account manager. **On stage change** Run automatically when a deal moves between stages on the pipeline. **Stage notification** Notifies a specific team member when a deal reaches a particular stage. For example, notify the sales manager when a deal hits Negotiation. Notify the account manager when a deal moves to Onboarding. Notify yourself when a partner deal closes. This replaces manual "FYI" messages between teammates. **Auto-create activity** Logs a "Stage changed" activity on the deal whenever it moves between stages. Useful for audit trails, deal reviews and understanding how long deals sit in each stage. Activity entries are timestamped and visible in the deal's activity history. **Cross-pipeline move** Automatically moves a deal to another pipeline when it reaches a specific stage. The most common use case: when a deal hits "Won" in your sales pipeline, it moves to "Kickoff" in your onboarding pipeline. The deal carries over its contact, company, value and activity history. The handoff happens without copy-paste, manual recreation or dropped context. Other use cases: * Move "Lost" deals to a nurture pipeline for future re-engagement * Move closed client work to a renewal pipeline 6 months out * Move qualified leads from an inbound pipeline to a sales pipeline **Time-based** Run automatically based on how long deals sit without movement. **Idle follow-up** Auto-moves deals that have been sitting in a stage too long. Pick the threshold (7 days, 14 days, 30 days, etc.) and Fluid moves idle deals to a stage of your choice. Common setups: * Move deals idle in "Proposal" for 14 days to "Negotiation" so you remember to push * Move deals idle in "Discovery" for 30 days to "Lost" so your pipeline stays honest * Move deals idle in "Negotiation" for 21 days back to "Proposal" if no progress This keeps your pipeline honest without manual cleanup work. ### Configuring automations per pipeline Automations are pipeline-specific by design. Different work needs different automations. **Sales pipeline example** * Auto-set deal value: €5,000 (your average deal) * Due date auto-set: 30 days * Auto-reminder: 2 days after creation * Auto-assign: to the assigned sales rep * Stage notification: notify owner on "Negotiation" * Cross-pipeline move: when "Won", move to onboarding pipeline * Idle follow-up: 14 days in any stage triggers a check **Onboarding pipeline example** * Auto-create activity: yes, on every stage change * Stage notification: notify the account manager on "Kickoff" * Auto-reminder: 1 day after creation (welcome call) * Auto-assign: to the assigned account manager **Partner pipeline example** * Auto-set deal value: zero (track relationships, not revenue) * Auto-reminder: 7 days after creation * Auto-assign: to the partnerships lead Each pipeline can have a completely different setup. You configure once, the automations run forever. ### When to use automations Automations work best for repetitive actions that you would otherwise do manually for every deal. Use automations when: * You always set the same default value on new deals * You always add a follow-up reminder for the same delay * You always assign deals in a specific pipeline to the same person * You want consistent handoffs between pipelines * You want to surface stale deals before they go cold Skip automations when: * The action varies deal-by-deal (just do it manually) * The pipeline has very low volume (manual is fine) * You are still figuring out your process (set up automations once your workflow is stable) ### Why automations matter Manual data entry kills small B2B teams. You forget to set reminders. You miss follow-ups. Deals go cold. The CRM becomes a chore. Automations remove the busy work without removing your control. You decide what fires. You decide which pipeline. You decide when. Fluid handles the execution. The goal is a pipeline that maintains itself in the background so you can focus on the actual selling work. #### What to read next * API & Webhooks, fire external automations from deal events * Lead forms, automate inbound capture into your pipeline --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fluid-crm.gitbook.io/fluid-crm-docs/features/automations.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.