Complete help for connecting SoftEXIT Studio to Zapier, using instant triggers and record actions, mapping Studio fields, searching records, and troubleshooting your connection.
Generate your SoftEXIT API key and add your Studio connection in Zapier.
Create, update, retrieve, search, and delete SoftEXIT Studio records from a Zap.
Understand supported field types, record IDs, lookups, users, paging, and common issues.
Technical endpoint documentation for Zapier’s review team and developers.
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.
To connect Zapier to SoftEXIT Studio:
When the connection succeeds, Zapier identifies the connection using your SoftEXIT organization name, making it easier to distinguish multiple SoftEXIT connections.
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.
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.
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.
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.
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.
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.
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.
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.
Searches a supported text field for an exact match and returns the first matching record. Use this when you expect a single match.
Searches a supported text field and returns multiple records. You can choose:
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.
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.
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.
SoftEXIT Studio converts supported field types into Zapier-friendly inputs and outputs.
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 Studio fields are not exposed as writable integration fields. This preserves Studio’s protected-field security model.
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 and Account fields expose active licensed SoftEXIT users. Zapier uses the user’s permanent UUID rather than the internal SoftEXIT account number.
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.
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.
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.
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.
Use Find Records instead of Find Record when more than one match is expected. Find Records supports Exact Match, Contains, and paging.
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.
Use SoftEXIT Studio as a flexible business data platform while Zapier connects it to the other applications your organization uses.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website and improve the visitor experience.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.