What to ask for

Ask for the outcome. The assistant chooses the tools, and will usually check its work before telling you it is done.

Make a template

Make me a certificate of completion. Our colours, the student's name large in the middle, the course name and date underneath.

It reads your brand kit, drafts the design, validates it, fixes anything the validator flags, and previews it. Previews are free, so it can iterate.

You get a template in your account and a preview image. Nothing has been rendered for real and no credit has been spent.

Change one

The name is too close to the border. Move it down and make the course name smaller.

It fetches the current design, edits it, and previews again.

Use a Word document you already have

Here is our offer letter. Turn it into a template.

Word templates keep their own fonts, tables, headers and layout exactly, which is the reason to use one rather than have a design drawn from scratch. The assistant gives you a link to send the file to, checks it, and tells you which placeholders it found.

If you would rather start from one of ours, ask for a Word template from the library — it can copy one, hand you the file to edit, and put your edited version back.

Go back to an earlier version

The last change made it worse. Put it back to how it was this morning.

Every save is kept. The assistant can list them with a note of what each looked like, and restore one. Restoring adds a version rather than erasing any, so nothing is lost either way.

Render documents

Generate certificates for these twelve students.

Each comes back with a link you can share.

Set up a link that renders on demand

Create a Dynamic URL for the certificate template so our system can build links itself.

You get one permanent address plus a signing secret. Your own code builds links from it, and nothing calls us until someone opens one.

See Dynamic URLs for the signing details.

Collect and generate

Make a form that asks for a name and a course, and generate a certificate from every submission.

It creates the form, connects it to the template, maps the fields, and publishes it. You get a link to share.

Wire up a notification

Tell my app at https://example.com/hooks whenever a certificate finishes.

It creates the webhook and sends a test delivery so you can see the payload shape before anything real fires.

Being specific pays

Vague in, vague out — the same as with a person.

What it will refuse

It cannot delete a template, run a bulk job, or write a Word document from scratch — a .docx is a real file, not something that can be typed out. It can upload one, fetch it back, edit it and replace it. Those live in the dashboard, deliberately — see Tools.

Last updated on