Why use 5-minute polling instead of real-time webhooks?

Basecamp 3 connector in Power Automate doesn't support webhooks. The API allows polling every few minutes without hitting rate limits, and 5 minutes is fast enough for most urgent scenarios.

What happens if multiple urgent items are posted simultaneously?

The flow processes each item individually in the same run. All urgent items from that 5-minute window will trigger separate Slack notifications and DMs.

Can I customize which Basecamp projects trigger alerts?

Yes, enter specific project IDs in the Get recordings action instead of leaving it blank. Get project IDs from the Basecamp URL when viewing each project.

How do I handle urgent items posted by external clients?

External emails won't match your Slack users. Create a fallback that DMs a designated project manager when the Slack user lookup fails, or post to a catch-all channel.

Intermediate~15 min setupCommunication & Project ManagementVerified April 2026

How to Send Basecamp Urgent Items to Slack with Power Automate

Automatically detect high-priority Basecamp messages and to-dos, then trigger instant Slack notifications to project managers.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Power Automate

Also on:Make Zapier N8n Pipedream

Best for

Teams managing client projects in Basecamp who need instant alerts for urgent issues posted during off-hours

Not ideal for

Teams wanting two-way sync or real-time webhooks - Basecamp's API limitations force 5-minute polling delays

Sync type

scheduled

Use case type

notification

Real-World Example

💡

A 12-person design agency runs client projects in Basecamp. When clients post messages containing 'URGENT' or 'ASAP', the flow immediately pings the #client-alerts Slack channel and DMs the project manager. Before automation, urgent requests sat unnoticed for hours because PMs only checked Basecamp twice daily.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

cheapest

Power Automatethis guide

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

Prices shown for annual billing. Based on published pricing as of April 2026.

Estimated ROI

1000

min saved/mo

$583

labor value/mo

Free

no platform cost

Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.

Implementation

Skip the setup

Import this workflow directly into Power Automate

Copy the pre-built Power Automate blueprint and paste it straight into Power Automate. All modules, filters, and field mappings are already configured — you just need to connect your accounts.

Before You Start

Make sure you have everything ready.

Basecamp 3 account with admin access to projects you want to monitor

Slack workspace with permission to install apps and post to target channels

SharePoint site or Dataverse environment to store processed item tracking

Power Automate license (included with Microsoft 365 or standalone)

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Recording ID		Unique identifier from Basecamp to prevent duplicate notifications
Project Name		Basecamp project title to provide context in Slack messages
Item Title		Subject line or title of the urgent Basecamp message or to-do
Creator Email		Person who posted the urgent item, used for Slack user lookup
Item URL		Direct link back to the Basecamp item for quick access
Item Content		Message body text used for urgent keyword detection

1 optional field▸ show

Created Date

Step-by-Step Setup

My flows > + New flow > Automated cloud flow

Create automated cloud flow

Navigate to make.powerautomate.com and sign in with your Microsoft account. Click 'My flows' in the left sidebar, then '+ New flow' at the top. Select 'Automated cloud flow' from the dropdown menu. Name your flow 'Basecamp Emergency Escalation' and leave the trigger selection blank for now.

1Click 'My flows' in the left navigation
2Click '+ New flow' button at the top
3Select 'Automated cloud flow'
4Enter flow name: 'Basecamp Emergency Escalation'
5Click 'Create' without selecting a trigger

✓ What you should see: You should see a blank flow canvas with 'Choose your flow's trigger' at the top.

Flow canvas > Choose trigger > Search 'Recurrence'

Add Basecamp recurrence trigger

Click the trigger box and search for 'Recurrence' in the connector search. Select the Recurrence trigger since Basecamp doesn't support webhooks in Power Automate. Set the interval to 5 minutes - this balances responsiveness with API rate limits. Basecamp allows 1,728 requests per day per integration.

1Click 'Choose your flow's trigger'
2Search for 'Recurrence' and select it
3Set Interval to '5'
4Set Frequency to 'Minute'
5Click 'New step'

✓ What you should see: A purple Recurrence box appears showing 'Every 5 minutes' with a green checkmark.

⚠

Common mistake — Don't set this below 5 minutes or you'll hit Basecamp's rate limit of 50 requests per 10-second window.

Power Automate

click +

search apps

Slack

Add Basecamp recurrence trig…

Slack

module added

New step > Search 'Basecamp 3' > Get recordings

Connect to Basecamp

Add a new step and search for 'Basecamp 3' in the connectors list. Select 'Get recordings' action - this retrieves recent activity from your Basecamp projects. You'll need to authenticate with your Basecamp account credentials. Make sure your account has access to all projects you want to monitor.

1Click '+ New step'
2Search for 'Basecamp 3'
3Select 'Get recordings' action
4Click 'Sign in' and authenticate with Basecamp
5Select your Basecamp account from the dropdown

✓ What you should see: The Basecamp 3 connector shows 'Connected' status with your account name displayed.

⚠

Common mistake — If you don't see 'Basecamp 3', your tenant might have restricted connectors - check with your Microsoft admin.

Get recordings > Project parameters

Configure Basecamp project scope

In the Get recordings action, you need to specify which projects to monitor. Leave the Project ID field blank to monitor all projects, or enter specific project IDs separated by commas. Set the 'since' parameter to filter recent items - use the expression builder to subtract 10 minutes from the current time to catch items you might have missed.

1Leave 'Project ID' blank to monitor all projects
2Click the 'Since' field
3Click 'Expression' tab
4Enter: addMinutes(utcNow(), -10)
5Click 'OK'

✓ What you should see: The Since field shows your expression, and Project ID shows 'Select a value' if monitoring all projects.

⚠

Common mistake — The 10-minute lookback prevents missing items if the flow runs late, but creates duplicate risk that we'll handle later.

New step > Filter array

Filter for urgent messages

Add a 'Filter array' action to identify urgent items. This checks message content for keywords like 'URGENT', 'EMERGENCY', 'ASAP', or 'HIGH PRIORITY'. The filter examines both the title and excerpt fields from Basecamp recordings. You'll build a complex condition using the 'or' operator to catch various urgency indicators.

1Click '+ New step' and search 'Filter array'
2Set 'From' to 'value' from Get recordings
3Click 'Edit in advanced mode'
4Enter the filter expression for urgent keywords
5Save the filter configuration

✓ What you should see: Filter array shows 'From: value' and your filter expression in advanced mode.

⚠

Common mistake — Don't filter by Basecamp's built-in priority field - most users don't set it consistently.

Slack

trigger

filter

Condition

= "Urgent"

yes — passes through

no — skipped

Basecamp

notified

New step > SharePoint > Get items

Add duplicate prevention

Create a SharePoint list or use Dataverse to track processed items. Add a 'Get items' action to check if the current Basecamp recording ID already exists. This prevents sending duplicate Slack notifications when the same urgent item appears in multiple polling cycles. Store the recording ID and timestamp for each processed item.

1Click '+ New step' and search 'SharePoint'
2Select 'Get items' action
3Choose your SharePoint site
4Select or create 'Processed Items' list
5Add filter: ID eq 'recording_id_from_basecamp'

✓ What you should see: SharePoint connection established with your site and list selected in the dropdown.

⚠

Common mistake — Create the SharePoint list first with columns for Recording ID (text) and Processed Date (date/time).

New step > Control > Condition

Add condition for new items

Insert a Condition control to check if the SharePoint query returned any results. If the list is empty (length equals 0), the item is new and should trigger a Slack notification. This prevents duplicate alerts while ensuring new urgent items get immediate attention. The condition branches your flow into 'Yes' and 'No' paths.

1Click '+ New step' and search 'Condition'
2Set left value to 'length' of SharePoint items
3Set operator to 'is equal to'
4Set right value to '0'
5Continue building the 'Yes' branch

✓ What you should see: A diamond-shaped condition appears with 'Yes' and 'No' branches below it.

⚠

Common mistake — Filters are the most common place setups break. Double-check the field name and value exactly match what your app sends — a single capital letter difference will block everything.

Yes branch > New step > Slack > Post message

Configure Slack notification

In the 'Yes' branch, add a Slack 'Post message' action. Connect your Slack workspace and select the target channel for urgent notifications. Build a formatted message including the Basecamp project name, item title, creator, and a direct link back to Basecamp. Use Slack's block formatting for better readability.

1Click 'Add an action' in the Yes branch
2Search for 'Slack' and select 'Post message'
3Authenticate with your Slack workspace
4Select channel (e.g., #client-alerts)
5Build message with Basecamp dynamic content

✓ What you should see: Slack shows 'Connected' with your workspace name and channel selected.

⚠

Common mistake — Test with a private channel first to avoid spamming your team during setup.

Yes branch > New step > Slack > Send direct message

Add direct message to project manager

Add another Slack action to send a direct message to the project manager. You'll need to map Basecamp project creators or assignees to Slack user IDs. Create a lookup table using a SharePoint list or hardcode common mappings. Include more detailed context in the DM since it's going directly to the responsible person.

1Click 'Add an action' in the Yes branch
2Select Slack 'Send direct message'
3Map Basecamp creator to Slack user
4Compose detailed message with project context
5Include direct link to Basecamp item

✓ What you should see: Second Slack action configured for direct messaging with user mapping.

⚠

Common mistake — Slack user IDs look like U01234ABCD - don't use display names or email addresses.

message template

🔔 New Record: {{text}} {{user}}
channel: {{channel}}
ts: {{ts}}

#sales

🔔 New Record: Jane Smith

Email: [email protected]

Company: Acme Corp

Yes branch > New step > SharePoint > Create item

Record processed item

Still in the 'Yes' branch, add a SharePoint 'Create item' action to log this notification. Store the Basecamp recording ID, project name, processed timestamp, and Slack message status. This prevents future duplicate notifications and provides an audit trail of all escalated items.

1Click 'Add an action' in the Yes branch
2Select SharePoint 'Create item'
3Choose your 'Processed Items' list
4Map Recording ID from Basecamp
5Set Processed Date to utcNow()

✓ What you should see: SharePoint create action configured with fields mapped from Basecamp data.

Flow header > Save > Test

Test and activate flow

Save your flow and run a test. Create a test message in Basecamp containing 'URGENT TEST' and wait 5 minutes for the next polling cycle. Check your Slack channel and DMs for the notification. Review the SharePoint list to confirm the item was logged. Once verified, turn on the flow to begin monitoring.

1Click 'Save' in the flow header
2Click 'Test' and select 'Manually'
3Create urgent test item in Basecamp
4Wait for next 5-minute cycle
5Verify Slack notifications arrived

✓ What you should see: Flow shows 'Your flow ran successfully' with green checkmarks on all actions.

⚠

Common mistake — If testing fails, check the flow run history for detailed error messages on each step.

Use this Power Fx expression in your Filter array action to catch urgent keywords while handling case sensitivity and partial matches. Paste it in the advanced mode filter expression.

Copy this templateor(

▸ Show code

or(
  contains(toLower(item()?['title']), 'urgent'),
  contains(toLower(item()?['title']), 'emergency'),

... expand to see full code

or(
  contains(toLower(item()?['title']), 'urgent'),
  contains(toLower(item()?['title']), 'emergency'),
  contains(toLower(item()?['title']), 'asap'),
  contains(toLower(item()?['excerpt']), 'urgent'),
  contains(toLower(item()?['excerpt']), 'emergency'),
  contains(toLower(item()?['excerpt']), 'high priority'),
  contains(toLower(item()?['excerpt']), 'critical'),
  startsWith(toLower(item()?['title']), '!!!'),
  contains(toLower(item()?['title']), 'down'),
  contains(toLower(item()?['excerpt']), 'broken')
)

Power Automate

▶ Test flow

executed

✓

Slack

✓

Basecamp

🔔 notification

received

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test urgent keyword detection with various formats and case sensitivity

Verify SharePoint list permissions allow flow to read and write processed items

Map Basecamp users to Slack user IDs for accurate direct message routing

Set up monitoring for flow failures using Power Automate email notifications

Configure Slack channel notifications to mention @channel for critical alerts

Document your urgent keyword list so team members know what triggers alerts

Test duplicate prevention by creating same urgent item twice within 10 minutes

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy n8n for this workflow

Use Power Automate for this if you're already deep in the Microsoft ecosystem and need SharePoint for tracking processed items. The built-in Basecamp 3 connector saves setup time compared to webhook alternatives. Skip Power Automate if you need real-time alerts - Zapier's webhook support reacts in seconds versus Power Automate's 5-minute polling delay.

Cost

This workflow costs 288 runs per day (every 5 minutes) plus one additional run per urgent item detected. At 20 urgent items monthly, you're looking at 8,660 total runs. That burns through the free 2,000 runs instantly - you'll need the $15/month plan. Zapier handles the same volume for $20/month but triggers instantly. Make offers 1,000 operations monthly free, making it cheaper for low-volume urgent items.

Tradeoffs

Zapier's Basecamp webhook triggers instantly when messages are posted, while Power Automate forces polling delays. Make's visual builder handles complex keyword filtering better than Power Automate's expression syntax. n8n gives you full control over duplicate detection logic without needing SharePoint. Pipedream's code-first approach handles Basecamp's API quirks more gracefully. But Power Automate wins if your IT team already manages SharePoint permissions and you need audit trails in familiar Microsoft tools.

You'll hit Basecamp's rate limits if you monitor too many projects simultaneously - the API allows 50 requests per 10-second window. Large message threads trigger multiple notifications because Basecamp's recording API returns each comment separately. Slack user ID mapping breaks when people change email addresses, causing DM delivery failures that fail silently.

Ideas for what to build next

→
Add severity levels — Create different Slack channels for HIGH, MEDIUM, and LOW priority based on keyword matching. Route critical items to #emergency and standard urgent items to #alerts.
→
Build escalation chains — If no response in Slack within 15 minutes, send SMS via Twilio or create PagerDuty incidents for true emergencies.
→
Create summary reports — Send weekly digest of all escalated items to management showing response times and resolution status from Basecamp and Slack thread tracking.