Zapier Integration
Zapier lets you connect EventWorks to thousands of other apps through automated workflows called "Zaps". Using the EventWorks API, you can trigger actions in other tools when things happen in EventWorks, or create and update EventWorks records from other apps.
Getting There
Zapier connects to EventWorks through the API v2. You'll need an API token to authenticate. Go to your EventWorks account settings to generate an API token, then use it when configuring your Zapier connection.
Overview
With Zapier, you can:
- Trigger actions in other apps when events, accounts, contacts, or invoices are created or updated in EventWorks
- Create records in EventWorks from other apps (e.g. create an event when a form is submitted)
- Sync data between EventWorks and tools that don't have a direct integration
- Build custom workflows combining multiple apps and actions
Key Concepts
API Token Authentication
Zapier connects to EventWorks using an API token. This token authenticates all requests and determines which data you can access.
API v2 Endpoints
Zapier uses the EventWorks API v2, which provides full CRUD (create, read, update, delete) access to your core data. Each resource type has standard endpoints for listing, viewing, creating, updating, and deleting records.
Dynamic Field Discovery
The API includes a metadata endpoint that Zapier can use to automatically discover available fields for each resource type, including your custom attributes. This means your Zaps automatically reflect your customised EventWorks setup.
Available Resources
The following EventWorks resources are available through the API for use with Zapier:
| Resource | Operations | Description |
|---|---|---|
| Events | List, View, Create, Update, Delete | Your events with status, type, dates, and custom attributes |
| Accounts | List, View, Create, Update, Delete | Client and supplier accounts with contacts and types |
| Contacts | List, View, Create, Update, Delete | Contact records linked to accounts |
| Invoices | List, View, Create, Update, Delete | Sales and purchase invoices |
| Credit Notes | List, View, Create, Update, Delete | Credit note records |
| Purchase Orders | List, View, Create, Update, Delete | Purchase order records |
| Costs | List, View, Create, Update, Delete | Event cost line items with supplier and type info |
| Cost Groups | List, View, Create, Update, Delete | Groups of costs within an event |
| Cost Tabs | List, View, Create, Update, Delete | Cost sheet tabs |
| Notes | List, View, Create, Update, Delete | Notes attached to events, accounts, or contacts |
| Users | List, View | User records (read-only) |
Additional Endpoints
| Endpoint | Description |
|---|---|
| Me | Returns the authenticated user's details |
| Meta | Returns available fields for a resource type, including custom attributes — used by Zapier for dynamic field discovery |
How To...
Set Up a Zapier Connection
- In Zapier, search for the EventWorks app (or use a "Webhooks by Zapier" or "API Request" action if the native app isn't available).
- When prompted for authentication, enter:
/api/v2/) - API Token — Your EventWorks API token
- Test the connection to confirm it works.
Create a Zap with EventWorks
- In Zapier, create a new Zap.
- Choose a trigger — This can be from EventWorks (e.g. a new event is created) or from another app (e.g. a new form submission).
- Choose an action — This can be in EventWorks (e.g. create a new account) or in another app.
- Map fields — Connect the data between your trigger and action. Use the field names from the EventWorks API.
- Test and enable — Test your Zap with sample data, then turn it on.
Common Zap Examples
- New form submission → Create EventWorks event — When someone fills out a booking form, automatically create an event in EventWorks.
- New EventWorks event → Create Google Calendar entry — When a new event is created, add it to a shared Google Calendar.
- New EventWorks account → Add to CRM — When a new account is created, add the company to a CRM that doesn't have a direct integration.
- New EventWorks invoice → Send Slack notification — When an invoice is created, notify a Slack channel.
Working with Custom Attributes
The API v2 supports custom attributes for events, accounts, and contacts. When creating or updating records via Zapier, you can set custom attributes using the custom_{key} format:
- Use the Meta endpoint to discover which custom attributes are available and their types.
- Custom attributes support text, boolean, and date types.
Tips & Best Practices
Tip: Use the Meta endpoint to discover all available fields before building your Zaps. This ensures you're using the correct field names and know which relationships are available.
Tip: When matching related records (like assigning an account to an event), you can provide an object with either anidor aname— the API will match it automatically.
Tip: The API supports filtering, sorting, and search on list endpoints, which is useful for finding specific records in multi-step Zaps.
Frequently Asked Questions
Q: Is there a native EventWorks app on Zapier?EventWorks connects to Zapier through its REST API. You can use Zapier's Webhooks or API Request actions to connect, or check the Zapier app directory for a native EventWorks app.
Q: What authentication does the API use?The API uses token-based authentication. Include your API token in the request headers.
Q: Can I create events with custom attributes via Zapier?Yes. Custom attributes are supported on events, accounts, and contacts. Use the custom_{key} field name format when creating or updating records.
The API has standard rate limiting in place. For most use cases with Zapier, you won't encounter limits. If you're processing a high volume of requests, Zapier handles retry logic automatically.
Q: Can I delete records via the API?Yes. Events and notes use soft deletion (they're marked as deleted but not permanently removed). Other resources are permanently deleted.