What can start an automation, and what one can do
Every event and date that can start an automation with the details it carries, and every step an automation can do in each area.
An automation is started by one event in one area, and then does steps in any of the areas below. Only the areas you can use are offered.
What can start an automation
| Area | What starts it | Can be limited to | Details it carries |
|---|---|---|---|
| Forms | A form is answered; Someone pays for a form | One form | Each question's answer, First email address, First name, Who answered, When it was answered, Form, Link to the answers, and Amount paid when paid |
| Meetings | A meeting is booked; A meeting is confirmed; A meeting is moved to another time; A meeting is cancelled | Who booked, Name, Email address, Phone number, Starts, Length in minutes, Notes from the booking, Meeting | |
| Contacts | A contact is added | Contact, Name, Email address, Phone number, Company, Tags | |
| Contacts | A tag is added to a contact | One tag | The contact's details, and Tag added |
| Contacts | A note is added to a contact | The contact's details, and Note, Kind of note, Who added it | |
| To-dos | A To-do is added; A To-do is assigned to someone | One List | Title, Notes, List, Deadline, Who it is assigned to, Who added it or Who assigned it, To-do |
| To-dos | A To-do is completed | One List | Title, Notes, Who completed it, To-do |
| Issues | An issue is added; An issue is completed | One project | Title, Description, Priority, Status, Who reported it, Issue |
| Issues | An issue is assigned to someone; An issue's status changes; Someone comments on an issue | One project | The issue's details, and Who it is assigned to and Who assigned it, or Status before, or Comment and Who commented |
| Kanban Boards | A card is added; A card is moved to a column | One board | Card title, Card description, Column, Board, Card |
| Kanban Boards | A card is assigned to someone; Someone comments on a card | One board | The card's details, and Who it is assigned to and Who assigned it, or Comment and Who commented |
| Store | An order is paid; An order is fulfilled; An order is refunded | Buyer, Buyer's name, Buyer's email address, Buyer's phone number, Order number, Order total, What was bought, Order, and Amount refunded when refunded | |
| Store | A customer asks to return an order | The order's details, and Return number, Reason for the return, What is being returned, Customer's note | |
| Store | Someone asks for a quote | Who asked, Their name, Their email address, Their message, What they asked about, Subtotal, Quote number, Quote | |
| Store | Someone reviews a product | Product, Product page, Rating, Review title, Review, Reviewer's name, Buyer, Buyer's email address, Order number | |
| Store | Stock is low | Product, Variant, Quantity left, Product page | |
| Invoicing | An invoice is sent | Client, Client's name, Client's email address, Client's company, Invoice number, Invoice total, Due date, Invoice | |
| Invoicing | An invoice is paid | Client, Client's name, Client's email address, Client's company, Invoice number, Amount paid, Invoice | |
| Proposals | A proposal is sent; A client opens a proposal; A proposal is accepted; A proposal is declined; A proposal expires | Client, Client name, Client email address, Proposal number, Proposal title, Total, Proposal, and Valid until when sent or expired | |
| Proposals | A client asks a question or for changes | The proposal's details, and Their message, Kind of message | |
| E-Signatures | A document is sent for signing; A signature request expires | Document, Signers, Signature request, Sign by, and Still to sign when expired | |
| E-Signatures | Someone signs a document | Document, Signers, Signature request, Who signed, Signer's email address, When they signed, Still to sign | |
| E-Signatures | Someone declines to sign | Document, Signers, Signature request, Who declined, Email address of the person who declined, Their reason | |
| E-Signatures | Everyone has signed a document | Document, Signers, When the last person signed, Signature request | |
| Newsletter | Someone subscribes; Someone unsubscribes | Subscriber, Name, Email address, How they subscribed | |
| Courses | Someone applies to a course; A student enrols; A student completes a course; A student gets a certificate; A student's access ends | One course | Student, Name, Email address, Course |
| Courses | A student finishes a lesson; A student finishes a quiz; A student hands in an assignment | One course | Student, Name, Email address, Course, Lesson, and Passed the quiz and Score, out of 100 for a quiz, or Handed in late for an assignment |
| Webinars | Someone registers; Someone attends; Someone asks a question; Someone answers a live poll | One webinar | Attendee, Name, Email address, Webinar, and Place, or What they asked, or Question and What they chose |
| Webinars | A webinar ends | One webinar | Webinar, People registered, People who attended |
| Automations | At a set time | Date, Day of the week |
When each one happens
- A form is answered: a form's questions are details only when one form is chosen. First name is the first answer to a question about a name. First email address is the first usable email address in the answers.
- Someone pays for a form is for a form that takes a payment. It happens once the payment goes through. A form is answered happens earlier, when the form is sent, before the payment.
- Meetings: a booked meeting belongs to the member it was booked with, so automations for meetings are made in that member's Personal.
- A meeting is confirmed happens when you confirm a meeting that was waiting for your confirmation.
- A tag is added to a contact happens once for each tag a contact gains, a new contact's first tags included. Taking a tag off starts nothing.
- A note is added to a contact happens for every kind of note: a note, a call, an email, a meeting, a message.
- A To-do is added happens once when a To-do is made, however it was made: by you, by an import, by another area or by an automation. A repeating To-do counts once, not each time its next one appears.
- A To-do is assigned to someone happens when a To-do is given to a person, yourself included, or is made already assigned. Removing the person starts nothing. The same goes for an issue and a card.
- An issue's status changes happens when an issue moves to another status: by hand, with other issues, in triage, or by one of the rules in Issues. Completing an issue starts this and An issue is completed.
- Someone comments on a card: a comment from someone outside the team, on a board that takes suggestions, counts too, and gives only their name.
- A card is moved to a column: moving a card up or down in its own column is not a move. For one column, add an Only if step on Column.
- Store's events are offered only to a member who may see the same details in Store: See orders for orders, returns and quotes, Manage products and See orders for a review, and Manage stock or Manage products for stock. A team admin may use them all. An automation whose member loses the permission is paused.
- An order is fulfilled happens for each shipment or hand-over, and An order is refunded for each refund, since both can happen in parts.
- Someone reviews a product happens when a buyer posts a review, whether it waits for your approval or is published at once.
- An invoice is sent happens the first time an invoice is emailed to its client: by you, by a recurring invoice or by another area. Sending it again starts nothing.
- An invoice is paid happens when the invoice is paid in full. A part payment starts nothing.
- A proposal is sent happens each time a version is sent, a scheduled send included. A revised version sent again starts it again.
- A client opens a proposal happens the first time each recipient opens it. Your own look at it starts nothing.
- Someone signs a document happens each time one signer signs, the last one included, who also starts Everyone has signed a document.
- A proposal expires and A signature request expires happen when the date passes. One that is extended and expires again starts it again.
- Someone subscribes happens when a subscriber confirms, or subscribes by ticking a box at a Store checkout, on a webinar or course page, in a Social Media offer or on a form. An imported subscriber starts nothing.
- Someone unsubscribes happens only when the person unsubscribes themselves.
- A student finishes a quiz happens when the student hands in an attempt. An attempt Magpie closes itself, because it was left open or the student's access ended, starts nothing. A student hands in an assignment happens again for each new version handed in.
- A student's access ends happens when the student's last access to the course ends: it was removed, or it ran out.
- Someone asks a question happens when an attendee asks one in the live webinar. A question asked anonymously does not say who asked.
- Someone answers a live poll: only a person's first answer to a poll counts.
- A webinar ends happens when a session ends: the host ends it, its time limit is reached, or a pre-recorded webinar finishes. A test run starts nothing.
- At a set time: every day, every week on the days you choose, or every month on one day, at a time you choose. The time is in the time zone of the team's owner, or yours in Personal.
What an automation's own steps cause can start other automations, up to 3 automations in a row. An automation already in that row is never started again by it.
When a date arrives
Some records keep a date: a To-do's Deadline, an invoice's due date, the start of a meeting. An automation can start when that date arrives, or a number of days before or after it. Each date is listed under its area, after the area's other events.
| Area | What starts it | Timing | Can be limited to | Details it carries |
|---|---|---|---|---|
| To-dos | A To-do's Deadline arrives | Before, On the day, After | One List | Title, Notes, List, Deadline, Who it is assigned to, Who added it, To-do |
| To-dos | A To-do's When date arrives | Before, On the day, After | One List | The To-do's details, and When date |
| Issues | An issue's due date arrives | Before, On the day, After | One project | Title, Description, Priority, Status, Who reported it, Due date, Who it is assigned to, Issue |
| Kanban Boards | A card's due date arrives | Before, On the day, After | One board | Card title, Card description, Column, Board, Card, Due date, Who it is assigned to |
| Invoicing | An unpaid invoice's due date arrives | Before, On the day, After | Client, Client's name, Client's email address, Client's company, Invoice number, Invoice total, Due date, Amount owed, Invoice | |
| Meetings | A meeting starts | Before, At the time, After | Who booked, Name, Email address, Phone number, Starts, Length in minutes, Notes from the booking, Meeting | |
| Meetings | A meeting ends | Before, At the time, After | The meeting's details, and Ends | |
| Proposals | A proposal's last valid day arrives | Before, On the day | Client, Client name, Client email address, Proposal number, Proposal title, Total, Proposal, Valid until | |
| Courses | A student's access is about to end | Before | One course | Student, Name, Email address, Course, Access ends |
| E-Signatures | A signature request is about to expire | Before | Document, Signers, Signature request, Sign by | |
| Contacts | A contact's Last contacted date passes | After | One tag | Contact, Name, Email address, Phone number, Company, Tags, Last contacted |
Which records count
- A To-do's Deadline arrives counts a To-do that is not completed and not in Trash. A To-do's When date arrives also leaves out a To-do set to Someday. A To-do's own time of day is not used: its When date arrives at the time the automation names.
- An issue's due date arrives counts an issue that is not completed or cancelled.
- A card's due date arrives counts every card on the board, because a card is never marked done. To leave out a Done column, add an Only if step on Column. A suggestion still waiting for approval does not count.
- An unpaid invoice's due date arrives counts an invoice that was sent, not a draft or a void one, and is not paid in full. Amount owed is what is still to pay. An invoice is overdue the day after its due date. To start an automation then, choose An unpaid invoice's due date arrives, After, 1 day.
- A meeting starts counts a confirmed meeting, and A meeting ends a confirmed or finished one. As with the other meeting events, they are made in the Personal of the member the meeting was booked with.
- A proposal's last valid day arrives counts a proposal that was sent and is not yet accepted, declined, expired or withdrawn. Valid until is the last day the client can accept. The day after, the proposal expires, which starts A proposal expires.
- A student's access is about to end counts a student whose access to the course has an end. Access that is extended moves the date, and access with no end means the student has no date. A student's access ends starts at the moment itself, so this one offers only Before.
- A signature request is about to expire counts a request still waiting for signatures. A signature request expires starts at the moment itself, so this one offers only Before.
- A contact's Last contacted date passes counts a contact with a Last contacted date. That date moves forward when you set it, when a note is added to the contact, and when Outreach writes to them. "Not heard from for 30 days" is After, 30 days. Limited to one tag, it counts the contacts that have the tag at that moment.
Timing
- A date with no time of day (a Deadline, a due date, Valid until, Last contacted) arrives at the time you choose, in the time zone of the team's owner, or yours in Personal. Before and After count days, from 1 to 365.
- A date with a time (a meeting's start or end, the end of a student's access, a signature request's expiry) arrives at that moment. At the time starts then. Before and After count minutes (5 to 120), hours (1 to 48) or days (1 to 365).
- Days keep the time of day: 3 days before a request that expires at 12:00 is 12:00 three days earlier, in the team's time zone. Hours and minutes count exactly: 1 hour before a meeting at 15:00 is 14:00.
- When the clocks change, a time that does not happen that night starts at the first moment after it, and a time that happens twice starts at the first of the two.
When it starts, and how late
- An automation starts within about a minute of its date's moment, once for each record. Changing the time of day after it has run for a record today does not run it again for that record.
- Moving a record's date makes a new moment. A run that already started for the old date goes on.
- A record that is completed, paid, cancelled, signed, moved to Trash or given another date before its moment starts nothing.
- If Magpie cannot start it at its moment, it starts later the same day, in the team's time zone. For At the time, or a timing in minutes or hours, it starts up to an hour late. After that it does not start, so a reminder never comes days late.
- Before never starts at or after the date itself.
- Nothing starts for a moment before the automation was turned on, or before Use these changes changed its When. Turned on at 15:00, an automation for To-dos due today at 09:00 starts nothing for today's To-dos, and starts at 09:00 tomorrow for tomorrow's.
- Send an email goes only to a member of the team, because nobody did anything to start it.
What an automation can do
| Area | Step | Answers | Details it gives later steps |
|---|---|---|---|
| Contacts | Add or update a contact | Email address (required), Name, Phone number, Company, Tags to add, Note | Contact, Name, Email address |
| Contacts | Add tags to a contact | The contact, or its email address; tags | Contact |
| Spreadsheets | Add a row to a spreadsheet | Spreadsheet; one answer for each column heading | Spreadsheet, Row number |
| To-dos | Add a To-do | Title (required), Notes, Deadline, or Deadline, in days after it happens; List | To-do, Title |
| Kanban Boards | Add a card | Board, Column, Title, Description | Card, Title |
| Notes | Add a Note | Title, Text | Note, Title |
| Issues | Add an issue | Title (required), Description, Project | Issue, Title |
| Team chat | Post a message in a channel | Channel, Message (both required) | None |
| Calendar | Add an event | Title and Starts (required), Length in minutes, Notes | Event, Title, Starts |
| Documents | Make a document | Title (required), Text | Document, Title |
| Newsletter | Add a subscriber | Email address (required), Name | None |
| Automations | Send an email | To, Subject and Message (all required) | None |
| Automations | Send the details to a web address | Web address, Details to send, Secret to sign with (all required) | It answered |
No step deletes anything, moves money, publishes anything or shares a record with someone outside the team.
What each step does
- Add or update a contact looks for a contact in Personal or the team with the email address. If there is one, it fills only the facts that are empty and adds the tags, and never changes a name, phone number or company that is set. If there is none, it adds one.
- Add a row to a spreadsheet reads the first row of the first sheet as
its column headings, and writes the row under the last row that holds
anything. A value that starts with
=is written as text, not as a formula. - Add a row to a spreadsheet: a heading added to the sheet later appears as a new answer. A heading removed from the sheet leaves its answer marked "(no column now)", and that value is left out.
- Add a To-do: Deadline, in days after it happens counts from the day of the event in the team's time zone, and is used instead of Deadline when both are filled.
- Add a card puts the card in the column with the name you chose, or in the board's Inbox when no column is chosen.
- Post a message in a channel offers the channels you are in that are not archived.
- Add an event takes Starts as a date and time such as
2026-11-20 14:00, in the team's time zone, or a date for an all-day event. Without a length the event is 60 minutes long, and it can be up to 14 days long. Its team can see it; it is never public. - Add a subscriber works only when the member it runs with is a team admin. The person gets the Newsletter's confirmation email and joins when they confirm. An address that unsubscribed is not added again.
- Send an email sends one email to one person: a member of the team, or the person who did what started the automation. It comes from the team's name, or yours in Personal. To someone outside the team, its last line says why they received it.
- Send an email to the person who did it is offered when the event is something that person did themselves: they answered or paid for a form, booked a meeting, paid an order or an invoice, asked for a return or a quote, reviewed a product, subscribed, applied to or enrolled in a course, finished a lesson or a quiz, handed in an assignment or completed a course, registered for, attended, asked a question in or answered a poll in a webinar, opened, asked about, accepted or declined a proposal, or signed or declined to sign a document.
- Send an email: Personal or a team sends at most 200 of these emails a day.
- Send the details to a web address: see Send details to a web address.
If an area you use is missing from these lists, Contact support.
Ask Magpie support
Send Magpie staff a question about anything this article does not answer.