Higgsfield, without opening Higgsfield.
Describe the shot in the thread, approve the prompt, get the file back.
“@Ray make three vertical variants of this hero shot”
What Ray can and cannot do in Higgsfield
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Higgsfield
- Which models exist and what each one accepts
- Your past generations, your uploaded media, and the presets and voices to draw on
- Whether a job has finished, with a bounded wait for up to twelve at once
- Credit balance, transaction history, and which workspace the spending lands on
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Generating images, video, audio and 3D models, one at a time or in a batch
- Editing what exists: upscale, outpaint, reframe, background removal, motion control
- Changing the voice in a video, or dubbing it into another language
- Cloning a voice from audio you uploaded, on a card that states the person agreed to it
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Run shell commands in Higgsfield's cloud sandbox, or call Marketplace apps on your behalf
- Publish to a connected TikTok account, or enter a website into a contest
- Buy credits, cancel a trial, or confirm on your behalf that you own a flagged generation
How Ray works with Higgsfield
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Higgsfield
One click, right where you asked. Ray posts a connect card, you authorise Higgsfield with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Higgsfield, and tell Dana it is being looked at.
Clone a voice in Higgsfield. Approving confirms this person agreed to their voice being used
- Waiting on
- your approval
What does connecting Higgsfield to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Higgsfield and it can do the Higgsfield part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Higgsfield account, so Ray can only reach what that person can already reach, and the history in Higgsfield shows who actually asked.
Security and permissions
- You authorise Higgsfield on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Higgsfield in a message, or uninstall Ray and every connection it held is revoked.
More design & whiteboards integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Higgsfield.
Free to start, no credit card, and it asks before it acts.