Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Wild Apricot
Anthropic Claude

Connect Wild Apricot and Anthropic Claude

Explore ready-made Wild Apricot and Anthropic Claude templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Wild Apricot with Anthropic Claude and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Wild Apricot
Trigger: Contact created or modified
Anthropic Claude
Action: Select an action
1. Select a trigger

  • Fires almost immediately after contact was created or modified. This is a recommended replacement for 'Contact modified (obsolete)' module.

  • WARNING: This trigger is obsolete, we recommend to use "Contact modified - instant" module. This trigger fires when a contact data was modified. You could select a date, from which to monitor contact modifications. If you choose some date in the past, you will get all contacts modified since that date.

  • Fires when an event was either created, updated or deleted.

  • Fires when event registration is created, updated, canceled or deleted. Also fires on RSVP response.

  • Warning: this module is obsolete. Use "Invoice created or modified" instead. This trigger fires when a new invoice is created in your Wild Apricot account

  • Fires when invoice is created, modified, voided or deleted.

  • This trigger fires when a new audit log item created. Records does not contain detailed information about related documents. If you need more details, please use 'Get audit log item details' module.

  • Fires when payment is created, updated, canceled or deleted.

2. Select an action

  • Creates a memory in a memory store.

  • Creates a memory store.

  • Creates a new prompt based on a structured list of input messages.

  • Creates a session.

  • Creates a new Skill.

  • Creates a new Skill version.

  • Deletes an existing file.

  • Deletes an existing Skill.

  • Deletes an existing Skill version.

  • Downloads a Claude-generated file.

  • Retrieves an existing file's metadata.

  • Retrieves an existing Skill.

  • Retrieves an existing Skill version.

  • Performs an arbitrary authorized API call.

  • Sends events to a session.

  • Generates text responses from prompts without requiring an account or connection.

  • Uploads a new file.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Wild Apricot and Anthropic Claude.

Check-in event attendee
Mark event attendee as checked-in, or remove check-in flag.
Action
Clone event
Clone existing event.
Action
Contact created or modified
Fires almost immediately after contact was created or modified. This is a recommended replacement for 'Contact modified (obsolete)' module.
Trigger
Contact modified (obsolete)
WARNING: This trigger is obsolete, we recommend to use "Contact modified - instant" module. This trigger fires when a contact data was modified. You could select a date, from which to monitor contact modifications. If you choose some date in the past, you will get all contacts modified since that date.
Trigger
Create a memory
Creates a memory in a memory store.
Action
Create a memory store
Creates a memory store.
Action
Create a Prompt
Creates a new prompt based on a structured list of input messages.
Action
Create a session
Creates a session.
Action
Create a Skill
Creates a new Skill.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.