Zapier

Sponsy integrates with Zapier, giving you a no-code way to connect Sponsy with tools like Slack, Google Sheets, Airtable, HubSpot, and thousands of other apps.

Use Zapier when you want activity in Sponsy to trigger a workflow outside Sponsy, or when another tool needs to create or update Sponsy records.

Getting started

1. Go to the Sponsy Zapier Integration page.
2. Choose a pre-made Zap or create your own.
3. Connect your Sponsy account.
4. Select the trigger, search, or action you want to use.
5. Map the Sponsy fields into the next app in your Zap.
6. Test the Zap and turn it on.

Zapier uses your Sponsy API connection to identify the workspace. You do not need to manually enter a workspace ID when using current triggers.

Available triggers

Sponsy supports triggers for common ad ops and sales events:

• New Slot: Runs when a slot is created.
• Slot Updated: Runs when a slot changes.
• Slot Deleted: Runs when a slot is deleted.
• New Publication: Runs when a publication is created.
• New Customer: Runs when a customer is created.
• New Deal: Runs when a deal is created.
• Deal Updated: Runs when a deal changes.
• Deal Stage Changed: Runs when a deal moves to a different stage.

Slot and deal update triggers include change data where available, so downstream tools can react to what changed instead of only receiving the current record.

Available searches and actions

Use searches when another Zap step needs to find an existing Sponsy record:

• Find a customer by name.
• Find slots by date, status, or customer.

Use actions when Zapier needs to write back into Sponsy:

• Create a customer.
• Update a customer.

Payload fields

Zapier payloads include the fields most teams need for routing, reporting, and CRM automation.

Customer payloads can include:

• Customer ID, name, website, customer type, internal customer URL, portal URL, created date, and updated date.
• Primary contact details.
• Customer custom fields, including custom field slug, label, value, and file references when applicable.

Slot payloads can include:

• Publication and placement details.
• Customer and agency customer details when present.
• Slot status, dates, due date, price, metrics, link, custom field values, content update date, created-by, and last-modified-by fields.

Deal payloads can include:

• Deal ID, name, status, customer, agency, sales reps, custom fields, totals, external ID, timestamps, deal link, and change data.

Agency customer fields are included on slot and deal payloads when an agency is associated with the record.

Example Zaps

• Send a Slack message when a slot status changes.
• Add new Sponsy customers to a CRM or spreadsheet.
• Create a task when a deal moves into a production stage.
• Send a finance notification when a deal is created or updated.
• Push campaign details into Airtable when a new slot is booked.

Troubleshooting

If a Zap does not trigger, confirm that the Sponsy API connection is still active and that the event happened in the same workspace connected to Zapier.

If expected fields are missing, refresh the Zap sample data. Zapier field lists can lag behind recent Sponsy payload changes until the step is retested.

For Zapier platform help, see Zapier’s help docs. For Sponsy-specific issues, contact support.