Taalk Help Center

Plugin Actions Reference

Every field and option in the plugin action editor, with limits. For a walkthrough, start with Plugins Overview.

Go to Outreach › AI Agents › Plugins, open a plugin and click an action (or Add Action).

Plugin-level fields

Field Notes
Name Required
Auth Custom HTTP Headers (default) or GHL OAuth2 Token
Memo Required. Up to 1,000 characters
HTTP Headers Name/value pairs sent with every webhook action. Values are masked; click Reveal to edit
Actions At least one. Saving an action saves the plugin

What Triggers This Action

Field Notes
Action Name Up to 80 characters, for example "Post Lead to CRM"
When This Action Runs The call event. Default In Conversation
Action Type Webhook (default) or Lookup Table

Events

Event When it fires AI Data Extraction Regex SMS on Success
Pre-Engagement Accepted Before the start event. Useful for pre-call lookups No No Yes
Engagement Accepted Once, when the call is answered No No Yes
Post-Engagement Accepted Right after the start event completes No No Yes
In Conversation On every spoken message during the live call Yes Yes Yes
Engagement Refused When the engagement is rejected (for example DNC or busy) Yes No Yes
Engagement Finished When the call ends. The full transcript is available Yes No Yes
Post-Engagement Processing After the finish event. Good for delayed webhooks Yes No Yes
Transfer Initiated When a live transfer starts Yes No Yes
Transfer Connecting While the transfer is ringing Yes No Yes
Transfer to Internal Operator When the call is handed to a Taalk Phone operator Yes No Yes
Transfer Failed When a transfer attempt fails No No Yes
Survey End When an end-of-call survey is completed No No Yes
Email Replied When a reply to a playbook email arrives Yes Yes No
Embedded URL Clicked When a tracked link in a text or email is clicked No No No
Text Message on Call When a text is sent during the live call No No Yes
Post Text Message on Call After a text is sent during the live call No No No
SMS Sent When a text is sent No No No
SMS Received When a text is received No No No
SMS Error When a text fails No No No

The AI Data Extraction and Regex columns apply to developer users (see the advanced section below).

Action Setup: Webhook

Field Notes
HTTP Method GET (default), POST, PATCH, DELETE, PUT
Endpoint URL Required. Masked after saving; click Reveal to edit. Placeholders allowed
Request Body (JSON) Up to 5,000 characters. Format and expand buttons help with long bodies

Placeholders

Placeholders use angle brackets and are filled in per call.

Placeholder Value
<contact.phone>, <contact.first_name> and other <contact.…> fields The contact's data
<params._gpt.fieldName> A value from AI Data Extraction
<params._regex.name> A named group from a regex trigger
<result.field> A field from your endpoint's response (Response Formatting only)

[Confirm] Saving values for later actions with <save … as …> and starting a transfer by saving a number to _redirectTo (C5).

Action Setup: Lookup Table

Field Options and limits
Matching Method Strict Match or Closest Match
Input expression The value to look up. Up to 1,000 characters
Data Source: Static Table: paste CSV or drop a .csv file. Up to 10,240 characters. Show RAW CSV shows the source
Data Source: Dynamic Input Context Field: a field from the call that holds the table

Response Formatting

Field Notes
Success Message Told to the agent when the action succeeds. Use <result.field> for response data
Failure Message Told to the agent when the action fails or returns an error. Up to 1,000 characters
SMS on Success (Optional) Texts the contact when the action succeeds. Shown only for events marked Yes in the table above

Advanced (developer users)

Developer users see a Prepare Data section between What Triggers This Action and Action Setup, and an extra event, Function. Taalk support can turn on developer access.

Regex Triggers

Available for In Conversation and Email Replied.

Field Notes
Patterns One regular expression per line, up to 2,000 characters. Every line must be a valid regex. Named groups (?<name>...) become params._regex.name
Test Cases Paste sample text to check your patterns. Test at Regex101 opens an external tester

AI Data Extraction

Available for the events marked Yes in the table above. Switching to another event drops the prompt when you save.

Field Notes
Extraction Prompt Write an OBJECTIVE listing the fields to extract, then a JSON TEMPLATE. Results are stored as params._gpt.fieldName
Transcript Segment Full Transcript, Before Transfer (default), After Transfer, No Transcript

JS Data Processor

Runs your JavaScript before the action. It can read params._gpt.*, params._regex.* and contact.*. Return an object; its keys merge into the action payload.

Rules checked when you save:

  • The code must be one arrow function, for example (params) => { return { tier: params._gpt.budget > 1000 ? "high" : "low" }; }. Otherwise: "Preprocessor function is missing."
  • These words are blocked: fetch, import, Promise, then, global, require, function, process, globalThis. Using one shows "The JS contains unsafe code."

[Confirm] The function's arguments and the JavaScript features the runtime supports (for example optional chaining, async) (C5).

Function event

Function lets the AI model call the action as a tool during the conversation.

Field Notes
When to Call Describe when the model should call this function
Parameters (JSON Schema) Must be valid JSON. Every property needs a description

Related articles