Clone an event with registrants
Clone an event with registrants
Apps used in template
About
This template is expected to be run on demand, when you want to make a full copy of existing event including all event registrants.
Due to system limitations it does not copy guests.
Trusted by thousands of fast-scaling organizations around the globe
Similar templates for inspiration
Looking to get more out of your apps? With Make, you can visually integrate any app into any workflow to save time and resources - no coding required. Try any of these templates in just a few clicks.
Create your own workflow
Create custom workflows by choosing triggers, actions, and searches. A trigger is an event that launches the workflow, an action is the event.
Mark event attendee as checked-in, or remove check-in flag.
Clone existing event.
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.
This module creates new contact record in your Wild Apricot account.
Create new event in your organization account.
Create new event registration (register existing contact)
Create event registration type.
Create new invoice
FAQ
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.
How it works
Traditional no-code iPaaS platforms are linear and non-intuitive. Make allows you to visually create, build, and automate without limits.










