Connect Sydnee to Zapier
Connect an API key and use the Sydnee triggers and actions that are live in Zapier.
Zapier connects Sydnee to other apps without custom code. A Zap is an automated workflow. A trigger starts it. An action is the step Zapier asks Sydnee to take.
Connect Zapier with a Sydnee API key.
API keys are included with paid plans. To connect during the free trial, select a plan and add a payment method first.
You also need a Zapier account and permission to connect the other app used in the Zap.
Connect Sydnee to Zapier
- Ask a workspace owner or admin to create a key in Company Settings → API Keys.
- Give the key a label such as
Zapier. - Open the Sydnee app in Zapier.
- Add a Sydnee connection.
- Paste the API key when Zapier asks for it.
- Let Zapier test the connection.
- Build and test the Zap with non-sensitive sample data.
Use a key only for Zapier. If you delete it later, your other API tools can keep their own keys.
Paste the key only into Zapier's connection field. Do not send it in a support or chat message, and do not include it in screenshots or sample data.
Choose a trigger or action
Choose from the triggers and actions below, or browse the Sydnee app in Zapier.
Current Sydnee triggers
Choose the event that should start the Zap:
- Account Created starts when a client account is created.
- Account Status Changed starts when an account is archived, restored, or deleted.
- Portal User Changed starts when a portal user is added, removed, or accesses an account.
- Request Status Changed starts when a Request is published, unpublished, completed, reopened, archived, unarchived, or deleted.
- Request Field Completed starts when a portal user completes a field in a Request.
- Task Changed starts when a task is created, updated, completed, reopened, archived, unarchived, or deleted. Completion and reopening wait 45 seconds so an Undo can finish first.
- Task Comment Added starts when a comment is added to a task.
- Task Attachment Added starts when an attachment is added to a task.
- File Comment Added starts when a top-level comment or reply is added to a file.
- File Uploaded starts when a file is uploaded, receives a new version, is renamed, moved, or deleted.
- Deliverable Changed starts when a Deliverable is published, viewed, or removed.
- Service Request Submitted starts when a portal user requests a service that is not active for the account.
- Service Ticket Created starts when a portal user creates a ticket for an active service.
- Task Board Status Update Posted starts when a status update is posted to a task board.
- Portal User Sent Live Chat Message starts when a portal user sends text, an attachment, or a location in Live Chat.
Every trigger except Account Created includes an optional Account field. Choose an account to receive events only for that account, or leave it blank to receive events from every account. Account Created does not have this filter because the account does not exist before the event.
All triggers have an optional Include Authored Text field. Turn it on only when the destination app should receive that content. Depending on the event, it can send:
- Resource names or titles.
- Request field labels and answers.
- Task and file comment previews.
- Task Board updates and coming-next text.
- File-version change notes.
- Previews of Live Chat messages sent by clients.
Preview text is plain text, up to 280 characters. When the option is off, these fields are blank. Sensitive Request answers, signatures, and file contents are excluded.
Each trigger exposes the shared webhook fields, including Sydnee App URL. Use that authenticated link when a person should open the affected item in Sydnee. Resource URL remains the machine-oriented Public API URL. Deleted or removed resources can leave one or both fields blank when no useful destination remains. File-version events also expose File Version Number whether authored text is on or off.
Portal User Changed and Portal User Sent Live Chat Message also include Include User Email. When it is on, the event can include the portal user's email address. When it is off, the email field is blank. Turn these fields on only when the destination app should receive that content.
Trigger timing can vary. Use Zapier's test and run history to confirm when the Zap runs.
Older Zaps may still show legacy triggers. Sydnee keeps them for existing Zaps, but they are hidden when you build a new Zap:
- Replace New Account with Account Created in a new Zap.
- Replace New Portal User with Portal User Changed in a new Zap.
- Replace Comment Added with Task Comment Added or File Comment Added, based on where the comment is added.
- Replace Service Requested with Service Request Submitted. Use Service Ticket Created when the client creates a ticket for an active service.
- New Request Template and New Task Template remain available only to existing legacy Zaps. The current trigger list does not include a replacement for template creation.
Current Sydnee actions
Choose what Zapier should ask Sydnee to do:
- Create Account creates a client account.
- Add Portal User to Account adds a portal user to the selected account.
- Remove Portal User From Account removes a portal user's access to the selected account.
- Add Task Template to Account adds a task template to the selected account.
- Send Request to Portal User sends a Request from a template to the selected portal user.
- Archive Account archives the selected account.
Changes made by a Zapier action appear as System in Sydnee. To receive those changes through webhooks, set the endpoint to All people. See webhook events and payloads for the event fields.
Zapier can load current accounts, portal users, Request templates, and task templates into supported setup fields. The Account picker shows the account name and slug, then stores the public Sydnee account ID for the action.
Each action asks for System Run ID and System Step ID. Open each field in Zapier and select the system value with the same name. Do not enter one fixed value for every run. These values let a retry return the first result instead of repeating the action.
If the action runs in a loop, map a durable ID from the source item to Loop Item ID. The same item should keep the same ID during a retry, and different items should have different IDs. Use a record ID or another fixed source identifier, not an editable name or the item's position in the loop. Leave Loop Item ID blank outside a loop.
Older Zaps may show action names ending in (Legacy) or the older Remove User From Account name. Keep a working legacy step in an existing Zap. For a new Zap, choose the action without (Legacy). Remove Portal User From Account applies only to portal users.
The public API and Zapier support different sets of steps. Check the live Zapier list before you build a workflow.
Test a safe workflow
- Choose a test account that does not hold private client data.
- Check every account, user, and template field.
- Run the test once.
- Confirm the result in Sydnee.
- Turn the Zap on only after the result is correct.
Check access changes carefully: Archive Account and Remove Portal User From Account change access. Test both with a safe account before you turn the Zap on.