Creating a Blob and giving it a job
Creating a Blob is four decisions: what it is called, what its job is, how much it can do without asking, and what it is allowed to reach.
Give it only what its job needs
- Start from a suggestion or from scratch
- The description is the brief
- Decide how much it can do without asking
- Give it only what its job needs
Starting from a starter
Pick one of the suggested Blobs and it arrives with its job already described. Editing it afterwards is expected, not a sign you picked wrong.
Naming and describing the job
The description is the actual brief. Write it as you would brief a person: what it is responsible for, what good looks like, and what to leave alone.
Choosing autonomy
| Mode | What it means |
|---|---|
| Read only | Can look at things and tell you what it found. Cannot change anything, anywhere. |
| Ask me first | Works on its own, but asks before anything that sends, spends, publishes or deletes. |
| Go ahead | Acts without asking, except for money, sending on your behalf, publishing and deleting, which always ask. |
The floor under Go ahead
This is worth reading twice. Even on Go ahead, anything involving money, sending on your behalf, publishing or deleting still asks first. That floor cannot be switched off. See approvals and undo.
Connectors and skills
Give it only what its job needs. An expenses Blob does not need your calendar. See connectors overview and skills.
Meeting it before you save
The form previews the Blob's expressions, so you see it before it exists.