Skip to content
Workflows

Basecamp Actions & Triggers in Workflows

Automate Basecamp with GHL Customer Care. Use instant triggers and premium actions to create projects, to‑do lists, tasks, and documents—plus setup, tips, and FAQs.

5 min read1,135 words10 explained images
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. Key Benefits of the Basecamp Integration
  2. Triggers & Actions
  3. How To Set Up the Basecamp Integration
  4. Build your first flow
  5. Use Cases
  6. Use Case 1: Create To‑do + Project Document from a GHL Customer Care Form
  7. Use Case 2: AI Kickoff Brief on “Closed Won”
  8. Use Case 3: Create To‑do List + Task from a GHL Customer Care Form
  9. Frequently Asked Questions
  10. Related Articles

Video 1 Open in a new tab

Connect Basecamp to GHL Customer Care to automate project setup, tasks, and team communication in real time. This guide mirrors the Typeform article’s structure and covers instant Basecamp → GHL Customer Care triggers, all available Basecamp actions you can run from a workflow, and step‑by‑step setup. You’ll also find mapping tips, billing notes, and related resources so your team can launch confidently.

TABLE OF CONTENTS

What is the Basecamp Integration in Workflows?

GHL Customer Care’s native Basecamp integration lets you react to Basecamp activity instantly and perform Basecamp tasks directly from a workflow. Use Basecamp triggers (like New To‑do or New Message Posted) to enroll records the moment activity happens, and add Basecamp actions (like Create Project, Create/Update To‑do, Create Message, Create Document) to streamline onboarding, task tracking, and client delivery.

Key Benefits of the Basecamp Integration

  • Faster handoffs: Automatically create projects, to‑do lists, and tasks when deals move to delivery.

  • Instant triggers: Webhook‑based triggers fire immediately—no polling delays.

  • Fewer duplicates: “Find” actions (Project/List/To‑do/Person/Document) let you search first, then create only when needed.

  • Flexible plans: Works with Basecamp’s free and paid plans (feature availability depends on your Basecamp plan).

  • Predictable costs: Basecamp triggers/actions are premium and billed per execution under Workflow Pro tiers; agencies can optionally rebill.

Triggers & Actions

Triggers (Basecamp → GHL Customer Care)
These events enroll records into a workflow the moment they occur in Basecamp.

TriggerFires when
New To‑doA new to‑do is created in Basecamp.
New Comment AddedA comment is added to a to‑do or message.
New DocumentA new document is created.
New ActivityNew activity occurs in a Basecamp project (project‑level event).
New Message PostedA new message is posted in a project.
New To‑do ListA new to‑do list is created.

Actions (GHL Customer Care → Basecamp)
Run these steps in workflows to create, update, or look up items inside Basecamp.

ActionPurpose / Example uses
Create ProjectCreate a new project (blank or from a template, where supported).
Create To‑do ListCreate a list inside a specific project.
Create To‑doAdd a task to a selected to‑do list (title, due date, assignee, etc.).
Update To‑doModify an existing task’s fields (title, due date, assignee, status).
Create MessagePost to a project’s message board.
Create Campfire MessageSend a chat message to a project's Campfire room.
Create DocumentCreate a text note or file entry in a project.
Add Person to ProjectAdd a team member or client to a project.
Find ProjectLocate an existing project to reference later steps and prevent duplicates.
Find To‑do ListLocate an existing to‑do list for downstream mapping.
Find To‑doLocate a to‑do by name/ID so you can update it reliably.
Find DocumentLocate an existing document to link/update.
Find PersonLocate a Basecamp user/client to add/assign.

How To Set Up the Basecamp Integration

Connect Basecamp (two paths)

  1. From a Trigger/Action step

  • In Workflows → open or create a workflow.

  • Click + Add Trigger (or + Add Action) and search Basecamp.

  • Choose a Basecamp trigger or action, then click Connect Now.

  • Sign in to Basecamp and authorize GHL Customer Care.

    Step 4 of 4: Sign in to Basecamp and authorize GHL Customer Care What this shows Step 4 of 4: Sign in to Basecamp and authorize GHL Customer Care. What this shows Shows what this covers for step 4 of 4 in the "How To Set Up the Basecamp Integration" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 4 of 4 in the "How To Set Up the Basecamp Integration" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you sign in to Basecamp and authorize GHL Customer Care. This part of the guide covers 2 fields, listed below. Step 4 of 4Image 1 of 10 What this coversSign in to Basecamp and authorize GHL Customer Care.
    Fields in this part of the guide From a Trigger/Action stepFrom Settings → Integrations
    Buttons and menus referenced Connect Basecamp (two paths)From a Trigger/Action step+ Add Trigger+ Add ActionBasecampConnect NowFrom Settings → IntegrationsSettings → Integrationsper sub‑account (location)
    All 4 steps in this procedure
    1. In Workflows → open or create a workflow.
    2. Click + Add Trigger (or + Add Action) and search Basecamp.
    3. Choose a Basecamp trigger or action, then click Connect Now.
    4. Sign in to Basecamp and authorize GHL Customer Care. this image

  1. From Settings → Integrations

  • Go to Settings → Integrations, locate Basecamp, and complete the OAuth connection.

  • Note: Connections are per sub‑account (location). Install/bulk install does not auto‑connect every location—authorize in each sub‑account that needs Basecamp.

    Step 2 of 2: Note: Connections are per sub‑account (location). Install/bulk install… What this shows Step 2 of 2: Note: Connections are per sub‑account (location). What this shows Shows what this covers for step 2 of 2 in the "How To Set Up the Basecamp Integration" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 2 of 2 in the "How To Set Up the Basecamp Integration" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you note: Connections are per sub‑account (location). Install/bulk install does not auto‑connect every location—authorize in each sub‑account that needs Basecamp. This part of the guide covers 2 fields, listed below. Step 2 of 2Image 2 of 10 What this coversNote: Connections are per sub‑account (location). Install/bulk install does not auto‑connect every location—authorize in each sub‑account that needs Basecamp.
    Fields in this part of the guide From a Trigger/Action stepFrom Settings → Integrations
    Buttons and menus referenced per sub‑account (location)Connect Basecamp (two paths)From a Trigger/Action step+ Add Trigger+ Add ActionBasecampConnect NowFrom Settings → IntegrationsSettings → Integrations
    All 2 steps in this procedure
    1. Go to Settings → Integrations, locate Basecamp, and complete the OAuth connection.
    2. Note: Connections are per sub‑account (location). Install/bulk install does not auto‑connect every location—authorize in each sub‑account that needs Basecamp. this image

Build your first flow

  1. From the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one).

    Step 1 of 5: From the desired sub‑account, go to Automations → Workflows and click… What this shows Step 1 of 5: From the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one). What this shows Shows what to click for step 1 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 1 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you from the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one). The next step is to add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required). Step 1 of 5Image 3 of 10 What to clickFrom the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one).
    Buttons and menus referenced Automations → WorkflowsCreate WorkflowTriggerActionsNotify UserSend EmailUpdate OpportunityPublishExecution Logs
    Next stepAdd a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required).
    All 5 steps in this procedure
    1. From the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one). this image
    2. Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required).
    3. Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).
    4. Add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).
    5. Publish and perform a one‑time event (e.g., create a to‑do in Basecamp) to verify entries appear in Execution Logs.

  2. Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required).

    Step 2 of 5: Add a Basecamp Trigger (e.g., New To‑do) and select the target project… What this shows Step 2 of 5: Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required). What this shows Shows what to choose for step 2 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 2 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required). The next step is to add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). Step 2 of 5Image 4 of 10 What to chooseAdd a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required).
    Buttons and menus referenced TriggerAutomations → WorkflowsCreate WorkflowActionsNotify UserSend EmailUpdate OpportunityPublishExecution Logs
    Next stepAdd Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).
    All 5 steps in this procedure
    1. From the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one).
    2. Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required). this image
    3. Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).
    4. Add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).
    5. Publish and perform a one‑time event (e.g., create a to‑do in Basecamp) to verify entries appear in Execution Logs.
    Step 2 of 5: Add a Basecamp Trigger (e.g., New To‑do) and select the target project… What this shows Step 2 of 5: Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required). What this shows Shows what to choose for step 2 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 2 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required). The next step is to add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). Step 2 of 5Image 5 of 10 What to chooseAdd a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required).
    Buttons and menus referenced TriggerAutomations → WorkflowsCreate WorkflowActionsNotify UserSend EmailUpdate OpportunityPublishExecution Logs
    Next stepAdd Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).
    All 5 steps in this procedure
    1. From the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one).
    2. Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required). this image
    3. Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).
    4. Add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).
    5. Publish and perform a one‑time event (e.g., create a to‑do in Basecamp) to verify entries appear in Execution Logs.

  3. Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).

    Step 3 of 5: Add Basecamp Actions (e.g., Find Project → If Not Found → Create… What this shows Step 3 of 5: Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). What this shows Shows what this covers for step 3 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 3 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). The next step is to add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity). Step 3 of 5Image 6 of 10 What this coversAdd Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).
    Buttons and menus referenced ActionsAutomations → WorkflowsCreate WorkflowTriggerNotify UserSend EmailUpdate OpportunityPublishExecution Logs
    Next stepAdd internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).
    All 5 steps in this procedure
    1. From the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one).
    2. Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required).
    3. Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). this image
    4. Add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).
    5. Publish and perform a one‑time event (e.g., create a to‑do in Basecamp) to verify entries appear in Execution Logs.
    Step 3 of 5: Add Basecamp Actions (e.g., Find Project → If Not Found → Create… What this shows Step 3 of 5: Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). What this shows Shows what this covers for step 3 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 3 of 5 in the "Build your first flow" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). The next step is to add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity). Step 3 of 5Image 7 of 10 What this coversAdd Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do).
    Buttons and menus referenced ActionsAutomations → WorkflowsCreate WorkflowTriggerNotify UserSend EmailUpdate OpportunityPublishExecution Logs
    Next stepAdd internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).
    All 5 steps in this procedure
    1. From the desired sub‑account, go to Automations → Workflows and click Create Workflow (or open an existing one).
    2. Add a Basecamp Trigger (e.g., New To‑do) and select the target project or scope (as required).
    3. Add Basecamp Actions (e.g., Find Project → If Not Found → Create Project, then Create To‑do List → Create To‑do). this image
    4. Add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).
    5. Publish and perform a one‑time event (e.g., create a to‑do in Basecamp) to verify entries appear in Execution Logs.

  4. Add internal follow‑ups (e.g., Notify User, Send Email, Update Opportunity).

  5. Publish and perform a one‑time event (e.g., create a to‑do in Basecamp) to verify entries appear in Execution Logs.

Use Cases

Use Case 1: Create To‑do + Project Document from a GHL Customer Care Form

  • Goal: Turn a submitted intake form into actionable Basecamp work and documentation.

  • Workflow Setup:

    • Trigger: Form Submitted

    • Filter: Form Name = “Project Intake Form”

    • Actions: Create To‑do (Basecamp), Create Document (Basecamp), Notify User

  • Example: A client submits the “Project Intake” form. A task appears in Basecamp (“Create workspace for Client X”), a document is created with the form answers, and your team is notified to kick off.

    Step 3 of 3: Example: A client submits the “Project Intake” form. A task appears in… What this shows Step 3 of 3: Example: A client submits the “Project Intake” form. What this shows Shows what this covers for step 3 of 3 in the "Use Case 1: Create To‑do + Project Document from a GHL Customer Care Form" section of "Basecamp Actions & Triggers in Workflows". This screenshot accompanies step 3 of 3 in the "Use Case 1: Create To‑do + Project Document from a GHL Customer Care Form" section of "Basecamp Actions & Triggers in Workflows". At this point in the walkthrough you example: A client submits the “Project Intake” form. A task appears in Basecamp (“Create workspace for Client X”), a document is created with the form answers, and your team is notified to kick off. This part of the guide covers 3 fields, listed below. Step 3 of 3Image 8 of 10 What this coversExample: A client submits the “Project Intake” form. A task appears in Basecamp (“Create workspace for Client X”), a document is created with the form answers, and your team is notified to kick off.
    Fields in this part of the guide Workflow Setup:Trigger: Form SubmittedFilter: Form Name = “Project Intake Form”
    Buttons and menus referenced Form SubmittedCreate To‑doCreate DocumentNotify User
    All 3 steps in this procedure
    1. Goal: Turn a submitted intake form into actionable Basecamp work and documentation.
    2. Workflow Setup:
    3. Example: A client submits the “Project Intake” form. A task appears in Basecamp (“Create workspace for Client X”), a document is created with the form answers, and your team is notified to kick off. this image

Use Case 2: AI Kickoff Brief on “Closed Won”

  • Goal: Generate a project summary via AI, store it in Basecamp, and alert the team.

  • Workflow Setup:

    • Trigger: Opportunity Stage Changed (Stage = Closed Won)

    • Filter: Opportunity Stage = “Closed Won”

    • Actions: GPT (OpenAI) → Create Document (Basecamp) → Notify User

  • Example: When the deal closes, AI drafts a kickoff brief using opportunity details. The brief is saved as a Basecamp document and the onboarding team is notified.

Use Case 2: AI Kickoff Brief on “Closed Won” (image 9 of 10) What this shows Goal: Generate a project summary via AI, store it in Basecamp, and alert the team. What this shows Illustrates the "Use Case 2: AI Kickoff Brief on “Closed Won”" section of "Basecamp Actions & Triggers in Workflows". This screenshot appears in the "Use Case 2: AI Kickoff Brief on “Closed Won”" section of "Basecamp Actions & Triggers in Workflows". The text alongside this image reads: Goal: Generate a project summary via AI, store it in Basecamp, and alert the team. Workflow Setup: Example: When the deal closes, AI drafts a kickoff brief using opportunity details. The brief is saved as a Basecamp document and the onboarding team is notified. This part of the guide covers 3 fields, listed below. Immediately after, the guide continues: Goal: Stand up a fresh list with a first task whenever a request form is submitted. Workflow Setup: Example: On submission, a new list “Website Redesign – Client ABC” is created. If successful, a task “Assign designer & schedule kickoff”…. Image 9 of 10 What this coversGoal: Generate a project summary via AI, store it in Basecamp, and alert the team. Workflow Setup: Example: When the deal closes, AI drafts a kickoff brief using opportunity details. The brief is saved as a Basecamp document and the onboarding team is notified.
Fields in this part of the guide Workflow Setup:Trigger: Opportunity Stage Changed (Stage = Closed Won)Filter: Opportunity Stage = “Closed Won”
Buttons and menus referenced Opportunity Stage ChangedGPT (OpenAI)Create DocumentNotify User
Next stepGoal: Stand up a fresh list with a first task whenever a request form is submitted. Workflow Setup: Example: On submission, a new list “Website Redesign – Client ABC” is created. If successful, a task “Assign designer & schedule kickoff” is added so work can begin immediately.
All 3 steps in this procedure
  1. Goal: Generate a project summary via AI, store it in Basecamp, and alert the team.
  2. Workflow Setup:
  3. Example: When the deal closes, AI drafts a kickoff brief using opportunity details. The brief is saved as a Basecamp document and the onboarding team is notified.

Use Case 3: Create To‑do List + Task from a GHL Customer Care Form

  • Goal: Stand up a fresh list with a first task whenever a request form is submitted.

  • Workflow Setup:

    • Trigger: Form Submitted

    • Filter: None

    • Actions: Create To‑do List (Basecamp) → Condition → Create To‑do (Basecamp)

  • Example: On submission, a new list “Website Redesign – Client ABC” is created. If successful, a task “Assign designer & schedule kickoff” is added so work can begin immediately.

Use Case 3: Create To‑do List + Task from a GHL Customer Care Form (image 10 of 10) What this shows Goal: Stand up a fresh list with a first task whenever a request form is submitted. What this shows Illustrates the "Use Case 3: Create To‑do List + Task from a GHL Customer Care Form" section of "Basecamp Actions & Triggers in Workflows". This screenshot appears in the "Use Case 3: Create To‑do List + Task from a GHL Customer Care Form" section of "Basecamp Actions & Triggers in Workflows". The text alongside this image reads: Goal: Stand up a fresh list with a first task whenever a request form is submitted. Workflow Setup: Example: On submission, a new list “Website Redesign – Client ABC” is created. If successful, a task “Assign designer & schedule kickoff” is added so work can begin immediately. This part of the guide covers 3 fields, listed below. Immediately after, the guide continues: Q: Do I need a paid Basecamp plan? The integration works with Basecamp’s free and paid plans. Advanced Basecamp features still follow your Basecamp subscription limits. Image 10 of 10 What this coversGoal: Stand up a fresh list with a first task whenever a request form is submitted. Workflow Setup: Example: On submission, a new list “Website Redesign – Client ABC” is created. If successful, a task “Assign designer & schedule kickoff” is added so work can begin immediately.
Fields in this part of the guide Workflow Setup:Trigger: Form SubmittedFilter: None
Buttons and menus referenced Form SubmittedCreate To‑do ListConditionCreate To‑do
Next stepQ: Do I need a paid Basecamp plan? The integration works with Basecamp’s free and paid plans. Advanced Basecamp features still follow your Basecamp subscription limits.
All 3 steps in this procedure
  1. Goal: Stand up a fresh list with a first task whenever a request form is submitted.
  2. Workflow Setup:
  3. Example: On submission, a new list “Website Redesign – Client ABC” is created. If successful, a task “Assign designer & schedule kickoff” is added so work can begin immediately.

Frequently Asked Questions

Q: Do I need a paid Basecamp plan?
The integration works with Basecamp’s free and paid plans. Advanced Basecamp features still follow your Basecamp subscription limits.

Q: Can I sync data both ways between Basecamp and GHL Customer Care?
The integration currently supports one-way sync. You can trigger workflows when events happen in Basecamp or perform actions in Basecamp from GHL Customer Care. For full bi-directional syncing, use middleware platforms like Make or Zapier.

Q: Are the Basecamp steps premium‑billed in GHL Customer Care?
Yes. Basecamp triggers and actions are premium and billed per execution at your account’s standard rate. Agencies can optionally rebill sub‑accounts.

Q: Can I create a project from a template?
Yes. Create Project supports creating from a template when available in your Basecamp account.

Q: Where do I troubleshoot failures?
Open Execution Logs to review the specific step error (e.g., invalid ID, missing permission). If authorization expired, reconnect Basecamp under Settings → Integrations and re‑run a test.

Q: Can I connect multiple Basecamp accounts?
Yes. Authenticate the appropriate Basecamp account per sub‑account and select the desired connection in each action/trigger step. Changing the selected account may reload or reset account-dependent fields.

Was this guide helpful?

Related guides

Introduction to Workflows and Automations4 min read · 9 imagesWorkflow Notes, Action Notes & Sticky Notes3 min read · 11 imagesWorkflows Pro Plan - New Pricing Tiers5 min read · 8 imagesComprehensive workflow stats1 min read · 3 images