Wildnote teams: The handoff that runs itself

Explore how Fulcrum automates the steps occuring after a record is submitted — and what that means for field teams, project managers, and the people who work with your data.

The relay race no one signed up for

Here’s a scene most environmental project managers know well.

It’s 5pm. Your field crew has wrapped up a long day of SWPPP inspections that included fifteen sites, three flagged for corrective action. The records are in Fulcrum. Now someone needs to read through them, pull out the flagged ones, write up a task for the project manager, send a Teams message to the site supervisor, and add three rows to the compliance log spreadsheet.

None of that administrative work is on anyone’s job description, yet it falls on the team simply because data doesn’t move on its own.

Fulcrum takes over the repetitive relay. Your team still makes the important calls, such as determining corrective actions and verifying issue resolution. But software handles the routine legwork: reading the record, notifying the right person, and moving the data to its next stop.

Here’s how it works, starting from the simplest option and working up.

Fulcrum workflows: automation that’s already there

Think of Fulcrum workflows like the “if this, then that” rules you might set up in your email. If an email arrives from a specific client, move it to a folder. If a message has the word “urgent,” flag it. You set the rule once, and it runs every time, and no one has to remember to do it.

Workflows in Fulcrum work the same way, but for records.

You decide: when a record matches certain conditions, what should happen? A few examples:

A SWPPP inspection comes in with status “Corrective Action Required” → automatically assign it to the project manager, who gets a notification that a record is waiting for them
A biological survey is marked complete → route it to QA review with a status change, so the next person knows it’s ready
Any new inspection record is created in a particular app → email the project lead automatically

You set these up inside Fulcrum, with no new account, no separate tool, no password to remember. Your GIS staff or a tech-comfortable team member can configure them in the app builder.

Fulcurm Workflow Automation Power Automate Flow

Zapier and Power Automate: connecting Fulcrum to everything else

Sometimes the action doesn’t just happen inside Fulcrum. It needs to happen somewhere else: in the tool where your team tracks tasks, the platform where your files live, or the messaging app where your crew communicates.

That’s what Zapier and Power Automate are for.

Both tools work as a bridge between Fulcrum and other software. When something happens in Fulcrum (submitting a record, changing a status, or receiving an inspection), it passes that information to another app to take action. No code is required. You build these connections in a visual, step-by-step interface that reads more like a form than a programming environment.

Zapier works with thousands of apps, including Slack, Asana, Monday.com, Google Sheets, Gmail, Salesforce, and most tools your team might use for tracking work or communicating.

Power Automate is Microsoft’s version of the same concept, and it’s the better choice if your firm runs on the Microsoft ecosystem with SharePoint for files, Teams for communication, Outlook for client updates. It also connects to ArcGIS Online through Esri’s connector, so if your GIS workflows are in ArcGIS, data can move between systems without an extra step.

Real-world automation scenarios for field teams

Here’s what this looks like in practice for an environmental team:

A corrective action that routes itself

Your inspector submits a SWPPP inspection and marks three BMPs as requiring corrective action. The moment that record hits Fulcrum, it automatically creates a task in your team’s tracking app. Tools like Asana or Monday.com will include the site name, issue, and inspector’s notes. The project manager sees it in their normal task list, not buried somewhere else they have to remember to check.

With Power Automate, the same trigger can post a message directly to a Teams channel, including a map link and a link to the Fulcrum record, so the right people know immediately, without anyone composing a message.

A rare species sighting that triggers a protocol change

Your biologist observes a special-status species and submits the record. Within a minute, the team lead gets a Slack or Teams message with the species, location, and a link to the record while the crew is still in the field. No one has to check a dashboard at the end of the day. The alert comes to the person who needs it.

A client who gets an update without you sending one

Someone marks a monitoring record complete. Automatically, an email goes to the project client contact with a link to their Shared View in Fulcrum Data Viewer. There they can see the new record on the map, with photos and field notes, without needing a Fulcrum login, a PDF attachment, or a follow-up email from you.

Inspection reports that file themselves

When Fulcrum generates a PDF report, Power Automate sends it to the correct SharePoint folder. SharePoint organizes, labels, and shares the report with your team and clients without manual uploads.

A compliance log that updates itself

Every new SWPPP or environmental inspection record created in Fulcrum adds a row to a spreadsheet including date, site, inspector, status, and any flagged items. The log is always current. No one has to open it on Friday afternoon and catch up.

Fulcrum Workflow Automation Screenshot Zapier Example — Zapier workflow

Live reporting: your data in the tools where decisions get made

Not every workflow problem is about triggering an action. Sometimes the goal is simpler: people need to see the data, and they shouldn’t have to ask you for it every time.

Fulcrum has a Query API allowing your IT staff or GIS team to connect reporting tools directly to Fulcrum and pull live data on demand. It works a bit like a window into your records: they can look through it whenever they need to, and what they see is always current, without anyone opening Fulcrum and exporting a spreadsheet.

Tools that connect this way include:

Power BI. Your project manager or client can open a Power BI report and see current inspection counts, status breakdowns, and coverage by site. Data refreshes automatically as your crew collects.
QGIS and ArcGIS Online. Your GIS team can connect a live map layer directly to Fulcrum. New field records appear on the map as they come in without a file import or “here’s this week’s shapefile” email.
Google Sheets. Paste a Fulcrum feed URL into a Google Sheet and it stays live-synced to your records. Your client opens the spreadsheet on Monday morning and it already reflects Friday’s collection.

If any of this sounds useful, your GIS staff or IT contact will know how to set it up. Getting it started is on the technical side, but the result is straightforward: the right people see current data without anyone being the middle step.

For your IT team or GIS staff: Webhooks and the REST API

If someone on your team is comfortable with APIs, or if you work with a consulting firm or IT partner that manages your data systems, Fulcrum’s Webhooks and REST API are worth knowing about.

A Webhook is like a doorbell. The moment a record event happens in Fulcrum, like a new record is submitted, an existing one is updated, it immediately rings a bell at whatever system you’ve pointed it at. Your developer can set up that receiving system to do anything with the notification: add a row to a database, trigger a custom report, push data to a client’s GIS server, update a record in another system.

The REST API offers a broader set of capabilities for developers. Through it, they can programmatically manage forms, handle attachments, create records, and generate reports. Code libraries in JavaScript, Python, and Ruby are available on GitHub.

This setup serves teams managing high-volume compliance programs or building custom dashboards that rely on near-real-time data. Even if you aren’t configuring the code yourself, this section gives your IT or GIS lead everything they need to get started.

Fulcrum Workflow Automation Power Automate Flow Screenshot 3 Webhook Circle

Taking the friction out of field handoffs

At the end of the day, field teams shouldn’t have to double as manual data couriers. Automating your handoffs keeps projects moving, cuts down on admin overhead, and ensures critical issues get flagged immediately. Start small with a single alert or report export, and let your data start moving itself.