Resources · n8n integration

Action Network n8n integrationAutomate Action Network with n8n.

Your supporter list lives in Action Network, the rest of the campaign lives everywhere else. The Action Network n8n integration covers 7 resources with 23 operations, for people, tags, events, petitions and signatures. No trigger node ships with it, so a schedule starts the run.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Action Network n8n integration give you?

The Action Network n8n integration lets a workflow read and write your organizing data without anyone exporting a CSV. The node ships with n8n and exposes 23 operations spread over 7 resources, so one run can create a supporter, tag them, register them for a meeting, open a petition and log a signature. Everything happens through an API key credential you set up once.

Start with the sign-up path. A form on your own site posts into n8n, the workflow calls Create a person with the email address and the name, then Add a person tag so the new supporter lands in the right segment straight away. The same run can drop a row into Google Sheets for the volunteers who still work from a shared file.

Second path: events. A Schedule Trigger wakes the workflow every morning, Get many events returns what is on the calendar, and Get many attendances pulls the RSVP list for each one. Post the counts into Slack and the field team sees which meeting needs another push before lunch.

Third path: petitions. Get many signatures on a petition feeds a loop that thanks each signer through Gmail. The signature comment field travels with the record, so the thank-you can quote what the person wrote, and the same run can look up the petition itself with Get a petition to pull its current title into the message.

When a call you need sits outside these 23 operations, the HTTP Request node hits any Action Network API endpoint directly and reuses the same credential through predefined authentication. You keep one key, one place to rotate it, and no second connection to maintain.

Two things to plan for. Reads that can grow long, Get many people or Get many signatures, are paged: leave Return All off and Limit decides how many records come back, switch it on and n8n walks every page. And every required field is a hard stop, an empty Person ID fails the node rather than guessing. If your team is new to that logic, the n8n training covers it before you wire a live list.

Connect

How do you connect Action Network to n8n?

  1. 01

    Ask Action Network for API access

    API keys are not on by default. If your organization already pays for Action Network, contact them and request partner access, which includes API key access. If you are a developer, request a developer account instead, and the key access comes with it once the request is granted. Nothing in n8n works until one of those two requests goes through, so start here rather than in the credential screen.

  2. 02

    Generate the key on the right list

    Log in to Action Network, open the Start Organizing menu, then Details and API & Sync. Pick the list you want the key to cover, generate an API key for that list, and copy it. The page is the only place the value comes from, so keep the tab open while you finish the setup in n8n.

  3. 03

    Create the credential in n8n

    In n8n, open the Credentials menu, create an Action Network credential and paste the value into the API Key field. A credential is stored once and reused everywhere, so every Action Network node in every workflow picks it from a dropdown instead of holding its own copy of the key. Self-hosted or n8n Cloud, the steps are identical.

Actions

What the Action Network node can do, operation by operation

The Action Network node exposes 23 operations across 7 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateAddRemove
Attendance✓✓✓
Event✓✓✓
Person✓✓✓✓
Person Tag✓✓
Petition✓✓✓✓
Signature✓✓✓✓
Tag✓✓✓

Attendance

3 operations
01

Create an attendance

attendance.create

What you see in n8n

Notes & use cases

Files one person as attending one event, the same record Action Network writes when someone RSVPs on the platform.

Key parameters

  • Person ID: the Action Network identifier of the person attending, often {{ $json.id }} passed along from a Create a person step earlier in the run.
  • Event ID: the identifier of the event the RSVP belongs to.
  • Simplify: on, n8n hands back a trimmed version of the response rather than the raw payload.
Use cases
a volunteer signs up through your own site and the RSVP lands against the right canvass, with no one retyping a name into the platform.
02

Get an attendance

attendance.get

What you see in n8n

Notes & use cases

Pulls back one RSVP so a workflow can check it before acting on it.

Key parameters

  • Event ID: the event whose attendance you want to read, because an RSVP only exists inside an event.
  • Attendance ID: the identifier of that specific RSVP.
Use cases
before a reminder goes out, the workflow reads the RSVP again and confirms the person is still on the list for Saturday's door knock, which keeps the reminder from reaching someone who already dropped out.
03

Get many attendances

attendance.getAll

What you see in n8n

Notes & use cases

Lists the RSVPs recorded for a single event, page after page.

Key parameters

  • Event ID: the event whose attendance list you are reading.
  • Return All: on, n8n follows every page of the list; off, Limit sets how many RSVPs come back.
  • Limit: the ceiling applied when Return All stays off, handy while you test on a busy event.
Use cases
build tomorrow's phone bank sheet, one line per attendee, refreshed each night.

Event

3 operations
04

Create an event

event.create

What you see in n8n

Notes & use cases

Publishes a new event in Action Network and returns the created record, ready for RSVPs.

Key parameters

  • Origin System: free text naming where the event came from, useful when several tools feed the same calendar.
  • Title: the public title of the event.
  • Additional Fields: 8 optional fields, among them Start Date, End Date, Location, Description and Instructions, the last two accepting HTML.
Use cases
your meeting planner fixes a date, n8n mirrors it into Action Network so activists can sign up in one click.
05

Get an event

event.get

What you see in n8n

Notes & use cases

Reads one event and returns its record as Action Network stores it.

Key parameters

  • Event ID: the identifier of the event to retrieve, commonly {{ $json.eventId }} when the id travels from a previous node.
  • Simplify: keeps the output to the readable fields, which makes the mapping in the next node much shorter.
Use cases
a Slack command asks for the details of one town hall, and the workflow answers with the title and the schedule pulled live from the platform.
06

Get many events

event.getAll

What you see in n8n

Notes & use cases

Walks the event calendar and returns the events it finds. No required field, so it runs as a plain inventory step.

Key parameters

  • Return All: on, every page of the calendar comes back; off, the run stops at Limit.
  • Limit: the maximum number of events to return in one execution.
Use cases
a nightly run copies the full calendar into a shared spreadsheet so the comms team schedules posts a week ahead.

Person

4 operations
07

Create a person

person.create

What you see in n8n

Notes & use cases

Adds a supporter to Action Network. Nothing is strictly required, which means the node can create a bare record and let a later step fill it in.

Key parameters

  • Email Address: the collection holding the person's email addresses, the field most workflows populate first.
  • Additional Fields: Given Name, Family Name, Status for the subscription state, Language Spoken, Phone Number and Postal Addresses.
Use cases
a petition hosted on your own site turns each new signer into a supporter record within the same run.
08

Get a person

person.get

What you see in n8n

Notes & use cases

Looks up a single supporter and returns what Action Network holds on them.

Key parameters

  • Person ID: the identifier of the supporter to read, not their email address.
  • Simplify: on, the response drops to its readable form, which is usually enough to feed a message template.
Use cases
an organizer pastes an id into a form, the workflow returns the person's current details, and the caller knows who is on the other end before dialling.
09

Get many people

person.getAll

What you see in n8n

Notes & use cases

Returns supporters from the list the API key covers, with no required field to fill in.

Key parameters

  • Return All: on for a complete export, since the node then chains the pages of the API on its own.
  • Limit: the cap that applies while Return All stays off, which is the safe setting for a first test run.
  • Simplify: trims each record to its main fields.
Use cases
a weekly export feeds the deduplication check the data team runs before a mailing.
10

Update a person

person.update

What you see in n8n

Notes & use cases

Edits an existing supporter record instead of creating a second one for the same human.

Key parameters

  • Person ID: the record to modify, the only required value here.
  • Update Fields: 5 fields you can change, Given Name, Family Name, Language Spoken, Phone Number and Postal Addresses.
Use cases
someone corrects a spelling or a phone number on a landing page, and the correction reaches the organizing list the same minute instead of a monthly cleanup.

Person Tag

2 operations
11

Add a person tag

personTag.add

What you see in n8n

Notes & use cases

Attaches an existing tag to a supporter, which is how segments get built in Action Network.

Key parameters

  • Tag Name or ID: pick the tag from the dropdown n8n loads from your account, or pass an id through an expression when the tag is chosen at runtime.
  • Person ID: the supporter receiving the tag.
Use cases
everyone who attended a training gets tagged the evening of the session, so the next invitation only goes to people who already came once.
12

Remove a person tag

personTag.remove

What you see in n8n

Notes & use cases

Detaches a tag from a supporter. The operation works on the tagging, the link between the person and the tag, not on the person.

Key parameters

  • Tag Name or ID: the tag whose tagging you are deleting, from the list or through an expression.
  • Tagging Name or ID: the specific tagging to remove, chosen the same way.
Use cases
a supporter asks to leave a local group, and the workflow lifts the group tag without touching the rest of their profile.

Petition

4 operations
13

Create a petition

petition.create

What you see in n8n

Notes & use cases

Opens a new petition in Action Network and returns it, ready to collect signatures.

Key parameters

  • Origin System: where the petition came from, which keeps campaigns traceable when several teams publish.
  • Title: the public title shown to signers.
  • Additional Fields: Petition Text for the letter to the target, Targets as comma separated names, plus Browser URL, Featured Image URL and an internal Name.
Use cases
a local group files a petition from a shared form and the campaign page exists before the meeting ends.
14

Get a petition

petition.get

What you see in n8n

Notes & use cases

Retrieves one petition and its stored content.

Key parameters

  • Petition ID: the identifier of the petition to read, which every signature operation also needs.
  • Simplify: returns the readable version of the petition instead of the raw payload.
Use cases
a dashboard page pulls the current title and target list of a campaign before rendering it, so the copy shown to visitors always matches what the platform holds.
15

Get many petitions

petition.getAll

What you see in n8n

Notes & use cases

Enumerates the petitions available to the key, with nothing required to start.

Key parameters

  • Return All: on, the node chains the pages until the list is complete.
  • Limit: how many petitions come back when Return All stays off.
  • Simplify: shortens each petition to its main fields, which keeps a long list readable in the execution view.
Use cases
a monthly review lists every open campaign so the coordination team can close the ones that stalled.
16

Update a petition

petition.update

What you see in n8n

Notes & use cases

Rewrites part of an existing petition without republishing it.

Key parameters

  • Petition ID: the petition to modify.
  • Update Fields: 5 fields, including Petition Text, Targets, Browser URL, Featured Image URL and the internal Name.
Use cases
a council member changes portfolio, the workflow updates Targets on every petition that named them, and the letter keeps going to the right desk.

Signature

4 operations
17

Create a signature

signature.create

What you see in n8n

Notes & use cases

Records a supporter's signature on a petition, linking a person to a campaign.

Key parameters

  • Petition ID: the petition being signed.
  • Person ID: the supporter signing it, usually created a step earlier in the same run.
  • Comments: an optional message the person leaves with the signature.
Use cases
a signature collected on paper at a market stall gets typed once into a form, and the workflow creates the person then the signature in one pass.
18

Get a signature

signature.get

What you see in n8n

Notes & use cases

Reads back a single signature, including what the signer wrote with it.

Key parameters

  • Petition ID: the petition the signature belongs to.
  • Signature ID: the identifier of the signature itself.
Use cases
a moderator flags a comment for review, and the workflow fetches that exact signature so a human reads the original text before deciding whether it goes on the public wall.
19

Get many signatures

signature.getAll

What you see in n8n

Notes & use cases

Collects the signatures gathered on one petition.

Key parameters

  • Petition ID: the campaign whose signatures you are reading.
  • Return All: on for the full set, because a live campaign rarely fits in one page.
  • Limit: the number of signatures returned when Return All is off.
Use cases
a daily count feeds the progress bar on the campaign page, and the same run thanks the signers from the last batch.
20

Update a signature

signature.update

What you see in n8n

Notes & use cases

Amends a signature that already exists on a petition.

Key parameters

  • Petition ID: the petition holding the signature.
  • Signature ID: the signature to change.
  • Update Fields: one field, Comments, the message left with the signature.
Use cases
a signer emails back asking to shorten what they wrote, and the workflow rewrites the comment in place rather than deleting and recreating the whole signature.

Tag

3 operations
21

Create a tag

tag.create

What you see in n8n

Notes & use cases

Declares a new tag in Action Network so supporters can be sorted with it.

Key parameters

  • Name: the name of the tag, the only value the operation needs.
  • Simplify: on, the created tag comes back in short form, enough to grab its id for the next step.
Use cases
each new campaign opens with its own tag created automatically, which stops organizers from typing three slightly different spellings of the same label.
22

Get a tag

tag.get

What you see in n8n

Notes & use cases

Resolves one tag and returns its record.

Key parameters

  • Tag ID: the identifier of the tag to retrieve, not the label people see in the interface.
  • Simplify: returns the readable form of the tag instead of the raw response.
Use cases
a workflow that receives a tag id from another system checks the tag really exists before it starts attaching supporters to it, which turns a silent mistake into a clear stop.
23

Get many tags

tag.getAll

What you see in n8n

Notes & use cases

Sweeps the tags available in the account, with no required input.

Key parameters

  • Return All: on, every page of tags is returned; off, the node stops at Limit.
  • Limit: the maximum number of tags to bring back.
  • Simplify: keeps each tag to its main fields.
Use cases
an audit of the tag list spots the duplicates that pile up after a year of campaigns, before anyone builds a segment on the wrong one.
Need help

Need help automating Action Network with n8n?

A person reads every message.

FAQ

Action Network and n8n, the questions that come next

01Is the Action Network n8n integration free?
Yes on the n8n side. The Action Network node ships with n8n, so there is nothing to install and no extra cost, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves the same way in both. What Action Network itself costs is a separate matter this page does not cover. One point to plan for: API key access is not automatic, it has to be requested from Action Network before any of the 23 operations can run.
02What credentials do you need to connect Action Network to n8n?
An API key, and nothing else. The credential holds a single API Key field. To get the value, log in to Action Network, open the Start Organizing menu, then Details and API and Sync, select the list you want the key to cover, generate the key and copy it into n8n. Access has to be granted first: paying customers contact Action Network and request partner access, developers request a developer account. Once the credential exists in the Credentials menu, every workflow reuses it from a dropdown.
03What are the limits of the Action Network node in n8n?
The node covers 23 operations over 7 resources: attendance, event, person, person tag, petition, signature and tag. Anything you need beyond those operations goes through the HTTP Request node, which calls any Action Network API endpoint and reuses the same credential through predefined authentication. Two behaviours to keep in mind: reads that return lists are paged, so Return All decides between the full set and the ceiling fixed by Limit, and a required field left empty stops the node instead of running with a guess.
04Does Action Network trigger an n8n workflow in real time?
No, because Action Network has no trigger node in n8n. A workflow that touches Action Network starts from another source: a Schedule Trigger that runs at a fixed interval and reads the data with Get many people or Get many events, an n8n Webhook that a third party service calls, or the trigger of another tool already in your setup. That covers most needs, since the common pattern is a form or another platform pushing into n8n, which then writes to Action Network.
05n8n or Make for Action Network?
It depends on four things. Hosting first: n8n runs on your own server or on n8n Cloud, Make is hosted only. Data control follows from that, since a self-hosted instance keeps supporter data on infrastructure you own, which matters for an organization handling political affiliation. Cost model next: Make bills per operation, so a workflow reading long signature lists gets expensive as the campaign grows. Visual logic last: both build workflows on a canvas, and the choice there is a matter of habit more than capability.