January 22, 2026

Typeform to PandaDoc, proposals ready to send

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

You finish a sales call, feel good about it, then lose momentum because you’re stuck rebuilding a proposal from scratch. Copying notes, rewriting sections, hunting for the right template, double-checking pricing. It’s slow, and it’s easy to miss something important.

This Typeform PandaDoc proposals automation hits consultants and agency owners first, honestly. But sales reps who need clean follow-ups also feel the drag. You get a ready-to-review PandaDoc draft, your ClickUp “CRM” updated, and a Gmail follow-up draft waiting to send.

Below is what the workflow does, what it replaces, and how to get it running without turning your week into an automation project.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: Typeform to PandaDoc, proposals ready to send

Click to explore

flowchart LR

    subgraph sg0["Client Intake Flow"]
        direction LR
        n0@{ icon: "mdi:robot", form: "rounded", label: "Draft Proposal Text", pos: "b", h: 48 }
        n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Generate PandaDoc File"]
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/clickup.svg' width='40' height='40' /></div><br/>Update CRM Task"]
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/clickup.svg' width='40' height='40' /></div><br/>Set Company Field"]
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/clickup.svg' width='40' height='40' /></div><br/>Set Quote Field"]
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/clickup.svg' width='40' height='40' /></div><br/>Store Proposal Link"]
        n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/typeform.dark.svg' width='40' height='40' /></div><br/>Client Intake Trigger"]
        n7@{ icon: "mdi:message-outline", form: "rounded", label: "Gmail Draft Message", pos: "b", h: 48 }
        n2 --> n3
        n2 --> n4
        n2 --> n5
        n5 --> n7
        n6 --> n0
        n0 --> n1
        n1 --> n2
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n6 trigger
    class n0 ai
    class n1 api
    classDef customIcon fill:none,stroke:none
    class n1,n2,n3,n4,n5,n6 customIcon

The Challenge: Proposals Steal Your Follow-Through

Most proposals don’t fail because your offer is bad. They fail because the process is messy. After the call, you’re juggling raw notes, a half-updated CRM record, and the nagging feeling you should send a follow-up “soon” (which becomes tomorrow, then next week). Formatting and rewriting turns into a mini writing project, and every time you do it manually you introduce tiny inconsistencies: pricing phrased differently, scope less clear, the wrong client name in one spot. It’s exhausting, and it quietly costs deals.

It adds up fast. Here’s where it usually breaks down.

You rewrite the same sections repeatedly because your call notes aren’t structured for proposal copy.
PandaDoc drafts take longer than they should because you’re manually mapping details into the template.
ClickUp (or whatever you use as a lightweight CRM) stays outdated, so your pipeline view lies to you.
Follow-up emails go out late because you still need to “pull the link and write the message.”

The Fix: Turn Call Notes Into a PandaDoc Draft + Follow-Up

This workflow starts right after the call, when the details are fresh. You fill out a short Typeform with the essentials (client name, pain points, what you pitched, the price). n8n takes that structured input and sends it to an AI step that turns messy notes into clean proposal-ready copy. Next, the workflow creates a PandaDoc draft through an HTTP request, using a JSON body where your dynamic fields get mapped into your PandaDoc template. Once PandaDoc returns the proposal link, the workflow updates your ClickUp lead record with the company name, quote, and the proposal URL. Then it creates a Gmail draft that includes a thank-you note and that proposal link, so you can review and send without starting from zero.

The workflow begins with a Typeform submission. AI turns that submission into polished sections you can reuse across proposals. PandaDoc receives the filled template, ClickUp gets updated, and Gmail produces the follow-up draft so you can hit send when you’re ready.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Rewriting proposal sections from scratch after each call.
Manually copying names, pains, scope, and pricing into PandaDoc fields.
Forgetting to update ClickUp with the latest status and proposal link.
Starting every follow-up email as a blank page.

What used to take about 60 minutes becomes a 3-minute form plus review.
Proposals read more consistently because the same structure is used every time.
Your ClickUp pipeline stays trustworthy, which makes forecasting less guessy.
Follow-ups go out the same day more often, not “when you get around to it.”
You spend your energy on deal quality and negotiation, not formatting.

Real-World Impact

Say you send 10 proposals a month. Manually, it’s common to spend about 45 minutes writing and assembling each one, plus another 10 minutes updating ClickUp and drafting a follow-up email, so you’re burning roughly 9 hours a month. With this workflow, the “assembly” time becomes a 3-minute Typeform submission, then a few minutes to review the PandaDoc draft and Gmail draft. Even if you still spend 10 minutes polishing, you’re getting most of that time back.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Typeform to capture post-call details.
PandaDoc to generate proposal drafts from a template.
ClickUp to store the lead record and custom fields.
Gmail to create the follow-up email draft.
OpenAI API key (or LLM key) (get it from your LLM provider dashboard).

Skill level: Intermediate. You’ll connect accounts, paste an API key, and edit a JSON request to match your PandaDoc template fields.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

Typeform submission triggers the run. After the call, you fill out the intake form with the client’s company name, needs, what you proposed, and the quote.

AI turns your notes into proposal copy. n8n sends the form data to the OpenAI step, which returns structured text you can drop into a proposal without heavy rewriting.

PandaDoc gets a draft created via HTTP request. The workflow maps the generated copy and your form fields into a JSON body that matches your PandaDoc template, then creates a new document draft and captures the resulting proposal URL.

ClickUp and Gmail get updated automatically. ClickUp receives the company name, quote, and proposal link in the right custom fields, then Gmail creates a draft follow-up email that includes the link so you can review and send.

You can easily modify the PandaDoc template fields to match your own proposal layout based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Typeform Trigger

Set up the workflow entry point so new client intake submissions kick off proposal generation.

Add the Client Intake Trigger node and set Form ID to RADFsrT7.
Keep Only Answers set to false and Simplify Answers set to false.
Credential Required: Connect your typeformApi credentials.

Tip: Ensure your Typeform includes hidden field clickup_id and the answer indexes used in expressions (e.g., answers[0] for first name, answers[2] for email).

Step 2: Set Up AI Proposal Drafting

Configure the AI to generate structured proposal content used downstream.

Add the Draft Proposal Text node and select Model GPT-4O.
Keep JSON Output enabled (true) to return a single JSON object.
Verify the prompt includes the expression inputs, such as {{ $json.form_response.answers[5].text }} and {{ $json.form_response.answers[4].text }}, to bind Typeform content into the prompt.
Credential Required: Connect your openAiApi credentials.

⚠️ Common Pitfall: If the AI response is not valid JSON, the downstream PandaDoc request will fail—ensure the prompt preserves the JSON format exactly.

Step 3: Configure PandaDoc Generation

Send the AI-generated fields and client details to PandaDoc to create a proposal document.

Add the Generate PandaDoc File node and set URL to https://api.pandadoc.com/public/v1/documents with Method POST.
Set Specify Body to json and JSON Body to the provided object starting with ={ "owner": { "email": "[YOUR_EMAIL]" }, "template_uuid": "<template id>", "name": "Proposal for {{ $('Client Intake Trigger').item.json.form_response.answers[3].text }}" }.
In Header Parameters, set Authorization to API-Key [CONFIGURE_YOUR_API_KEY] and accept to application/json.
Confirm token mappings use expressions like {{ $json.message.content.problemText.replace(/\n/g, '\\n') }} and client details from Client Intake Trigger.

⚠️ Common Pitfall: The PandaDoc API key is not stored as n8n credentials here—ensure the header value is updated to your live key.

Step 4: Configure CRM Updates and Parallel Fields

Update ClickUp with proposal data and populate custom fields in parallel once the PandaDoc document is created.

Add Update CRM Task and set ID to {{ $('Client Intake Trigger').item.json.form_response.hidden.clickup_id }} with Operation update.
Set Update Fields → Content to the multiline expression starting with Company Summary: {{ $('Client Intake Trigger').item.json.form_response.answers[4].text }}.
Credential Required: Connect your clickUpOAuth2Api credentials to Update CRM Task, Set Company Field, Set Quote Field, and Store Proposal Link.
Configure Set Company Field with Task {{ $json.id }}, Field {{ $json.custom_fields[0].id }}, and Value {{ $('Client Intake Trigger').item.json.form_response.answers[3].text }}.
Configure Set Quote Field with Task {{ $('Update CRM Task').item.json.id }}, Field {{ $('Update CRM Task').item.json.custom_fields[9].id }}, and Value {{ $('Client Intake Trigger').item.json.form_response.answers[9].number }}.
Configure Store Proposal Link with Value =https://app.pandadoc.com/a/#/documents/{{ $('Generate PandaDoc File').item.json.id }}.

Update CRM Task outputs to both Set Company Field and Set Quote Field and Store Proposal Link in parallel.

Step 5: Draft the Client Email

Create an email draft that references the client’s name and is sent after the proposal link is stored.

Add Gmail Draft Message and set Resource to draft and Email Type to html.
Set Subject to sent you the Proposal.
Set Message to the HTML content starting with =Hey {{ $('Client Intake Trigger').item.json.form_response.answers[0].text }}, thanks for the great call..
Set Options → Send To to {{ $('Client Intake Trigger').item.json.form_response.answers[2].email }}.
Credential Required: Connect your gmailOAuth2 credentials.

Tip: Replace (proposal link) in the message template with the PandaDoc link if you want the draft to include it automatically.

Step 6: Test and Activate Your Workflow

Run a full test to ensure the proposal is generated, ClickUp fields update, and the email draft is created.

Click Execute Workflow and submit a new Typeform entry using real sample data.
Confirm Draft Proposal Text returns valid JSON and Generate PandaDoc File returns a document ID.
Verify ClickUp updates: task content, company field, quote field, and proposal link.
Check Gmail for a new draft created by Gmail Draft Message.
When everything works, toggle the workflow to Active to enable production runs.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

PandaDoc API credentials can expire or lack document permissions. If creation fails, check your PandaDoc API app access and the error response from the HTTP Request node first.
ClickUp custom fields must match your workspace setup. If the Company, Quote, or Proposal URL fields don’t update, confirm the field IDs and that your ClickUp token can edit the specific list/task.
Gmail drafts can land in the wrong thread or fail silently when scopes are missing. If you don’t see a draft, re-check Gmail OAuth permissions inside n8n and confirm the “From” account is the one you intended.

Common Questions

How quickly can I implement this Typeform PandaDoc proposals automation?

About an hour if your PandaDoc template and ClickUp fields are already set.

Can non-technical teams implement this proposal drafting automation?

Yes, but someone needs to handle the first-time PandaDoc field mapping. After that, day-to-day use is just filling out the Typeform.

Is n8n free to use for this Typeform PandaDoc proposals workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs (often a few cents per proposal, depending on length).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

How do I adapt this Typeform PandaDoc proposals solution to my specific challenges?

Start with the HTTP Request step that creates the PandaDoc document and adjust the JSON body to match your template fields. Common customizations include swapping Typeform for Tally, changing the AI tone in the proposal-writing prompt, and updating different CRM fields in ClickUp (or replacing ClickUp entirely). If you want faster internal turnaround, add a Telegram alert when the PandaDoc link is created so you know it’s ready to review.

Why is my PandaDoc connection failing in this workflow?

Usually it’s an expired or incorrect API token, or the HTTP request is pointing at the wrong PandaDoc endpoint for your account region. Also check the template/document IDs in your request body and look at the raw error message returned by the HTTP Request node, because PandaDoc is pretty specific about what field failed.

What’s the capacity of this Typeform PandaDoc proposals solution?

For most small teams, it comfortably handles dozens of proposals a week.

Is this Typeform PandaDoc proposals automation better than using Zapier or Make?

Often, yes. This workflow depends on a custom HTTP request payload to PandaDoc plus multiple field updates in ClickUp, and n8n handles that kind of “do a few precise things in a row” logic without getting awkward. If you later want branching (different proposal templates by service, or different follow-up emails by deal size), it’s much easier to expand here. Zapier or Make can still work for simpler versions, but you may hit limits when you need deeper API control. If you want a second opinion, Talk to an automation expert and we’ll sanity-check the best path.

When the proposal is drafted, the CRM is updated, and the follow-up is sitting in Gmail, you stay in motion. Set it up once, then focus on closing instead of formatting.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"name": "Automated Proposal Generation Flow",
"meta": {
"instanceId": "e61aa5af46807728de9229ac0cf888caeaeb40c808288172a49ed0465d78a8de",
"templateId": null,
"templateCredsSetupCompleted": null
},
"nodes": [
{
"id": "flowpast-topbar-6534",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
20,
-40
],
"parameters": {
"color": 7,
"width": 1275,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "7d32401a-90d3-462d-ab44-435e92371afb",
"name": "Draft Proposal Text",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
900,
140
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-4o",
"cachedResultName": "GPT-4O"
},
"options": [],
"messages": {
"values": [
{
"role": "system",
"content": "You are a helpful, intelligent writing assistant."
},
{
"content": "=Your task is to generate a proposal using input data from a form. This proposal should be highly customized, specific, and high-quality, considering we're going to be sending it immediately after you're done.\n\nContext: we are an automation/no-code agency that develops systems revolving around growth, revenue ops, etc.\n\nThe proposal template we're using has many fields. You must return these fields in one JSON object.\n\nUse this format:\n\n{\n  \"proposalTitle\": \"\",\n  \"problemTitle\": \"\",\n  \"problemText\": \"\",\n  \"solutionTitle\": \"\",\n  \"solutionText\": \"\",\n  \"scope1\": \"\",\n  \"scope2\": \"\",\n  \"scope3\": \"\",\n  \"scope4\": \"\",\n\"deliverable1\":\"\",\n\"deliverable2\":\"\",\n\"deliverable3\":\"\",\n  \"timeline1\": \"\",\n  \"timeline2\": \"\",\n  \"timeline3\": \"\"\n}\n\nRules:\n1. Use a spartan, casual tone of voice.\n2. Be to-the-point but professional\u2014assume you're writing to a sophisticated audience.\n3. Ensure that all fields are filled out. Do not miss a field or leave any variables empty.\n4. For problemText and solutionText, make sure to number the responses (usually 3, make sure they're inside of the string).\n5. There will only ever be 4 scoping bullet points, 3 timeline and 3 deliverable bullet points\u2014stick to this precisely. For the timelines, only say the amount of days (\"x days\")"
},
{
"content": "={\"problem\":\"Right now they're managing all of their leads & projects in a massive Google Sheet. The key issues: their system is disorganized, incapable of scaling, and provides little in the way of accountability. Team members are manually updating fields, copying and pasting data, and there is no single source of truth.\",\n\"solution\":\"Migration to a dedicated CRM & project management solution like Monday.com, and a bespoke setup that includes a CRM board to handle new leads, alongside a PM board to handle new and ongoing projects. The creation of new records, and various administrative tasks alongside them, will be handled using both built in Monday automations and third party tools. I'll also create a process library of SOPs to improve operations more generally.\",\n\"deliverables\":\"completed Monday CRM, PM boards, process library of SOPs, training materials, video\",\n\"timeline\":\"two weeks\",\n\"companyDescription\":\"Robert Half is an executive recruiting firm that works primarily out of NYC.\"}"
},
{
"role": "assistant",
"content": "={\n  \"proposalTitle\": \"Scalable Project Management system for Robert Half\",\n  \"problem\": {\n    \"title\": \"Your systems don't scale & you're paying too much\",\n    \"text\": \"1. You're using systems that don't scale\\n\\nCurrently, your team spends a ridiculous amount of time manually updating fields in a Google Sheet. This is resource-intensive, inefficient, and tedious\u2014it's easy for a small mistake to cascade into a large one, and this has happened multiple times. Perhaps more importantly, there's no accountability, so when said problems inevitably arise, it's impossible to trace it back to its root and solve it.\\n\\n2. You're doing (and paying) too much\\n\\nGoogle Sheets is free. But the impact on your business has been costly. Given the archaic nature of your current setup, specific daily tasks are difficult to operationalize\u2014leading to a large chunk of your employee/contractor costs going to admin tasks that are easily automatable.\\n\\n3. You're missing a ton of functionality\\n\\nGoogle Sheets is primarily textual, and misses the rich functionality afforded by more intentional CRMs. For instance, you can't assign owners to records, or automatically notify team members when something needs to happen (instead, everyone has to be online all the time \"just in case\"), or take advantage of more effective views to represent data flow.\"\n  },\n  \"solution\": {\n    \"title\": \"Scalable systems & built-in project management\",\n    \"text\": \"1. First, I'll migrate & build you a scalable system:\\n\\nI'll help you migrate to Monday.com, a dedicated CRM and project management platform. This will address many of the scalability issues inherent to Google Sheets\u2014your team will be able to assign owners to records, receive notifications on important tasks, and communicate with eachother in a public, accountable way. \\n\\nIn addition, I'll build bespoke automations (both in Monday and using a third party tool, Make.com) to eliminate the need for manual record creation and related administrative functions. This will improve cycle time, better the quality of life of your staff, and decrease the likelihood of a costly error.\\n\\n2. Then, I'll help you improve cost efficiency:\\n\\nNext, we'll operationalize your procedures, add them to a library of SOPs, and begin scoping automated solutions to improve the effectiveness of each task. Much of the knowledge in your company currently exists in conversation or hidden direct messages and threads\u2014turning this into a central, accessible knowledge base will streamline new hire onboarding, significantly improve margins on tasks, and make your team much more flexible.\"\n  },\n  \"scope\": {\n    \"1\": \"We'll migrate your current Google Sheets set-up to Monday.com, a scalable CRM & project management system\",\n    \"2\": \"We'll create two boards\u2014a CRM board and a Project Management board\u2014which will be your single source of truth for business operations moving forward.\",\n    \"3\": \"We'll build you a process library that exhaustively covers your business SOPs, which will let your team train faster and delegate work more effectively.\",\n    \"4\": \"We'll produce an end-to-end piece of video documentation of the system upon delivery.\"},\n\"deliverable\": {\n    \"1\": \"Sheets -> Monday Migration\",\n    \"2\": \"SOPs & Process Library\",\n    \"3\": \"Video Documentation\"\n  }\n  \"timeline\": {\n    \"1\": \"5 business days\",\n    \"2\": \"3 business days\",\n    \"3\": \"1 business day\"\n  }\n}"
},
{
"content": "={\"problem\":\"{{ $json.form_response.answers[5].text }}\",\n\"solutionIPitched\":\"{{ $json.form_response.answers[6].text }}\"\"\n\"deliverables\":\"{{ $json.form_response.answers[7].text }}\",\n\"timeline\":\"{{ $json.form_response.answers[8].text }}\",\n\"companyDescription\":\"{{ $json.form_response.answers[4].text }}\"}"
}
]
},
"jsonOutput": true
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "2526fb73-6b90-4434-93d6-d605fdd702b8",
"name": "Generate PandaDoc File",
"type": "n8n-nodes-base.httpRequest",
"position": [
660,
250
],
"parameters": {
"url": "https://api.pandadoc.com/public/v1/documents",
"method": "POST",
"options": [],
"jsonBody": "={\n  \"owner\": {\n    \"email\": \"[YOUR_EMAIL]\"\n  },\n  \"template_uuid\": \"<template id>\",\n  \"name\": \"Proposal for {{ $('Client Intake Trigger').item.json.form_response.answers[3].text }}\",\n  \"metadata\": {\n    \"clickup_id\": \"{{ $('Client Intake Trigger').item.json.form_response.hidden.clickup_id }}\",\n    \"project_type\": \"proposal\",\n    \"source\": \"typeform_automation\"\n  },\n  \"fields\": {\n    \"Initials\": {\n      \"value\": \"AM\"\n    }\n  },\n  \"tokens\": [\n    {\n      \"name\": \"Client.ProposalTitle\",\n      \"value\": \"{{ $json.message.content.proposalTitle }}\"\n    },\n    {\n      \"name\": \"Client.ProblemTitle\",\n      \"value\": \"{{ $json.message.content.problemTitle }}\"\n    },\n    {\n      \"name\": \"Client.ProblemText\",\n      \"value\": \"{{ $json.message.content.problemText.replace(/\\n/g, '\\\\n') }}\"\n    },\n    {\n      \"name\": \"Client.SolutionTitle\",\n      \"value\": \"{{ $json.message.content.solutionTitle }}\"\n    },\n    {\n      \"name\": \"Client.SolutionText\",\n      \"value\": \"{{ $json.message.content.solutionText.replace(/\\n/g, '\\\\n') }}\"\n    },\n    {\n      \"name\": \"Client.Scope1\",\n      \"value\": \"{{ $json.message.content.scope1 }}\"\n    },\n    {\n      \"name\": \"Client.Scope2\",\n      \"value\": \"{{ $json.message.content.scope2 }}\"\n    },\n    {\n      \"name\": \"Client.Scope3\",\n      \"value\": \"{{ $json.message.content.scope3 }}\"\n    },\n    {\n      \"name\": \"Client.Scope4\",\n      \"value\": \"{{ $json.message.content.scope4 }}\"\n    },\n    {\n      \"name\": \"Client.Company\",\n      \"value\": \"{{ $('Client Intake Trigger').item.json.form_response.answers[3].text }}\"\n    },\n    {\n      \"name\": \"Client.LastName\",\n      \"value\": \"{{ $('Client Intake Trigger').item.json.form_response.answers[1].text }}\"\n    },\n    {\n      \"name\": \"Client.FirstName\",\n      \"value\": \"{{ $('Client Intake Trigger').item.json.form_response.answers[0].text }}\"\n    },\n    {\n      \"name\": \"Client.Timeline1\",\n      \"value\": \"{{ $json.message.content.timeline1 }}\"\n    },\n    {\n      \"name\": \"Client.Timeline2\",\n      \"value\": \"{{ $json.message.content.timeline2 }}\"\n    },\n    {\n      \"name\": \"Client.Timeline3\",\n      \"value\": \"{{ $json.message.content.timeline3 }}\"\n    },\n    {\n      \"name\": \"Client.Deliverable1\",\n      \"value\": \"{{ $json.message.content.deliverable1 }}\"\n    },\n    {\n      \"name\": \"Client.Deliverable2\",\n      \"value\": \"{{ $json.message.content.deliverable2 }}\"\n    },\n    {\n      \"name\": \"Client.Deliverable3\",\n      \"value\": \"{{ $json.message.content.deliverable3 }}\"\n    }\n  ],\n  \"recipients\": [\n    {\n      \"delivery_methods\": {\n        \"email\": true\n      },\n      \"redirect\": {\n        \"is_enabled\": false,\n        \"url\": \"https://example.com\"\n      },\n      \"type\": \"recipient\",\n      \"role\": \"Client\",\n      \"email\": \"{{ $('Client Intake Trigger').item.json.form_response.answers[2].email }}\",\n      \"first_name\": \"{{ $('Client Intake Trigger').item.json.form_response.answers[0].text }}\",\n      \"last_name\": \"{{ $('Client Intake Trigger').item.json.form_response.answers[1].text }}\"\n    }\n  ],\n  \"pricing_tables\": [\n    {\n      \"name\": \"Pricing Table 1\",\n      \"options\": {\n        \"currency\": \"USD\"\n      },\n      \"sections\": [\n        {\n          \"rows\": [\n            {\n              \"data\": {\n                \"qty\": 1,\n                \"name\": \"{{ $json.message.content.proposalTitle }}\",\n                \"price\": \"{{ $('Client Intake Trigger').item.json.form_response.answers[9].number }}\"\n              },\n              \"options\": {\n                \"optional\": false,\n                \"qty_editable\": false,\n                \"optional_selected\": false\n              }\n            }\n          ],\n          \"title\": \"Pricing Section\",\n          \"default\": true\n        }\n      ]\n    }\n  ]\n}",
"sendBody": true,
"sendHeaders": true,
"specifyBody": "json",
"headerParameters": {
"parameters": [
{
"name": "Authorization",
"value": "API-Key [CONFIGURE_YOUR_API_KEY]"
},
{
"name": "accept",
"value": "application/json"
}
]
}
},
"typeVersion": 4.2
},
{
"id": "5fa8478e-1e09-4510-86ab-54bc46f7def5",
"name": "Update CRM Task",
"type": "n8n-nodes-base.clickUp",
"position": [
430,
160
],
"parameters": {
"id": "={{ $('Client Intake Trigger').item.json.form_response.hidden.clickup_id }}",
"operation": "update",
"updateFields": {
"content": "=Company Summary: {{ $('Client Intake Trigger').item.json.form_response.answers[4].text }} \n\nProblem: {{ $('Client Intake Trigger').item.json.form_response.answers[5].text }}\n\nSolution I pitched: {{ $('Client Intake Trigger').item.json.form_response.answers[6].text }}\n\nDeliverables: {{ $('Client Intake Trigger').item.json.form_response.answers[7].text }}\n\nHow long: {{ $('Client Intake Trigger').item.json.form_response.answers[8].text }}"
},
"authentication": "oAuth2"
},
"credentials": {
"clickUpOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "96826976-e7c8-4eee-8245-47433633a4e7",
"name": "Set Company Field",
"type": "n8n-nodes-base.clickUp",
"position": [
200,
60
],
"parameters": {
"task": "={{ $json.id }}",
"field": "={{ $json.custom_fields[0].id }}",
"value": "={{ $('Client Intake Trigger').item.json.form_response.answers[3].text }}",
"operation": "setCustomField",
"authentication": "oAuth2"
},
"credentials": {
"clickUpOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "b8a6c4e1-08bb-4106-ad54-71b443b25638",
"name": "Set Quote Field",
"type": "n8n-nodes-base.clickUp",
"position": [
210,
380
],
"parameters": {
"task": "={{ $('Update CRM Task').item.json.id }}",
"field": "={{ $('Update CRM Task').item.json.custom_fields[9].id }}",
"value": "={{ $('Client Intake Trigger').item.json.form_response.answers[9].number }}",
"operation": "setCustomField",
"authentication": "oAuth2"
},
"credentials": {
"clickUpOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "67bc4dd5-1a1c-4943-bd53-2961da61106f",
"name": "Store Proposal Link",
"type": "n8n-nodes-base.clickUp",
"position": [
240,
210
],
"parameters": {
"task": "={{ $('Update CRM Task').item.json.id }}",
"field": "={{ $json.custom_fields[8].id }}",
"value": "=https://app.pandadoc.com/a/#/documents/{{ $('Generate PandaDoc File').item.json.id }}",
"operation": "setCustomField",
"authentication": "oAuth2"
},
"credentials": {
"clickUpOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "3cf561e4-17ee-41ab-b282-b670a381e7b6",
"name": "Client Intake Trigger",
"type": "n8n-nodes-base.typeformTrigger",
"position": [
1195,
210
],
"webhookId": "28fd78a2-c166-436b-8888-9f6b305ff2ad",
"parameters": {
"formId": "RADFsrT7",
"onlyAnswers": false,
"simplifyAnswers": false
},
"credentials": {
"typeformApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.1
},
{
"id": "847ab08d-ec61-4f24-b4b3-59427080e72a",
"name": "Gmail Draft Message",
"type": "n8n-nodes-base.gmail",
"position": [
20,
240
],
"webhookId": "44ef2e2b-9d2b-4974-94f7-d418f1bb09e4",
"parameters": {
"message": "=Hey {{ $('Client Intake Trigger').item.json.form_response.answers[0].text }}, thanks for the great call.\n<br><br>\nI put together a detailed proposal for you below. Please take a look at your earliest convenience and let me know your thoughts.\n<br><br>\n(proposal link)\n<br><br>\nHit me if you have any q's. You should be redirected pay after you sign, so I can get started soon as that's sorted.\n<br><br>\nCheers,<br>\n[YOUR_NAME]",
"options": {
"sendTo": "={{ $('Client Intake Trigger').item.json.form_response.answers[2].email }}"
},
"subject": "sent you the Proposal",
"resource": "draft",
"emailType": "html"
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
}
],
"pinData": [],
"connections": {
"Update CRM Task": {
"main": [
[
{
"node": "Set Company Field",
"type": "main",
"index": 0
},
{
"node": "Set Quote Field",
"type": "main",
"index": 0
},
{
"node": "Store Proposal Link",
"type": "main",
"index": 0
}
]
]
},
"Store Proposal Link": {
"main": [
[
{
"node": "Gmail Draft Message",
"type": "main",
"index": 0
}
]
]
},
"Client Intake Trigger": {
"main": [
[
{
"node": "Draft Proposal Text",
"type": "main",
"index": 0
}
]
]
},
"Set Company Field": {
"main": [
[]
]
},
"Draft Proposal Text": {
"main": [
[
{
"node": "Generate PandaDoc File",
"type": "main",
"index": 0
}
]
]
},
"Generate PandaDoc File": {
"main": [
[
{
"node": "Update CRM Task",
"type": "main",
"index": 0
}
]
]
}
},
"settings": [],
"active": false,
"versionId": null
}