You can use Zapier to connect Anchor with ClickUp so that whenever a client signs a proposal, a ClickUp Space is created for them automatically, along with onboarding tasks based on the services included in their agreement.
📣 Note: This integration is in beta. If you run into any issues or have questions, reach out to us at [email protected].
Anchor > ClickUp, Automatically create Space/Tasks on proposal approval
What this Zap does
Whenever a proposal is approved in Anchor, this Zap will:
Create a Space in ClickUp named after the client's business name and the agreement name.
Save the signed agreement's Anchor ID into that Space, so you can reference it for ClickUp-to-Anchor actions in other Zaps.
Check which services were included in the signed proposal, and create a folder with onboarding tasks in ClickUp for each matching service, using folder templates you set up in advance.
First, open the Zap template here and follow the steps along. You can refer to this article for guidance.
Before you start
In ClickUp, create a folder template for each Anchor service you want to trigger onboarding tasks for. Each template should include the tasks relevant to that service. It's recommended to name your templates to match your Anchor service names exactly, since this makes mapping much easier later.
Setting up the Zap
1. Getting started
Click Use this template. Name your Zap and choose which folder you wish to save it in. Click Next to move through the guided setup.
2. Connect your apps
Anchor — click Select. You'll be asked for:
API Key — generate this from Integrations > API keys in your Anchor account.
Email — the email of an Anchor team member with admin or owner permissions.
ClickUp — click Select, then connect your account. Before connecting, make sure you've already created the folder templates described above, one for each Anchor service you want to trigger tasks for.
3. Fields
Most of this Zap can be filled in directly from the guided setup, since it pulls from Anchor data rather than a form submission. The one exception is the folder template selection in each service path, which you'll map after publishing (see step 5 below).
This template has the following steps:
Step 1, Proposal Approved — the trigger. Fires automatically on every approved proposal, nothing to configure here.
Step 2, Create Space in ClickUp:
Workspace — choose the ClickUp workspace to create the Space in.
Name — by default this is set to the client's business name followed by the agreement name, but you can map it to any other field from the signed proposal, or add your own text.
The remaining fields (Private Space, Time estimates, Custom Fields, Multiple Assignees, Time Tracking, Tags) come with defaults already set. Adjust them if you'd like your Space configured differently.
Step 3, Save Anchor agreement ID:
Workspace — choose the same workspace you selected in step 2.
Content — this is pre-filled with the Anchor ID of the signed agreement, which gets pushed into the Space created in step 2. You can leave this as is.
Step 4, Split into paths — the Zap checks the services included in the signed agreement and branches based on which ones match. Any path whose condition matches will run, so a single proposal with multiple services can trigger multiple task sets in the same run.
Setting up each service path
The template comes with two example paths (Path A and Path B) to show you the structure. For each path:
Click into the Path conditions step. This checks whether the "Services Name" field from the signed agreement contains (or exactly matches, if you'd prefer) a specific service name. Replace the example text with the name of one of your own services (After publishing the Zap, you can add more paths if you have a wider variety of services you want to trigger tasks for).
Click into the Create Folder in ClickUp step for that path:
Workspace — choose the same workspace as step 2.
Folder Name — choose what to call the folder. By default this is set to the service name followed by the client's business name, but you can adjust it.
Template — leave this for now. You'll map it after publishing, once ClickUp can show your actual folder templates (see step 5 below).
Important note: If a service in the signed agreement doesn't match any of your configured path conditions, that path simply won't run, no folder or tasks will be created for that service.
4. Review and publish
Once Zapier confirms all steps are set up, click Publish.
5. Map your folder templates
Now that the Zap is live, open it to edit it. For each service path, click into the Create Folder in ClickUp step and open the Template dropdown. It will now show the actual folder templates in your ClickUp workspace, select the one that matches the service for that path. Test each Create Folder step once mapped.
To confirm everything's working end to end, sign a test proposal in Anchor that includes one of your configured services. You should see a matching Space and folder with onboarding tasks created in ClickUp shortly after.
Still have questions? Email us at [email protected].