Skip to main content

📊 Module 2: Export Your Opportunities into Google Sheets

Auto-log your applied opportunities into Google Sheets.

Written by Thibaut Vanderhofstadt

In this module, you’ll connect Sortlist → Google Sheets so every opportunity you apply to is logged automatically in a spreadsheet.

Why this matters:

  • You’ll finally see the full data structure Sortlist can send.

  • You can filter, analyze, and share opportunities with your team.

  • And once you’ve mapped fields into Sheets, you’ll understand how to map them into any system (HubSpot, Pipedrive, Notion…).

Think of this step as your data cockpit: everything laid out clearly, row by row.

🛠 Preparation – Create Your Spreadsheet

Before you build the Zap, you need to prepare the destination. Zapier can only put data where a column header exists.

👉 Open Google Sheets and create a new file called:

Sortlist Opportunities Applied

If you want to save some time, I’ve done it for you here. You can copy this Google Spreadsheet to your Drive: Copy this file on your Drive

Start Simple

If this is your first integration, just create these columns:

Column Header

Why it’s useful

Opportunity ID

Unique ID of Opportunities → prevents duplicates in any softwares, CRM.

Title

Opportunity title to have same reference with Sortlist Opportunity Title interface

Expertise

Requested service.

Sector

Client’s industry.

Location

Client’s location.

Budget Min

Quick budget check.

Budget Max

Upper budget limit.

Opportunity Link

1-click back to Sortlist.

Applied At

When you applied.

This gives you a clean, lightweight log you can build on. Zapier also offers data mapping solutions such as Zapier Tables, which work much like Google Spreadsheets, database storage. It’s up to you to decide what best fits your needs 😉.

Note: Power users can access the full Sortlist integration data documentation here: Opportunity Applied Explained.

⚠️ Working with data — and understanding its usage and meaning — is very important. If used incorrectly, it can mess up your CRM, communication channels, and even create more noise instead of efficiency. That’s why we recommend always starting small, and following the Zapier training program in parallel to ensure you understand the tools, the data, and avoid mistakes in your future integrations.

🛠 Step 1 – Set Up the Trigger

  1. In Zapier, click Create Zap.

  2. For the Trigger App, select Sortlist.

  3. Choose the trigger: Opportunity Applied.

    • Fires every time you apply to an opportunity.

    • Great for building your personal activity log.

🛠 Step 2 – Connect Sortlist

  1. Connect your Sortlist account.

  2. Connect your Provider's Profile.

  3. Run a test → Zapier will pull a sample opportunity - Opportunity A.

👉 Here you’ll see fields like title, budget_min, sector, location… this is the raw payload you can map.

🛠 Step 3 – Add Google Sheets as the Action

  1. For the Action App, choose Google Sheets.

  2. Select Create Spreadsheet Row.

  3. Pick your spreadsheet Sortlist Opportunities Applied.

🛠 Step 4 – Map Your Data

This is where you connect the dots. Each Sortlist field → one column in your Google Sheet. eg: Sheet 1

Example mapping (simple version):

Google Sheet Column

Map this Sortlist field

Opportunity ID

id

Title

title

Expertise

expertise

Sector

sector

Location

location

Budget Min

budget_min

Budget Max

budget_max

Opportunity Link

opportunity_link

Applied At

applied_at

🛠 Step 5 – Test & Activate

  1. Click Test Action.

  2. Go check your Google Sheet → a row should appear instantly.

  3. If it looks good, click Publish Zap. 🎉


🎉 Micro-Win Unlocked

You now have a living log of all applied opportunities. That means:

  • No more copy-paste.

  • Full visibility on budgets, sectors, and locations.

  • A ready-to-share file for reporting or analysis.

Time spent: 5 minutes
Benefit gained: a clean data cockpit 🚀

📚 Learn More

If you’re curious about how Zapier works under the hood:


🚀 Next Step

Now that you understand data mapping in Zapier, you’re ready to connect Sortlist directly to your CRM — so your pipeline updates itself.

Did this answer your question?