# Rhythm Software Zapier Integration

Welcome to the Zapier integration for Rhythm Software! This guide covers supported services, available triggers, input behaviors, and tips for configuring dynamic output fields across tenants and modules.

## Authentication

This integration uses **OAuth2** for secure authentication. You'll authorize your Rhythm Software account when setting up your first Zap.

## Supported Services & Triggers

Each service below supports **3 standard triggers**:

- `Created`
- `Updated`
- `Deleted`


All triggers require:

- `tenant_id`: Your organization’s unique identifier
- `test_record_id`: An example record ID to load test data during Zap setup
- Optional: `additional_fields`: Select extra fields to include in your Zap output


### Career Center

- **Job Posting**: `job_postings_created`, `job_postings_changed`, `job_postings_deleted`


### Contacts & Organizations

- **Rolodex Contacts**: `rolodex_contacts_created`, `rolodex_contacts_changed`, `rolodex_contacts_deleted`
- **Rolodex Organizations**: `rolodex_organizations_created`, `rolodex_organizations_changed`, `rolodex_organizations_deleted`


### Membership & Committees

- **Memberships**: `memberships_created`, `memberships_changed`, `memberships_deleted`
- **Committee Memberships**: `committee_memberships_created`, `committee_memberships_changed`, `committee_memberships_deleted`


### Meetings & Shows

- **Events**: `events_created`, `events_changed`, `events_deleted`
- **Event Registrations**:
  - `event_registrations_created`, `event_registrations_changed`, `event_registrations_deleted`
  - **Extra Input Fields**:
    - `filter_field` (dropdown): Choose the field to filter registrations by (e.g., `event_id`)
    - `filter_value`: The value to match (e.g., `evt_123456`)


### Submissions & Reviews

- **Submissions**: `submissions_created`, `submissions_changed`, `submissions_deleted`


## Common Input Fields

All triggers support the following shared inputs:

| Field | Required | Description |
|  --- | --- | --- |
| `tenant_id` | Yes | Your Rhythm tenant identifier |
| `test_record_id` | Yes | Record ID used to preview data in setup |
| `additional_fields` | No | Optional fields to retrieve in the payload |
| `filter_field`, `filter_value` | No | Event Registrations only; used to filter results |


The `additional_fields` input lets you select custom fields exposed by the API. These vary per tenant and per service.

### Example: Selecting Additional Fields

During setup, users can select additional fields from a dropdown:


```json
[
  { "key": "first_name", "label": "First Name" },
  { "key": "last_name", "label": "Last Name" },
  { "key": "email_address", "label": "Email" }
]
```

These fields will be included in your Zap output if selected.

## Output Fields

By default, each trigger returns only the `id` field. If users opt into `additional_fields`, those are dynamically added during runtime.

Output fields are flattened—nested fields are converted to keys like `preferred_address__city`.

## Setup Considerations

When a new trigger is configured, Rhythm Software automatically provisions supporting infrastructure such as AWS EventBridge rules and webhooks. This process typically takes **5–10 minutes**.

During this time:

- Trigger test results may appear empty or delayed
- Live data may not flow immediately


This setup is only required once per trigger per tenant.

If data does not appear after this period, please verify:

- The `tenant_id` and `test_record_id` are correct
- Any selected `additional_fields` exist for the tenant
- Your Rhythm Software account has the appropriate permissions


## Additional Resources

- [Zapier Getting Started Guide](https://learn.zapier.com/path/zapier-basics-from-a-to-zap)
- [Rhythm AMS Zapier Integration](https://zapier.com/apps/rhythm-ams/integrations)