SoftEXIT Studio Zapier Help

Complete help for connecting SoftEXIT Studio to Zapier, using instant triggers and record actions, mapping Studio fields, searching records, and troubleshooting your connection.

Back to Studio Help

Connect to Zapier

Generate your SoftEXIT API key and add your Studio connection in Zapier.

Go to Connection Help

Triggers

Use New Record, Updated Record, and Deleted Record to start Zaps instantly.

Go to Triggers

Actions

Create, update, retrieve, search, and delete SoftEXIT Studio records from a Zap.

Go to Actions

Fields & Troubleshooting

Understand supported field types, record IDs, lookups, users, paging, and common issues.

Go to Field Help

Before You Begin

The SoftEXIT Studio Zapier integration is available to organizations with the Professional plan or higher. You also need permission in SoftEXIT Studio to use the integration and access the Solution and Tables you plan to use.

Zapier connects to SoftEXIT Studio using an API key. Treat the API key like a password: do not post it publicly, include it in screenshots, or share it with people who should not have access to your organization.

Connect SoftEXIT Studio to Zapier

To connect Zapier to SoftEXIT Studio:

  1. Sign in to SoftEXIT Studio.
  2. Open Integrations.
  3. Open Zapier.
  4. Open Organization and then Credentials.
  5. Generate or copy your Zapier API Key.
  6. In Zapier, add a new SoftEXIT Studio connection.
  7. Paste the API key into the API Key field.
  8. Continue so Zapier can verify the connection.

When the connection succeeds, Zapier identifies the connection using your SoftEXIT organization name, making it easier to distinguish multiple SoftEXIT connections.

If Authentication Fails

  • Make sure you copied the complete API key and did not include extra spaces.
  • Confirm the API key is still active in SoftEXIT Studio.
  • Confirm your organization has access to the Zapier integration.
  • If the key was regenerated or replaced, reconnect the SoftEXIT Studio account in Zapier using the new key.

Create a Zap with SoftEXIT Studio

In Zapier, create a new Zap and choose SoftEXIT Studio as either the trigger app or an action app. Select your SoftEXIT connection, then choose the Solution and Table you want the Zap to use.

SoftEXIT presents customer-friendly Solution, Table, User, PickList, and supported Lookup selections wherever possible. You normally do not need to know internal SoftEXIT database IDs.

Instant Triggers

SoftEXIT Studio uses instant REST Hook triggers. Once the Zap is turned on, SoftEXIT sends the event to Zapier when the matching record event occurs. Zapier does not need to repeatedly poll SoftEXIT for changes.

New Record

Starts a Zap when a new record is created in the selected Studio Table. Choose the Solution and Table, test the trigger to load sample data, then turn the Zap on. Create a new Studio record to test the live trigger.

Updated Record

Starts a Zap when an existing record is updated in the selected Table. After the Zap is active, edit and save a record in Studio to test the live trigger.

Deleted Record

Starts a Zap when a record is deleted from the selected Table. The trigger includes the deleted record’s permanent record ID and the supported record values captured before deletion.

Testing an Instant Trigger

  1. Select the SoftEXIT trigger in Zapier.
  2. Select the Solution and Table.
  3. Use Test trigger to load sample data.
  4. Finish configuring the Zap and turn it on.
  5. Create, update, or delete a record in Studio, depending on the trigger.
  6. Check Zapier’s run history to confirm the event arrived.

Record Actions

Create Record

Creates a record in the selected SoftEXIT Studio Table. After you select the Solution and Table, Zapier loads the supported Studio fields dynamically. You can enter values directly or map values from earlier Zap steps.

You can also assign the new record to an active licensed SoftEXIT user using Record Owner, or choose Unassigned.

Update Record

Updates an existing Studio record using its Record ID. In most Zaps, map the Record ID from a previous SoftEXIT trigger, Find Record, Find Records, Create Record, or Get Record step.

Only fields you provide are updated. Record Owner can also be changed or cleared by choosing Unassigned.

Get Record

Retrieves one Studio record by its permanent Record ID. This is useful when another Zap step already knows the SoftEXIT record ID and you need the current record values.

Find Record

Searches a supported text field for an exact match and returns the first matching record. Use this when you expect a single match.

Find Records

Searches a supported text field and returns multiple records. You can choose:

  • Exact Match — the complete field value must match.
  • Contains — the field must contain the search text.

Find Records returns up to 10 records per page. The response also includes Page, Page Size, Count, Has More, and Next Page so you can request additional pages when needed.

Delete Record

Deletes the Studio record identified by its permanent Record ID. Because deletion is permanent, make sure the Record ID is coming from the correct prior step before enabling the Zap.

Record IDs and Permanent IDs

Zapier uses SoftEXIT’s permanent record UUID as the record ID. These IDs look similar to:

11f1c330-56d8-e804-9611-0201d4641378

You usually should not type these IDs manually. Instead, map the ID from an earlier SoftEXIT step. For example, a New Record trigger can supply the Record ID to a later Update Record, Get Record, or Delete Record action.

Zapier may warn during integration validation that Record ID fields do not use a dropdown. This is intentional: record tables can be large, and mapping the ID from a prior step is more scalable than loading every record into a dropdown.

Supported Studio Field Types

SoftEXIT Studio converts supported field types into Zapier-friendly inputs and outputs.

  • Text and Indexed Text — text values.
  • Multiline Text — multiline text values.
  • PickList — customer-friendly choices.
  • Multi-select PickList — multiple selected values.
  • Integer — whole numbers.
  • Decimal — numeric decimal values.
  • Date — stored as YYYY-MM-DD.
  • Date & Time — date and time values.
  • Boolean — true/false.
  • Percentage — stored as a decimal; for example, 0.75 represents 75%.
  • Currency — numeric amount without a currency symbol.
  • Barcode — treated as text so leading zeros can be preserved.
  • Geolocation — latitude and longitude.
  • Rating — ratings from 1 through 5.
  • Lookup — friendly choices when the Lookup is not parent-filtered.
  • User / Account — active licensed SoftEXIT users.

Fields Not Currently Writable Through Zapier

Signature and Links fields are not currently exposed as writable Zapier fields. Auto Number and Formula fields are also not writable because Studio manages those values automatically.

Protected Fields

Protected Studio fields are not exposed as writable integration fields. This preserves Studio’s protected-field security model.

Lookup and User Fields

Lookup Fields

Standard Lookup fields are shown as friendly Zapier choices using the Lookup’s configured display information. When the Lookup uses a record ID internally, SoftEXIT exposes the permanent record UUID to Zapier instead of an internal numeric ID.

Parent-filtered Lookups may not have enough parent-record context during Zap setup to show a dynamic list. Those fields may require you to map the value from an earlier step.

User Fields

User and Account fields expose active licensed SoftEXIT users. Zapier uses the user’s permanent UUID rather than the internal SoftEXIT account number.

Searching and Paging

Find Record is intended for a single exact-match lookup and returns the first match.

Find Records is intended when multiple records may match. Choose Exact Match or Contains, then start with Page 1. Each page returns up to 10 records.

If Has More is true, use Next Page to request the next group of records.

In Zapier’s test-data display, fields returned inside the records list may appear with a Records prefix, such as Records Field Text. This is normal and indicates that the value belongs to an item inside the returned records list.

Security and Access

  • SoftEXIT authenticates Zapier requests using a Bearer API key.
  • API keys should be treated as secrets.
  • Zapier access is scoped through the authenticated SoftEXIT organization and the Solutions and Tables available to that integration.
  • Protected fields remain protected from integration writes.
  • When an instant-trigger subscription is removed or becomes invalid, SoftEXIT can deactivate the stale subscription.
  • Temporary webhook delivery failures are retried automatically before the delivery is marked failed.

Troubleshooting

My Solution or Table Does Not Appear

Confirm that your SoftEXIT account and Zapier integration have access to the Solution and Table. Reopen the Zap step after changing Studio permissions so Zapier can refresh the dynamic choices.

My Trigger Test Shows an Older Record

The Test Trigger step loads sample data so you can configure the Zap. To test the actual instant webhook, turn the Zap on and then create, update, or delete a record in Studio.

My Lookup Value Does Not Appear

Standard Lookups can load friendly choices. Parent-filtered Lookups may require a mapped value because Zapier does not necessarily know the parent record while the Zap is being configured.

My Search Returns Only One Record

Use Find Records instead of Find Record when more than one match is expected. Find Records supports Exact Match, Contains, and paging.

Authentication Stopped Working

Verify that the API key is still active. If the key was regenerated, reconnect the SoftEXIT Studio account in Zapier with the current API key.

SoftEXIT Studio + Zapier

Use SoftEXIT Studio as a flexible business data platform while Zapier connects it to the other applications your organization uses.

Back to Studio Help