Productivity · CONNECTIONRead Fallax phishing-simulation reports, events, campaigns and summaries, and keep its people directory in step with HR.
Explore 11 workflow actions for Fallax, including account permissions and operation limits.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Add a person, or update the one with this address (safe to repeat).
A repeated request may repeat the external action. Review the previous result before retrying a write.
Take a leaver out of the programme; their evidence trail is kept and the seat is freed.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The workspace the key belongs to and its scope.
One campaign and its counts.
One person from the directory.
People tested, messages delivered, and open, click, credential-submit and report rates for a period, with the previous period beside them.
Simulations with their send, open, click, submit and report counts.
The simulation interaction log: sent, opened, clicked, scanned, submitted and reported, each with its person.
The directory of people the workspace can simulate.
Messages people reported as phishing; verdict unknown means it matched nothing Fallax sent.
Change a person by id (the address cannot change).
A repeated request may repeat the external action. Review the previous result before retrying a write.
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
Inspect step outputs and confirm the result in Fallax. A saved workflow is not a completed provider action.
