- Home
- Resources
- Integrations
- Action Network
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
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.
How do you connect Action Network to n8n?
- 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.
- 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.
- 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.
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.
| Resource | Create | Get | Get Many | Update | Add | Remove |
|---|---|---|---|---|---|---|
| Attendance | ✓ | ✓ | ✓ | |||
| Event | ✓ | ✓ | ✓ | |||
| Person | ✓ | ✓ | ✓ | ✓ | ||
| Person Tag | ✓ | ✓ | ||||
| Petition | ✓ | ✓ | ✓ | ✓ | ||
| Signature | ✓ | ✓ | ✓ | ✓ | ||
| Tag | ✓ | ✓ | ✓ |
Operations index
Attendance
3 operationsCreate an attendance
attendance.createWhat 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.
Get an attendance
attendance.getWhat 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.
Get many attendances
attendance.getAllWhat 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.
Event
3 operationsCreate an event
event.createWhat 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.
Get an event
event.getWhat 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.
Get many events
event.getAllWhat 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.
Person
4 operationsCreate a person
person.createWhat 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.
Get a person
person.getWhat 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.
Get many people
person.getAllWhat 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.
Update a person
person.updateWhat 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.
Person Tag
2 operationsAdd a person tag
personTag.addWhat 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.
Remove a person tag
personTag.removeWhat 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.
Petition
4 operationsCreate a petition
petition.createWhat 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.
Get a petition
petition.getWhat 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.
Get many petitions
petition.getAllWhat 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.
Update a petition
petition.updateWhat 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.
Signature
4 operationsCreate a signature
signature.createWhat 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.
Get a signature
signature.getWhat 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.
Get many signatures
signature.getAllWhat 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.
Update a signature
signature.updateWhat 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.
Tag
3 operationsCreate a tag
tag.createWhat 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.
Get a tag
tag.getWhat 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.
Get many tags
tag.getAllWhat 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.
Need help automating Action Network with n8n?
A person reads every message.

