Integrating Asana with Oktopost Agent Builder lets you automatically create social posts in Oktopost whenever a content task is marked complete in Asana.
Prerequisites
- Access to Asana with permission to create Custom Rules
- Access to Oktopost Agent Builder (Settings > AI Management > Custom Agents)
Configure the Custom Rule in Asana
Use Asana's native Rules interface to send completed task data to Oktopost—no custom backend code required.
[Screenshot: Asana Customize menu with Rules selected and a Custom Rule being created]
- Open your content planning project in Asana.
- Select Customize, then open Rules.
- Create a Custom Rule.
- Set the trigger to Task completion changed > Task is completed.
- Set the action to Outgoing web request under External tools. This sends the completed task payload to Oktopost like a webhook.
Build the Agent in Oktopost
Design a canvas workflow in Agent Builder to receive the Asana payload and generate your post.
- In Oktopost, go to Settings > AI Management > Custom Agents, then open Agent Builder.
- Add a Webhook Trigger node and configure it to receive the incoming Asana payload. On the canvas, this appears as Asana (Outgoing Web Request).
- Connect the Webhook Trigger to an AI Action node.
- Configure the AI Action prompt to separate mandatory task data from elements the AI can infer:
| Data type | Guidance |
|---|---|
| Mandatory data | Map essential fields—such as final post copy or caption—directly from Asana task fields. Do not rely on the AI to invent this content. |
| AI-driven automation | Allow the AI to handle or infer non-critical elements based on your prompt guidelines (for example, formatting or optional metadata). |
[Screenshot: Agent Builder canvas showing a Webhook Trigger node connected to an AI Action node]
Verify the Payload
Test the workflow before moving to production to confirm critical metadata passes from Asana to Oktopost.
- Create a test task in Asana with sample metadata filled in.
- Mark the test task complete to trigger the Custom Rule.
- Inspect the payload in Oktopost and confirm the expected fields are present:
| Field | Description |
|---|---|
| Post copy / caption | The final text to publish on the social network. |
| Campaign name | The Oktopost campaign to associate with the post. |
| Social profile targets | The profile or profiles where the post should publish. |
| Tags | Labels applied to the post for reporting and organization. |
Handling subtask data
If your team stores social content in Asana subtask descriptions, the initial webhook payload may not include every field. Add an **HTTP Request** node immediately after the webhook to fetch full task details using the Asana Task ID. Generate an Asana authorization token from **Profile Settings > Apps > Developer Console** in Asana.Best Practices
- Use dedicated fields. Avoid managing post copy, network, due date, or campaign name in Asana comment threads—comments break automated field mapping and reduce reporting accuracy.
- Consolidate content planning. Keep planning and approval decisions in one platform so your team does not re-enter data before marking a task complete.
This workflow runs automatically whenever a task is marked complete. Instruct your team to check off tasks only when content is fully approved and ready to publish—otherwise Oktopost may receive premature or incomplete data.