Linq integration
Messaging connector, available on Zeplik
Linq is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Linq and Zeplik can act on your team messaging for you: Send and manage iMessage, RCS, and SMS conversations, attachments, phone numbers, payments, and webhooks through the Linq Partner API. You stay in the conversation while the assistant does the work in Linq directly.
Zeplik exposes 25 read actions and 43 write actions for Linq. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Linq without your consent.
Try Linq on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
What Zeplik can do with Linq
Read from Linq (25)
Runs automatically in any conversation.
Check messaging capability
Check whether a recipient can receive iMessage or RCS without sending a message. Linq permits only one capability check per 10 seconds; cache successful answers briefly (minutes, not days) instead of checking before every send.
Get attachment
Return metadata and current status for a Linq attachment referenced by a message. This metadata-only action does not download the file.
Get available number
Select an available Linq sending number, optionally for recipients or a line type. Treat the returned vCard URL as sensitive and ephemeral.
Get chat
Return one chat by ID, including participants, service, state, and health information.
Get chat location
Return precise locations currently shared by contacts in a chat. Treat coordinates and addresses as sensitive and minimize retention.
Get experience
Return one Linq experience and preserve its dynamic action field definitions. Discovery does not prove that required provider setup is complete.
Get message
Return one Linq message by ID with its content parts, sender, actual and preferred transport, delivery state, reply target, and timestamps.
Get payment
Read a payment's financial state, amount, customer handle, merchant details, and any customer-action URL. Treat returned identifiers and hosted URLs as sensitive financial metadata.
Get payment credentials
Return the complete, highly sensitive short-lived handoff used to reveal a ready payment's virtual card directly from the provider. The response includes provider, user_token, card_ref, and fetch_url when supplied. Use it only for the immediate authorized checkout; never log, persist, or disclose the handoff or the resulting PAN/CVC.
Get payment handle connection
Read the financial-consent connection status for a customer phone number or email. Query only a customer handle whose owner consented to this lookup; the response may include a transient connect_id for a pending ceremony.
Get payment provider
Read the organization's onboarding status for a payment provider. This is a read-only financial setup check; a 404 is an execution failure and must not be interpreted as a normal disabled status.
Get payment request
Return one payment request's amount, lifecycle status, checkout details, and provider join keys. This is read-only financial metadata; treat checkout URLs and customer or provider IDs as sensitive.
and 13 more.
Act in Linq (43)
Runs only after you enable write access.
Add chat participant
Add an external participant to an existing group chat. The participant-visible change is queued asynchronously.
Add poll options
Irreversibly add recipient-visible options to an existing iMessage poll. Poll options cannot be edited or removed after they are added.
Block handle
Block a handle account-wide from inbound and direct outbound messaging. Pair controlled test blocks with UNBLOCK_HANDLE cleanup.
Cancel payment
Irreversibly cancel a financial payment and close its virtual card. Confirm the payment identifier and authorization before calling because the canceled payment cannot be resumed.
Cancel payment request
Irreversibly cancel an unpaid payment request and its underlying payment intent. The checkout can no longer be completed after cancellation; paid, canceled, or expired requests cannot be canceled. Confirm the request ID and intent first.
Connect payment handle
Start the financial-consent ceremony for a customer phone number or email so an agent can later pay on that customer's behalf. This consent-sensitive, irreversible action may contact the customer and send an OTP; call it only with the customer's explicit consent.
Create chat
Create or reuse a chat on an explicit sending line and send an irreversible recipient-visible initial message. First-message text and parts cannot contain links.
Create payment
Create or advance a real financial payment on a connected customer's behalf, potentially minting a single-use virtual card. This is consent-sensitive and financially consequential; obtain explicit customer authorization, verify the amount and merchant, and use an Idempotency-Key for retries.
Create payment request
Create a customer-facing checkout that can collect a one-time charge or start an auto-renewing subscription. This creates financial state but does not itself send the checkout URL to a recipient. Confirm the amount, currency, mode, rail, and intended payer before calling; use idempotency_key for retries.
Create poll
Irreversibly send a recipient-visible iMessage poll to an existing chat. A poll cannot be the chat's first message, and its options are add-only and immutable.
Create webhook subscription
Create a webhook subscription for selected Linq events at a controlled HTTPS callback. The response includes a one-time signing secret that must be stored securely.
Delete attachment
Permanently delete a Linq attachment and its stored bytes.
and 31 more.
How to connect Linq
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Linq immediately.
Connect Linq
Open Settings and go to Connectors, then press Connect on Linq. You can also connect from the Linq page in the app.
Add your Linq API key
Paste your Linq API key when prompted. Zeplik stores it securely on the server and starts working with Linq right away.
Frequently asked questions
- Can I use Linq with Zeplik?
- Yes. Linq is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Linq account inside any conversation.
- What can Zeplik do with Linq?
- Once connected, Zeplik has 25 read and 43 write actions for Linq. Send and manage iMessage, RCS, and SMS conversations, attachments, phone numbers, payments, and webhooks through the Linq Partner API.
- How do I connect Linq to Zeplik?
- You connect Linq by pasting your own Linq API key in Settings under Connectors. There is no separate app to install.
- Does Zeplik change things in Linq without asking?
- No. Zeplik reads from Linq by default. Any action that changes data in Linq requires write access, which stays off until you enable it in Settings under Connectors.
- How much does connecting Linq cost?
- Connecting Linq is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.
Related messaging integrations
- MoceanMocean enables SMS, voice, and verification services, integrating messaging capabilities into applications for multifactor authentication or customer.
- Msg91MSG91 is a cloud communication platform offering secure and robust APIs for SMS, WhatsApp, Email, Voice, and more, enabling businesses to connect.
- NtfySend push notifications to your phone or desktop via PUT/POST
- OneSignal REST APIThe OneSignal REST API enables developers to programmatically send push notifications, emails, and SMS, manage users and subscriptions, and configure.
- OneSignal User AuthOneSignal is a customer engagement platform offering push notifications, email, SMS, and in-app messaging services.
- Photon MCPManage Photon messaging projects, resources, conversations, voice profiles and webhooks through its official hosted MCP server.
More on Zeplik
Connect Linq to your AI assistant
Every model, one chat. Bring Linq into Zeplik and let the assistant do the work.