Add Chat Participant
Add an external participant to an existing group chat. The participant-visible change is queued asynchronously.
Send and manage iMessage, RCS, and SMS conversations, attachments, phone numbers, payments, and webhooks through the Linq Partner API.
Add an external participant to an existing group chat. The participant-visible change is queued asynchronously.
Irreversibly add recipient-visible options to an existing iMessage poll. Poll options cannot be edited or removed after they are added.
Block a handle account-wide from inbound and direct outbound messaging. Pair controlled test blocks with UNBLOCK_HANDLE cleanup.
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.
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.
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.
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 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 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 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.
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 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.
Permanently delete a Linq attachment and its stored bytes.
Irreversibly delete a message record from Linq. This does not unsend the message or remove it from recipients' devices, and its idempotency key cannot be reused to resend it.
Permanently delete a Linq webhook subscription and stop its future event deliveries.
Irreversibly change recipient-visible text in one part of a message sent within the last 15 minutes. Linq permits at most five edits per message. A response with no message fields means Linq accepted an edit for a deleted message.
Return metadata and current status for a Linq attachment referenced by a message. This metadata-only action does not download the file.
Select an available Linq sending number, optionally for recipients or a line type. Treat the returned vCard URL as sensitive and ephemeral.
Return one chat by ID, including participants, service, state, and health information.
Return precise locations currently shared by contacts in a chat. Treat coordinates and addresses as sensitive and minimize retention.
Return one Linq experience and preserve its dynamic action field definitions. Discovery does not prove that required provider setup is complete.
Return one Linq message by ID with its content parts, sender, actual and preferred transport, delivery state, reply target, and timestamps.
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.
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.
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.
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.
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.
Return an iMessage poll's current options, voters, and distinct voter count.
Return a Linq line reputation audit created with explicit approval. Audits are retained for no more than 24 hours.
Return one Linq webhook subscription by ID, including its callback URL, event and phone filters, active state, and configured routing-header names.
Leave an iMessage group chat. This is irreversible and prevents further interaction through the sending line.
Return phone numbers, email addresses, short codes, and sender IDs currently blocked account-wide from inbound and direct outbound messaging.
Return one page of chats, optionally filtered by sending line or participant, with a cursor for the next page.
Return Linq account contact-card identity data, optionally for one E.164 sending line.
Discover Linq experiences and their dynamic action fields. Availability in this response does not prove payment-provider onboarding is complete.
Return one page containing the origin message and threaded replies, starting from any message in the thread. A message with no thread returns by itself.
Return one page of messages from a chat, including content, sender, transport, delivery state, direction, reply target, and timestamps, plus a cursor for older messages.
Return one newest-first page of payment requests for reconciliation, optionally filtered by lifecycle status. This is read-only financial metadata; checkout URLs and customer or provider IDs in results are sensitive.
Return the connected Linq account's sending lines with line type, forwarding configuration, and reputation status.
Return the webhook event types currently available for subscription on the connected Linq account.
Return the connected Linq account's webhook subscriptions, including event and phone-number filters, target URLs, active state, and routing-header names.
Mark every message in a chat as read and send an irreversible read receipt.
Reset a chat's recipient-visible transcript background to the default.
Remove an external participant from a group chat. This irreversibly changes recipient-visible conversation membership.
Reserve persistent attachment storage and return a 15-minute presigned upload URL. This action does not upload file bytes; PUT the raw bytes separately to the returned opaque URL using the exact required_headers.
Prompt a contact in a one-to-one iMessage chat to consent to sharing their precise location. This is recipient-visible and rate-limited per chat.
Irreversibly revoke this partner's financial-consent grant for a customer phone number or email. This prevents future payments through the grant but does not delete the customer's provider wallet; revoke only with explicit authorization.
Send one irreversible, externally visible message to phone numbers or emails. Linq reuses a matching chat or creates one and automatically selects the sending line.
Send one follow-up or threaded reply to an existing Linq chat using its established sending line. This creates an irreversible recipient-visible message.
Irreversibly send recipient-visible audio as a native iMessage voice memo bubble to every participant in an existing Linq chat.
Set a recipient-visible color, animated, or photo transcript background. Linq processes the change asynchronously.
Create or replace a Linq contact card for a sending line. This changes public account identity and may activate contact-card sharing.
Share the connected sending line's active contact card with a chat. This irreversibly discloses account identity to recipients.
Create a hosted payment-provider onboarding session for the organization. This starts an external Stripe/Agentcard authorization flow and returns a sensitive hosted URL that an authorized administrator must open; do not use it to complete production onboarding without explicit administrative consent.
Start a potentially metered or limited reputation audit for a Linq sending line. The resulting audit persists for 24 hours.
Show a best-effort recipient-visible typing indicator for about 85-90 seconds. Primarily effective for active iMessage chats.
Stop a specific contact's inbound location share. This consent-sensitive operation ends that contact's share across chats.
Immediately clear the connected line's recipient-visible typing indicator for a chat.
Irreversibly send a recipient-visible update that adds or removes the connected line's vote on one option of an iMessage poll.
Remove an account-wide messaging block. This changes messaging behavior; for testing, unblock only a handle blocked by the same test.
Update a group chat's display name or icon. The participant-visible change is processed asynchronously.
Update the public contact-card identity for one Linq sending line.
Irreversibly send a recipient-visible in-place update to an iMessage app card. The update creates a new message version; use its returned message ID for the next serialized update.
Irreversibly mutate recipient-visible reaction state by adding or removing a tapback, or by adding an iMessage sticker. Stickers cannot be removed.
Change a Linq sending line's production forwarding configuration. Capture the current value before changing it when rollback is required.
Irreversibly send a recipient-visible update that moves, resizes, or rotates an existing iMessage sticker on a message.
Update a Linq webhook subscription's callback, filters, active state, or routing-header names. Callback and routing changes can redirect future account events.
Submit a customer's single-use OTP to complete the financial-consent ceremony and authorize future payments on the customer's behalf. This irreversible, consent-sensitive action consumes the code and records consent; use only a code the customer explicitly provided for this connection.
The Linq integration connects your Dench AI CRM directly to Linq, so agents can read and act on your Linq data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
68 actions are available for agents to invoke on your behalf. Every call runs through Linq's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Linq and click Connect — you'll authorize access through Linq's own sign-in flow. No API keys or code required.
Ask an agent to use Linq in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Linq integration connects your AI CRM to Linq, so AI agents can work with your Linq data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Linq integration currently exposes 68 actions, including Add Chat Participant, Add Poll Options, Block Handle, Cancel Payment, Cancel Payment Request, and Check Messaging Capability. Agents invoke them on your behalf from chat or from automations.
No. You connect Linq from your Dench workspace using Linq's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Linq's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Linq connection from your workspace settings at any time.