Skip to main content
Depending on connected tools and workspace permissions, Ellie can help propose or perform actions such as creating a ticket, scheduling a reminder, setting an alert, or creating a recurring report.

​
Read versus write

​
Safe action pattern

  1. Ask for analysis.
  2. Ask for a draft action.
  3. Review destination, owner, recipients, schedule, timezone, and content.
  4. Ask what permission and connector will be used.
  5. Confirm only the intended action.
  6. Open the destination system and verify the result.
  7. Record or reverse the action if it is incorrect.

​
Ticket example

After review:

​
Alert and report example

Create the automation from Pulse after checking recipients and timezone.
Free-form instructions can combine connected context with external actions. Use least-privilege connectors, narrow scopes, test channels, and human review for changes that affect source control, incident response, tickets, people, or spend.

​
Verify and audit

For every write, capture:
  • Requesting user
  • Time and timezone
  • Connector identity
  • Destination
  • Created or changed object
  • Returned source link
  • Confirmation or approval state
  • Rollback or deletion path
If your workspace requires immutable audit logs, confirm the supported audit capability with Entelligence before relying on conversational history.

​
Next step

Use Automations for repeatable workflows or read permissions and troubleshooting.