Lynxbe
עברית
All guides
A dedicated key, a server-side secret and one enquiry checked in the board.
Base44 screens are documentation-based illustrations. The complete connection has not been verified in a live account.
A 3-minute 30-second video in 12 chapters. Jump directly to the step you need.
Connect one form and follow one enquiry through to its Lynxbe card.
The video is currently unavailable. Continue with the written guide and walkthrough below.
From form to board. Connect one form and follow one enquiry through to its Lynxbe card. Original Lynxbe screen · Demo data
Open API keys. Open API Documentation and choose API Keys. Check that you are in the right business. Original Lynxbe screen · Demo data
One key for this form. In Create New Key, give it a clear name: Base44 form. Original Lynxbe screen · Demo data
Only the permission you need. Deselect People Read and select only Write Contacts: write:contacts. Original Lynxbe screen · Demo data
Copy it once. The key is shown once. Copy it for server-side secret storage. Original Lynxbe screen · Dummy key
Keep the secret on the server. In Base44, save LYNXBE_API_KEY as a secret. Only the backend function reads it. Base44 illustration · No live connection
Connect the existing form. Ask for a backend function. Keep the design and entered values, with one request per enquiry. Base44 illustration · No live connection
One enquiry to check. Fill the example with Dana Example, a phone number, email and message. Base44 illustration · No live connection
Submit. Then wait. Click once. A receipt means the enquiry was captured; check its card in the board. Base44 illustration · No live connection
Return to the board. Refresh or reopen the board and find the same enquiry. Original Lynxbe screen · Demo data
Check inside the card. Open the enquiry and check its name, phone, email, message and base44-landing source. Original Lynxbe screen · Demo data
Know what to check. And how to stop. No card? Check before submitting again. To stop the connection, choose Revoke Key. Original Lynxbe screen · Dummy key
A local review example. Original Lynxbe screens use isolated data; Base44 screens are labeled illustrations. No live key or lead was created and no app was published. The complete journey in a Base44 account still needs verification. The original key-creation form was captured in a taller desktop viewport; it has a height limitation in shorter windows and on mobile. Some portrait scenes adapt the original desktop capture.
Before starting: the right Lynxbe business, key-management access, active CRM and a board with suitable contact columns. In Base44, you need an existing form plus access to secrets and backend functions. Before real testing, also review the automations and messages triggered by a new enquiry.
Open CRM → Boards and check your enquiry-intake board and its columns. This connection lets Lynxbe choose a suitable board; the form does not select a board ID. Our example has one Leads board with name, phone, email, message and source columns. Check that CRM is active and included in your plan.
Open Automation & Integrations → API Documentation → API Keys → Create New Key. Name it Base44 form. Deselect the default People Read scope and select only Write Contacts (write:contacts). The key is shown once after creation. Copy it directly to secret storage; keep it out of the AI chat and browser.
In the correct app, save LYNXBE_API_KEY as a secret. Only the backend function reads it. The Base44 screens here are illustrations; check the menu and access in your account. Current Runtime documentation describes secrets.get inside the request handler. Check compatibility with your app’s runtime.
Use the prompt below to create submitLynxbeLead and connect your form to it. Keep its design and entered values. The form asks for a name and at least one contact method, works for guests, and blocks another submission while pending. The key stays on the server and no marketing consent is sent. Review the generated result and app version before real testing.
In an isolated environment, enter one enquiry: Dana Example, 0500000001, dana@example.com and Please tell me more about the service. Refresh or reopen the board and open the card. Check all five fields and source base44-landing. The phone may be stored as 972500000001. A capture receipt does not guarantee a card. On failure, keep the form values; when delivery is uncertain, check capture before submitting again. To stop the connection, choose Revoke Key from the three-dot menu; revocation is immediate.
Check inside the card: the name, phone, email, message and source match the form. A thank-you message alone does not prove a card was created.
Captured without a card? Check CRM, the board and columns. Uncertain delivery? Check capture before trying again. Another submission can create a duplicate.
The prompt requests a backend function while keeping the form you already built. It was not sent to Base44 for this example and does not request app publication.
Connect the existing contact form on my Base44 landing page to Lynxbe. Preserve its current design, user-entered values and other app behavior. Create a backend function named submitLynxbeLead and call it from the form. It must work for anonymous visitors; do not require them to sign in to submit an enquiry. Read LYNXBE_API_KEY only through the supported Base44 server-side secrets API inside the handler. Send one POST to https://api.lynxbe.co.il/api/v1/leads with Content-Type: application/json and X-API-Key set from that secret. Allow only name, phone, email and message from the form. Set source to "base44-landing" on the server. Do not accept a client-supplied business ID, key or target URL. Require a trimmed name and at least one usable contact method in this form. Do not add consent, marketing opt-in or extra integration actions. Disable repeat submission while pending. Keep entered values when an error occurs. Never automatically replay this POST after a timeout or uncertain response: the lead endpoint has no request-idempotency guarantee. Check the Lynxbe JSON envelope, not just HTTP status. HTTP201 with success:true means the enquiry was captured. Show the visitor a calm receipt acknowledgement even when data.crmItemId is null; do not encourage another submission of an already captured enquiry. Report missing CRM linkage separately to the app owner using submissionId and crm_item_skipped when present, without logging the secret or personal form contents. Do not label a CRM card as created without crmItemId. When using base44.functions.invoke, read its response.data transport wrapper before the Lynxbe success/data envelope. Show a plain recoverable message on a definite failure, and an uncertain-delivery message on a timeout. Keep the key and upstream error details out of the browser. Do not publish the app.
Content checked against the source code and official Base44 documentation on 14 October 2026. Isolated product capture and provider illustrations do not prove a live connection, provider-account access or a deployed version. Presentation placement remains unassigned.
A read-only walkthrough. Choose a step or use Next. It does not submit, create a key or change an account. Each Base44 illustration is labeled.
The landing page receives the enquiry. In Lynxbe, the team sees it in a board and can handle it. This is a local review example: original Lynxbe screens with isolated data, alongside clearly labeled Base44 illustrations. It does not prove a live connection for your app. The goal is to check the same name, phone, email, message and source inside the card.
Open API Documentation and choose its API Keys tab. Key creation needs the appropriate permission. Check the business before creating a key: the key determines which business the connection can access. The film starts on API Documentation; it does not show global-menu navigation.
Choose Create New Key and enter Base44 form. A dedicated form key helps you identify and revoke this connection without revoking other integrations. The name is a management label; it is not the secret key. The walkthrough uses a dummy key only and creates no key in a real account.
People Read is selected by default; deselect it. Select only Write Contacts, identified by write:contacts. That is the key scope this lead-capture route requires. It does not need Full Access or messaging scopes. Check the selection before creating the key. A key scope is separate from the user permission needed to manage keys.
The key is shown once after creation. Copy it directly into your app’s secret storage. Keep it out of the AI prompt, form and browser code. The displayed value here is a labeled dummy key that grants no access. Check that the key card lists only Write Contacts.
In the correct Base44 app, find Secrets and save the key as LYNXBE_API_KEY. Its name must match the name read by the function. This screen is a labeled illustration; check the menu and secret access in your own account. Current Runtime documentation reads the secret inside the request handler with secrets.get. Check support in your app’s runtime.
Copy the full prompt below the video into Base44 chat. It requests submitLynxbeLead: a backend function receiving name, phone, email and message, reading the secret on the server and sending to Lynxbe with source base44-landing. The form must also work for guests without accounts. Review the generated code and form. A chat reply or saved code does not prove the live site has changed. This illustration is not a chat performed in a Base44 account.
In an isolated environment safe for testing, enter one enquiry. Our example uses Dana Example, 0500000001, dana@example.com and Please tell me more about the service. The form asks for a name and at least one contact method. Also check it as a guest without a sign-in page. It does not request marketing consent. This image illustrates the form; it is not a published Base44 page capture.
While submitting, the button waits for the request to finish and blocks a second click. HTTP201 with success:true means the enquiry was captured; it does not guarantee a CRM card. The illustration shows an example receipt, not a live request. On failure, keep entered values. When delivery is uncertain, check Lynxbe before trying again: another submission can create another enquiry and card.
Open CRM, Boards, and the board receiving enquiries. This connection lets Lynxbe choose a suitable board within the business; the form does not select a board ID. Our isolated example has one Leads board with contact columns. Refresh or reopen it and find Dana Example. If the enquiry was captured without a card, do not submit it again. Check CRM availability, plan access and a suitable board, then investigate why the enquiry was not linked to a card.
Open the card and check the actual fields. The name and message should match the form; 0500000001 may be stored as 972500000001. Check dana@example.com and source base44-landing. Fields populate existing columns, so a missing column can leave a detail out of the card. Capturing an enquiry does not grant marketing consent. This Lynxbe screen uses isolated data and does not prove a live Base44 end-to-end journey.
If the card is missing, first check capture, CRM availability, the board and its columns. A wrong key or missing scope needs a connection fix, rather than Full Access. To stop the connection, find Base44 form in API Keys and choose Revoke Key from its three-dot menu. The current interface revokes immediately. This shows an isolated dummy key only; no live key is revoked and no customers are affected.
