Zapier email automation with fourteen shared inbox triggers and five actions
Zapier connects Sektra to the other tools a team uses, so an event in the shared inbox can start work elsewhere and a step in a Zap can act on the inbox. Sektra gives Zapier fourteen triggers, from a new conversation to a service level at risk, and five actions that write back to the inbox. It is meant for operations and support leads who want email automation without asking a developer to build it. Each trigger reaches Zapier as the event happens, so a Zap does not wait for a scheduled check.
What Sektra does with Zapier
The fourteen Zapier triggers
A Zap can start when a conversation is created, assigned, closed or reopened, when a message arrives or a reply is sent, and when a note or a tag is added. Two contact triggers follow the shared address book, and two service level triggers fire when a conversation is at risk of missing its target and when it misses. The last two cover website chat: a visitor starting a chat, and a chat waiting for a person.
The five Zapier actions
Send New Email starts a conversation by sending a message from an inbox you choose. Add Note and Add Tag write to an existing conversation, Assign Conversation gives it to a teammate or clears the owner, and Create Contact adds a person to the shared address book. Each action runs with the permissions of the person whose key Zapier uses and behaves as it would in the app.
What each trigger sends to Zapier
Every conversation trigger passes the subject, a short excerpt, the inbox, status, tags, participants and owner, with a link that opens the conversation in Sektra. Message triggers add who sent the message, who received it and when. A conversation trigger can be limited to one inbox or left open to every inbox.
How Zapier connects to Sektra
Zapier connects with a key that a teammate who can manage integrations creates in Sektra's settings with read and write access. The key is shown once, is pasted into Zapier when it asks for the Sektra account, and can be revoked in Sektra at any time. Actions then run as the person who created the key, in the inboxes that person can use.
Delivery log and retries
Each trigger a Zap subscribes to is listed in Sektra's settings with a log of what was sent to it. A delivery that Zapier does not accept is tried again five times over about fifteen hours, and a delivered or failed entry in the log can be sent again by hand. Turning a Zap off in Zapier removes its trigger from Sektra.
Common questions
Setup, permissions and what Sektra reads from Zapier, with a contact link for anything not covered here.
Does Sektra work with Zapier?
Yes. Sektra gives Zapier fourteen instant triggers and five actions, enough to pass inbox events to another tool and to send email, add notes and tags, assign conversations and create contacts from a Zap. The connection uses a key created in Sektra's settings.
What email automation can we build with Zapier and Sektra?
A Zap can create a task or a CRM record when a tag is added to a conversation, or pass a service level warning to another tool. In the other direction, a form submitted elsewhere can send an email from a shared inbox. Work that stays inside the inbox, such as assigning, tagging or sending a template reply, needs no Zap because Sektra's own rules handle it.
Can a Zap reply to a customer email?
A Zap can start a new conversation by sending an email from an inbox, and it can add a note, a tag or an owner to an existing one. It has no action that sends a reply inside an existing conversation. Replies are written by a person in Sektra, or drafted by the assistant, Sektra's AI, for a person to review and send.
Connect Zapier and see it work
Connect a mailbox first, then add Zapier from Settings. Both steps take a few minutes, and the team can work from the inbox the same day.