Question 1

Can I connect Fairu to a CMS that is not Statamic?

Accepted Answer

Create a token in the API area, tick the permissions it needs, and call the REST endpoints or the federated GraphQL endpoint. There is no connector to install on either side. The GraphQL url field already returns a finished delivery URL you can drop into a template.

Question 2

How do I get Fairu into my Statamic site?

Accepted Answer

Three steps: composer require sushidev/fairu-statamic, two lines in your .env file, and php please fairu:setup to migrate existing assets. From then on you place images with an Antlers tag and pick them in a Fairu fieldtype, without leaving the control panel.

Question 3

Can Fairu notify my system when an asset changes?

Accepted Answer

Webhooks are active during the trial and on plans that include them. Pick the entity and the events, paste the target URL, and add basic or bearer auth if the receiving side needs it. Fairu batches the events and logs every delivery with response status and duration.

Question 4

My assets already sit in an S3 bucket. Do I have to move them?

Accepted Answer

No. Add the bucket once with its credentials and Fairu checks it on a schedule, importing new files as they show up. FTP and SFTP connections work the same way, and a file pattern narrows down what gets pulled in.

Question 5

Will my existing S3 tools and scripts keep working?

Accepted Answer

Your tools stay, the endpoint and keys change. The workspace owner creates a Raku credential and the dialog hands you the aws configure lines to paste. Uploading, downloading, listing and deleting run over the S3 API; server-side copy and bucket management do not.

Let your team work in the tools it knows.

Connections for your CMS, apps and file tools

Questions about integrations

Connect the tool your team uses every day.