{"id":18336525,"url":"https://github.com/onedoclabs/fileforge-triggerdev","last_synced_at":"2026-05-12T12:42:31.648Z","repository":{"id":250303831,"uuid":"834076638","full_name":"OnedocLabs/fileforge-triggerdev","owner":"OnedocLabs","description":"Sample Fileforge repository leveraging Trigger.dev v3 functions.","archived":false,"fork":false,"pushed_at":"2024-07-26T11:29:24.000Z","size":636,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-07-05T06:36:48.521Z","etag":null,"topics":["document-generator","fileforge","react","triggerdev"],"latest_commit_sha":null,"homepage":"https://www.fileforge.com","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/OnedocLabs.png","metadata":{"files":{"readme":"readme.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-07-26T11:15:37.000Z","updated_at":"2024-07-26T11:29:27.000Z","dependencies_parsed_at":"2024-07-26T12:49:33.712Z","dependency_job_id":"f1012c00-7dde-454f-a92b-7100fb8cffc9","html_url":"https://github.com/OnedocLabs/fileforge-triggerdev","commit_stats":null,"previous_names":["onedoclabs/fileforge-triggerdev"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/OnedocLabs/fileforge-triggerdev","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OnedocLabs%2Ffileforge-triggerdev","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OnedocLabs%2Ffileforge-triggerdev/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OnedocLabs%2Ffileforge-triggerdev/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OnedocLabs%2Ffileforge-triggerdev/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/OnedocLabs","download_url":"https://codeload.github.com/OnedocLabs/fileforge-triggerdev/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OnedocLabs%2Ffileforge-triggerdev/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":272930000,"owners_count":25017057,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-30T02:00:09.474Z","response_time":77,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["document-generator","fileforge","react","triggerdev"],"created_at":"2024-11-05T20:08:09.917Z","updated_at":"2026-05-12T12:42:31.597Z","avatar_url":"https://github.com/OnedocLabs.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Trigger.dev (v3) + Fileforge\n\n---\n\nThe easiest way to generate documents, reports, and presentations from your data!\n**This example is free for most use cases.**\n\nAdvantages of using [Trigger.dev](https://trigger.dev) + [Fileforge](https://fileforge.com):\n\n- Stack agnostic: Trigger.dev runs your functions in a runtime compatible with Fileforge. You can trigger your functions from any language or platform, including Python, Node.js, Ruby, Go, Java, and more.\n- No infrastructure: rendering documents is a heavy task that requires a lot of resources. Trigger.dev and Fileforge take care of all the infrastructure for you.\n- Use React: even if you do not have a React stack, you can use React to generate your documents.\n- Easy to monitor: Trigger.dev provides a dashboard where you can see the status of your functions and logs.\n\n## Getting started\n\n### Create a Trigger.dev account\n\nHead to [Trigger.dev](https://trigger.dev) and create an account. You will also be prompted to create a project. If you already are a Trigger.dev user, you can just create a project or use an existing one.\n\n### Create a Fileforge account\n\nHead to [Fileforge](https://fileforge.com) and create an account. Your API key will be displayed on the dashboard.\n\n![Fileforge dashboard](/images/fileforge-dashboard.jpg)\n\n### Configure the repository\n\nStart by cloning this repository:\n\n```bash\ngit clone https://github.com/onedoclabs/fileforge-triggerdev.git\ncd fileforge-triggerdev\n```\n\nThen, install the dependencies:\n\n```bash\nnpm install\n```\n\n### Configure the environment variables\n\nYou can copy and rename the `.env.example` file to `.env`:\n\n```bash\ncp .env.example .env\n```\n\nThen, open the `.env` file and fill in the `TRIGGERDEV_API_KEY` and `FILEFORGE_API_KEY` variables.\n\n- `TRIGGERDEV_API_KEY` can be found in the Trigger.dev dashboard, on the left hand side, under `API Keys`.\n- `FILEFORGE_API_KEY` can be found in the Fileforge dashboard, in the dark box at the top.\n\n### Configure the Trigger.dev project ID\n\nYou can find the project ID in the Trigger.dev dashboard, on the left hand side, under `Projects`.\n\nThen, open the `trigger.config.ts` file and replace the `triggerProjectID` value with your project ID.\n\n```ts\nconst triggerProjectID = \"your-project-id\";\n```\n\n## Run the example\n\n### Start the Trigger dev server\n\nThis command will start the Trigger dev server. This server will respond to test requests from the Trigger.dev dashboard.\n\n```bash\nnpm run dev\n```\n\nThen, head over to the Trigger.dev dashboard and click on the `Test` button. You should see the function.\n\n![Trigger.dev test](/images/triggerdev-functions.jpg)\n\n### Run a test request\n\nWhen clicking on the function, you can set a payload value and run the test.\n\n![Trigger.dev test run](/images/triggerdev-run.jpg)\n\n### View the logs\n\nYou can now view the logs and your generated document by using the URL logged in the console.\n\n![Trigger.dev URL result](/images/triggerdev-result.jpg)\n\nNB: the URL in the return preview is truncated. You should use the console URL to view the full document.\n\n### View the document\n\nYou can now view the document generated by the function.\n\n![Generated document](/images/document-example.jpg)\n\n## Deploying\n\n### Set up the Fileforge environment variable\n\nHead to your Trigger.dev dashboard and set the `FILEFORGE_API_KEY` environment variable (under `Environment Variables`) to the value of your Fileforge API key.\n\n### Deploy the function\n\nTo deploy the function, use the following command:\n\n```bash\nnpm run deploy\n```\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fonedoclabs%2Ffileforge-triggerdev","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fonedoclabs%2Ffileforge-triggerdev","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fonedoclabs%2Ffileforge-triggerdev/lists"}