Skip to main content
You can ask Fabricate to write code that connects your app to an external service. Treat each connection as an implementation to verify, not a preconfigured integration or a guarantee that every provider works.

​
Describe the connection

Provide the provider’s public documentation, the action you need, the data to send, and the response your app should show. Explain whether the action happens when a user clicks a button or when an external event arrives.
Confirm that the provider supports server-side HTTP access from your hosting environment. Features needing a background scheduler or long-running process require an explicit design; a page loading successfully does not establish that those processes exist.

​
Configure credentials

Create the provider account and credentials yourself. Add sensitive values in your project’s Environment settings using the exact names the code reads. Never place secret keys in browser code, prompts, or URLs. Secrets are applied to the published app when you publish. Preview does not receive them. Use test credentials on the published app while validating the integration, then configure production credentials only when ready.

​
Test more than success

Check a valid request, rejected input, an invalid credential, a provider timeout, and repeated submissions. For webhooks, verify signatures, reject invalid requests, and handle repeated deliveries without repeating the action. Keep the provider’s delivery or request receipt when available. A confirmation screen alone does not prove the external action happened. For payments, follow Payments and verify the provider’s test-mode result before using real money.