Automation and AI
Automations that do the next step for you
- TriggerForm submittedReferral form
- ActionCreate taskCall within 2 days · Sam
- ActionSend emailWelcome and what happens next
- WaitDelay / Wait3 days
- ActionSend SMSCheck-in text
What it does
What can start an automation
- Something happens in Affinux: a record is created or changed, a stage moves, a case opens, a payment arrives, an invoice falls overdue, a campaign is opened or clicked, someone unsubscribes, a calendar event is about to start or has ended. The list follows the features the organisation has switched on.
- A form is sent in, any form or a chosen one.
- A message arrives.
- A date on a record comes round, such as a birthday, a renewal or a review date, on the day or a set number of days before or after.
- A schedule, such as every Monday at 9 or the first of each month.
- Another system calls the automation’s private web address.
- A person starts it, for one record or for a list of people.
Paths and timing
- If and otherwise, on any field, including the organisation’s own custom fields.
- Several paths chosen by a value, and A/B splits to try two versions.
- Wait for a set time, until something happens (with a time limit), until working hours, or until a date on the record.
- Ask a person to approve before it goes on, with a separate path for a rejection.
- Pace it: no more than a set number in a period, the rest held, never dropped.
- Goals that move someone on as soon as they are met, and steps that jump or end the run.
What it can do
- People: update a field or custom field, add or remove a tag, assign an owner, set a status, give or remove a role, change a role’s status, create a person.
- Tasks: create, update or complete a task.
- Pipelines: create an opportunity, move its stage, mark it won or lost.
- Programmes: enrol someone, end their place, send a survey link.
- Calendar: book an appointment, invite someone, change its status, cancel or reschedule it and tell everyone.
- Messages: send an email, a text or a saved message template, add someone to a campaign group, send a form link.
- Money: create, issue and send an invoice, record a payment, void an invoice, create a payment link.
- Documents: issue a certificate, letter or receipt, and email it.
- Call log: log a call.
- Your team: notify a member of staff, or everyone in a role.
- AI: write something with the AI assistant and use it in later steps.
- Other systems: call another system’s web address, with its key kept safe.
- Other automations: start another automation.
Building and testing
- A visual canvas with undo, copy and rename.
- Templates to start from, such as a welcome series, chasing overdue invoices, a certificate on attendance, a receipt for a donation and a survey with a reminder.
- Details from the person, the record that started the run, earlier steps and the organisation’s own saved values, merged into messages and fields.
- Test the whole flow on a sample, or test one step without it doing anything.
- Checks before it goes live, such as a missing sender address.
- Versions, with any earlier one restored to the draft.
- Export an automation as a file and import it into another workspace, always as a draft.
Running and watching
- A history of every run, saying in plain words what each step did and why a step was skipped.
- Temporary failures are tried again; anything else follows the step’s error path, or the run stops and a notification names the step that failed.
- Run again, or cancel runs that are waiting.
- Choose whether someone can go through an automation more than once.
- Switching one on offers to start it for the people already waiting.
- What it creates is filed under the branch of the record that started it.
How it works
- Pick what starts it, and narrow it with filters: only this form, only this stage.
- Draw the steps: actions, conditions, waits and approvals.
- Test it on a sample record.
- Switch it on. From then on every match starts a run.
- Watch the runs, and change the draft whenever you need; the live version keeps running until you publish.
In your kind of organisation
Examples with made-up people and projects.
Charity delivering funded services
a referral form is sent in; the automation creates the person, opens a case, tells the duty worker, and sends the referrer an acknowledgement during working hours.
More for this kind of organisationFoster carer association
an applicant moves to Assessment; the assessor gets a task and the applicant the information pack, with a reminder a week later if they have not replied.
More for this kind of organisationMembership body
the day before a course, every booked member gets a reminder; when attendance is marked, each one is sent their CPD certificate.
More for this kind of organisationFundraising-led charity
a donation arrives; the donor gets a receipt and thanks, and first-time donors are tagged for a welcome series.
More for this kind of organisationSocial enterprise
an invoice falls overdue; finance is told and a chase task is created.
Control and safety
- An automation can only use steps the organisation has switched on and the builder’s role allows.
- Marketing messages it sends follow each person’s consent and quiet hours, like any other send.
- An approval step stops the run until a named person says yes or no.
- Every change it makes is recorded in the audit trail as made by an automation.
- Another system can only start it through its private address, and a call repeated with the same request key runs once.
- Keys for other systems are stored encrypted and kept out of the run history.
Works with
- Forms: a form sent in starts an automation.
- Email campaigns: campaign opens, clicks and groups; message series are listed under Campaigns as journeys.
- AI assistant: an AI step writes text for later steps, and every action here is also something the assistant can propose.
- Letters and documents: issue and email documents.
- Programmes and outcomes: enrolments and survey links.
Good to know
- How many live automations and runs a month an organisation has comes from its plan.
- Steps are Affinux’s own. To reach another app, another system calls an automation’s address, or a step calls the other system’s address.
Which plan you need
See what each plan includes and its limits.
See how Affinux would work for your team
A 30-minute demo, shown with your type of organisation. Or start a free trial and explore with sample data.