Gemini integration for Doc summarization+ chatbot

Certified Senior Developer

Hi Everyone,

I was trying to explore Appian integration with Gemini to summarize document, email and chatbot interface. If anyone did this either with or without plugin,  let me know the details in brief how you achieved it. Also, did you faced any limitations?

(PS: Specifically needed to integrate with Gemini)

  Discussion posts and replies are publicly visible

Parents
  • Hi Anvesh, do you have other model families available on the Google Vertex platform available to use, such as Anthropic Claude, or does you have to leverage a Gemini model? If it must be a Gemini model, why?

    Appian is currently evaluating direct support for more cloud vendors to power Appian's OOTB generative AI features, so this feedback would be helpful.

  • Not the OP, but been exploring the latest AI features recently and here are some thoughts.

    Many organizations have pre-allocated cloud budgets on AWS, Google Cloud, etc., with credits tied to specific resources or LLM pricing models. Given this, why would they use Appian's OOTB generative AI features (which create vendor lock-in) instead of directly leveraging APIs like Gemini? Similarly, since Appian's storage cost an arm and a leg at large scales, many businesses prefer offloading documents to Google Cloud Storage or S3 and running LLMs directly against those files. This raises the question: what incentive do Appian customers have to store documents locally and lock themselves into Appian's generative AI ecosystem when they have allowances on other cloud platforms? Only reason I can think of is easy of use and setup, which business aren't very interested in.

Reply
  • Not the OP, but been exploring the latest AI features recently and here are some thoughts.

    Many organizations have pre-allocated cloud budgets on AWS, Google Cloud, etc., with credits tied to specific resources or LLM pricing models. Given this, why would they use Appian's OOTB generative AI features (which create vendor lock-in) instead of directly leveraging APIs like Gemini? Similarly, since Appian's storage cost an arm and a leg at large scales, many businesses prefer offloading documents to Google Cloud Storage or S3 and running LLMs directly against those files. This raises the question: what incentive do Appian customers have to store documents locally and lock themselves into Appian's generative AI ecosystem when they have allowances on other cloud platforms? Only reason I can think of is easy of use and setup, which business aren't very interested in.

Children
No Data